JPR queue not processing

[Former Member]

PI 7.0 SP 16

IDOC -> XI -> JPR scenario.

Messages in SXMB_MONI are successful. But not proccessed by JPR.

In RWB we see that "JPRRecv" queue is started and 6200 messages waiting. 2 messages are proccessing infinite time.

Parameters Value

is started Yes

Number of Entries in Queue 6200

Assigned Threads 2

Working Threads 2

Maximum Number of Threads 5

In audit log we see:

Audit Log for Message: 493f2bfd-85ad-661b-e100-0000ac100235

Time Stamp Status Description

2008-12-10 13:33:47 Success Message successfully received by messaging system. Profile: XI URL: http://172.16.2.53:50000/MessagingSystem/receive/JPR/XI Credential (User): PIAPPLUSER

2008-12-10 13:33:48 Success Using connection JPR. Trying to put the message into the receive queue.

2008-12-10 13:33:48 Success Message successfully put into the queue.

2008-12-11 09:28:55 Success The message status set to TBDL.

2008-12-11 09:30:58 Success The message was successfully retrieved from the receive queue.

2008-12-11 09:30:58 Success The message status set to DLNG.

2008-12-11 09:30:58 Success Java proxy runtime (JPR) accepted the message

In adapter monitoring there is no answer from JPR adapter:

"Unable to retrieve JPR status within 10000 msec"

URL "http://172.16.2.53:50000/MessagingSystem/receive/JPR/XI" is opening infinite time.

[stefan_grube]

If this a synchronous Java proxy call and there is no response, maybe there is a loop inside the Java proxy code?

What is the Java proxy doing?

Regards

Stefan

[Former Member]

>

> If this a synchronous Java proxy call and there is no response, maybe there is a loop inside the Java proxy code?
> 
> What is the Java proxy doing?
> 
> Regards
> Stefan

Some file operations... basicly just put XML in proper folder on disk.

Anyway I've already cosidered that our java proxy code may be running into infinite loop and removed our custom code from server, so java proxy is now expected to produce some error.

[Former Member]

Is it possible to remove all messages from the JPR queue?

[Former Member]

It seems that JPR is trying to process 2 messages from queue (STATUS='DLNG').

But they stuck whith this status.

I've canceled all the messages from 'JPRRecv' queue, except 2 messages whith DLNG status. Is there any way to cancel them?

Edited by: Ilya Karnaukhov on Dec 12, 2008 10:28 AM

[prateek]

DLNG status means XI is trying to post data to receiver. When this fails for the first time, the status should change to "Waiting". make sure your receiver is up and running. If for 3 times (default) XI couldnt post the data, it goes to System Error status. You may then restart it.

What is the QOS you are using at sender?

Regards,

Prateek

[Former Member]

>

> DLNG status means XI is trying to post data to receiver. When this fails for the first time, the status should change to "Waiting". make sure your receiver is up and running. If for 3 times (default) XI couldnt post the data, it goes to System Error status. You may then restart it.
> What is the QOS you are using at sender?
> 
> Regards,
> Prateek

Quality of Service: Exactly Once

The problem is those messages never fails. And never successes.

They just keep hanging up in DLNG status.

[prateek]

I would suggest to recheck if by mistake the QOS is set to EOIO. The problem with message in DLNG status is that it could not be restarted. Other possibility could be upgrade to latest patch level.

Regards,

Prateek

[Former Member]

The strangest thing is that I can't get status of JPR adapter in rwb. It should be either green or red. But I got only "Unable to retrieve JPR status within 10000 msec".

[Former Member]

And main problem is that we can't see any any errors in those messages processing and therefore we can't fix them

[prateek]

In SLD, make sure that you have created a WebAS Java BS for XI Integration Server.

Perform JPR Self Test

http://172.16.2.53:50000/ProxyServer/jprselftest

Regards,

Prateek

[Former Member]

>

> In SLD, make sure that you have created a WebAS Java BS for XI Integration Server.
> 

BS created, scenario was working in productive mode until this problem occured.

>

> Perform JPR Self Test
> http://172.16.2.53:50000/ProxyServer/jprselftest

Page opening... no result

Edited by: Ilya Karnaukhov on Dec 11, 2008 9:32 AM

[former_member633171]

stefan.grube prateek.srivastava3

How did you solve this?