cancel
Showing results for 
Search instead for 
Did you mean: 

Missing messages in JMS sender adapter

former_member214909
Participant
0 Kudos

Hello All,

We are in the testing phase of one of the our implementation porject, In which we have used JMS to IDOC scenario  for WMS interfaces.

But unfortunately we are not receiving all the messages in SAP PI from JMS queue.

We have checked with JMS provider and maxximum JMS queue message limit is 100000. and there is no other system is trying to access the same queue.

also there is no message overwritting issue from JMS side.Please check the below screenshot for the channel configuration.

Accepted Solutions (0)

Answers (2)

Answers (2)

former_member214909
Participant
0 Kudos

Anyone can please help further, the issue is not yet resolved.

Thanks,

Anant

JaySchwendemann
Active Contributor
0 Kudos

I'm afraid you'll have to provide more input on where the error is located. As already mentioned, any occurences in Logging / Tracing would be helpful. You might also check your sender JMS channels duplicate handling section. If you turn that on, there should at least an alert being raised / the channel would be deaktivated if it happens to be a duplicate records problem.

Last resort would be opening an incident, i suppose (but then again you would be needing logs / traces to provide to SAP)

Cheers

Jens

former_member214909
Participant
0 Kudos

Hi Jens,

Thanks for your help.

We have resolved the isssue,I guess the problem was from JMS side.

Once they have deactivated the JMS queue all lost messages came into there queue again.

And SAP PI has picked all that messages.

We couldnt find the exact problem but now we have decided to restart the JMS queue if we face  such type of issue again.

Thanks,

Anant

JaySchwendemann
Active Contributor
0 Kudos

That explains the lack of errors / warnings on PI side.

Glad you got you issue resolved / at least got a workaround.

Cheers

Jens

JaySchwendemann
Active Contributor
0 Kudos

Hi Anant,

are you on AEX or Dual Stack? We are experiencing some similar problem at the moment with errors like this show up in the default trace


com.sap.sql.exception.OpenSQLIntegrityConstraintViolationException

...

[NON_TRANSIENT, INTEGRITY_CONSTRAINT_VIOLATION]

If that's the case in your environment, there's a note for that http://service.sap.com/sap/support/notes/1983366

We discovered that the problem occurs especially in high load situations.

Cheers

Jens

former_member214909
Participant
0 Kudos

Hi Jens,

Thanks for reply.

We are using Dual stack for 7.31.

And we are getting only below error in logs, please check if you feel this is related to your problems or not. Also we are in the testing phase so there is no chance of high load.

BR - Anant

JaySchwendemann
Active Contributor
0 Kudos

nah, SQL error from above is probably unrelated. Seems to be some problem with change lists.

Try the following to narrow down the problem

  • make sure tracing level is on warning. you can set that globally if you are on test system
  • don't filter for "SQL" explicitely, scam log for warnings / errors within specific time frame
  • have a look at communication channel monitoring --> select your sender channel --> Processing Details --> View = Persisted Logs

HTH

Cheers

Jens