| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Synchronous WS with empty reply randomnly |
« View previous topic :: View next topic » |
| Author |
Message
|
| ipujals |
 Posted: Tue Mar 10, 2015 1:46 am Post subject: Synchronous WS with empty reply randomnly |
 |
|
Apprentice
Joined: 26 Jun 2012
Posts: 31
|
Hi experts,
We have experimenting some issues in our WMB8.0.0.2 last weeks.
We have several EG with two or three applications in it. Every application is using a SoapInput node as initial point. These WS are synchronous. These WS have been running successfully for a long time, but last week started failing:
we get an automatic and instantly (200 ms aprox) empty reply, same response as they were asynchronous; an HTTP 200 OK but with any payload/error/... We have put netool between our RequestApplication and Messabe Broker, and we see an empty reply (0 bytes) as answer.
If we reprocess Request 4 or 5 times, we get at least one good answer (it's random, sometimes we need 3 times, sometimes 5...). This only occurs on WS located in 2 or 3 Executions Group, other WS located in different EG but same http port works successfully
The strangest: if we stop EG (expecting for a http404/not found reply) we have the same situation! 3 or 4 time we get an empty http200 OK and finally we got the HTTP Status 404 - Resource Not Found </h1> URI /I004_A002_DERIVACIOsss does not map to any message flow in broker.
There are no abends, and we have executed Broker agent, httplistener and EG system trace, but not found any error nor trace of the request. We have restarted Message Broker, without success.
Thank you all for ur help  |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Tue Mar 10, 2015 4:32 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
What kind of response do you send in case of expiry? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| ipujals |
| Posted: Tue Mar 10, 2015 7:11 am Post subject: |
|
|
Apprentice
Joined: 26 Jun 2012
Posts: 31
|
Hi,
we haven't defined any message for expiry, but our expiry time is not 200 ms, it is not possible that this message has expired. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Mar 10, 2015 8:20 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| ipujals wrote: |
Hi,
we haven't defined any message for expiry, but our expiry time is not 200 ms, it is not possible that this message has expired. |
When considering expiry you cannot just consider the processing time of the message. You also have to consider the time the message may have already spent on the queue... i.e. the message could expire within a millisecond of you receiving it, if you build a backlog...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| ipujals |
| Posted: Tue Mar 10, 2015 8:31 am Post subject: |
|
|
Apprentice
Joined: 26 Jun 2012
Posts: 31
|
Hi,
In our flow there is no MQ Node, which queue are you referring? It is all about SOAP Nodes.
And.. if there was a backlog.. why is the flow working succesfully at 20-25% of the tests? (same payload, same sender, same app...)
Thx fjb_saper! |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Mar 10, 2015 8:33 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| ipujals wrote: |
Hi,
In our flow there is no MQ Node, which queue are you referring? It is all about SOAP Nodes.
And.. if there was a backlog.. why is the flow working succesfully at 20-25% of the tests? (same payload, same sender, same app...)
Thx fjb_saper! |
Not talking about MQ Queues here...
The http listener has no queue?? How is it handling the requests then?
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| ipujals |
| Posted: Tue Mar 10, 2015 8:40 am Post subject: |
|
|
Apprentice
Joined: 26 Jun 2012
Posts: 31
|
Hi,
we are using broker httplistener, so SYSTEM.BROKER.WS.INPUT is the queue which httplistener put messages.
But every flow in our system is using broker httplistener, and only few ones are working like this
Thx |
|
| Back to top |
|
|
| ipujals |
| Posted: Tue Mar 10, 2015 10:36 am Post subject: |
|
|
Apprentice
Joined: 26 Jun 2012
Posts: 31
|
update:
we have changed the configuration of a EG which is not working, in order to work with EG embedded listener, and now they are working fine! So it looks like some Broker-wide httplistener.
As I understood in
http://www-01.ibm.com/support/knowledgecenter/SSKM8N_8.0.0/com.ibm.etools.mft.doc/ac69310_.htm
embedded listener does not use any queue, so it might be some missconfiguration with SYSTEM.BROKER.WS.INPUT? Maybe too many SOAPInput nodes reading fro mthat queue?
thx! |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
