cancel
Showing results for 
Search instead for 
Did you mean: 

Why we have to restart the J2EE engine???

Former Member
0 Kudos

Hi all,

every 5 days all the messages are sitting in adapter engine as status ''TO BE DELIVERED''. everytime after restarting the J2EE engine all the messages came up with ''successfull''. its happening in our Production System.

1)why this problem is happenning every 5 days?

2)after restarting the J2EE engine why all the messages gone through sucessfull?

3) is there any altternative way to fix this problem without restaring the J2ee engine?

Answer will be rewarded.

Kiran.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Kiran,

if the messages are stuck on the J2EE Adapter Engine, you should check for the log entries on the JAVA Node(s).

Could be for example that your machines goes into a kind of GC cycle (seen this in AIX), so that no normal processing on the JAVA Engine is possible. After restart it starts normal again, but you might run into it later on.

So check the GC output in std_server.out of your J2EE server node(s).

Might be helpful to check with an J2EE Engine specialist this part here.

Otherwise it could be that your network connections to one partner is unreliable, and this could prevent also all other messages to be processed.

You might be able to identify the last sucessfull message before and the message causing the "to be delivered" problem in the RWB monitoring of your AFW messages - check there the timeout definitions of the causing adapter.

In older XI releases and SPS the timeout was not set and a hanging partner could stay there for a very long time, even until the J2EE Enigne was and had to be restarted. But this behaviour has been fixed in the meantime. More details in regards to your system release and SPS release might be helpful.

Best regards,

Silvia

Former Member
0 Kudos

We too have the same kind of problem and mostly this is happening with the Sender or Receiver File Adapter.

Answers (2)

Answers (2)

Former Member
0 Kudos

You could try scheduling RSXMB_RESTART_MESSAGES

Otherwise, there may be something fundamentally wrong with your queues.

Do you get a list of queues in SMQR? do you monitor SMQ1 and SMQ2?

Former Member
0 Kudos

Hi,

Which adapters are you using which are getting this problem?

Are these sender or receiver channels?

What is the status in sxmb_moni?

What is the status of the communication channels that are problematic when you get the status "To be delivered"?

Former Member
0 Kudos

all the interfaces are sitting as ''TO BE DELIVERED'' . all the adapters are giving this problem.

in SXMB_MONI there is no error. smq1, smq2 there is no messages.

But after restaring the J2EE all the messages are going sucessfull.

Former Member
0 Kudos

The other place to check then are in SM13 and SM58.

We have been getting LUW Update errors were the update process fails to release the job.

Former Member
0 Kudos

I checked sm13 and sm58 in XI System noting there.

Any clues?

Former Member
0 Kudos

Do you currently have messaged stuck? if not, you won;t find them here.