| Author |
Message
|
| SRIkanth1234 |
 Posted: Sat Oct 27, 2012 2:18 pm Post subject: Issue in the test environment |
 |
|
Novice
Joined: 31 Aug 2011
Posts: 16
|
Hi,
My msgflow works perfectly in Dev environment but fails at the Collector node with the below error message in test Environment.
The collector node receives 2 inputs to send the collection to a WTX node but fails receiving at the very first message. I increased the collection expiry to 5000 secs and event coordination to "First complete collection" connecting the control terminal but no luck. Could someone plz advice as this needs to be taken care ASAP.
ExceptionList
RecoverableException
File:CHARACTER:F:\build\slot1\S800_P\src\DataFlowEngine\ImbDataFlowNode.cpp
Line:INTEGER:1154
Function:CHARACTER:ImbDataFlowNode::createExceptionList
Type:CHARACTER:ComIbmCollectorNode
Name:CHARACTER:UALSeatMapMain#FCMComposite_1_27
Label:CHARACTER:UALSeatMapMain.Collector
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:2230
Text:CHARACTER:Node throwing exception
RecoverableException
File:CHARACTER:EventCollection.java
Line:INTEGER:375
Function:CHARACTER:addMessage
Type:CHARACTER:
Name:CHARACTER:
Label:CHARACTER:
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:2112
Text:CHARACTER:Received event in a sequence group, which is being expired
Insert
Type:INTEGER:5
Text:CHARACTER:Collector
Insert
Type:INTEGER:5
Text:CHARACTER:Received event in a sequence group, which is being expired |
|
| Back to top |
|
 |
| SRIkanth1234 |
| Posted: Sun Oct 28, 2012 6:53 am Post subject: |
|
|
Novice
Joined: 31 Aug 2011
Posts: 16
|
On looking into the test server, the event log shows up the below error messages. Since collector node uses MQ to store the collections, does this cause my flow to fail in the test environment.
Channel program ended abnormally.
Channel program 'SYSTEM.BKR.CONFIG' ended abnormally.
Look at previous error messages for channel program 'SYSTEM.BKR.CONFIG' in the error files to determine the cause of the failure.
Error on receive from host 57 (57.23.59.89).
An error occurred receiving data from 57 (57.23.59.89) over TCP/IP. This may be due to a communications failure.
The return code from the TCP/IP recv() call was 10054 (X'2746'). Record these values and tell the systems administrator. |
|
| Back to top |
|
|
| Vitor |
| Posted: Sun Oct 28, 2012 11:02 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| SRIkanth1234 wrote: |
| Since collector node uses MQ to store the collections, does this cause my flow to fail in the test environment. |
Seriously?
| SRIkanth1234 wrote: |
Channel program ended abnormally.
Channel program 'SYSTEM.BKR.CONFIG' ended abnormally.
Look at previous error messages for channel program 'SYSTEM.BKR.CONFIG' in the error files to determine the cause of the failure. |
You seriously think WMQ stores anything in a channel? Or could?
| SRIkanth1234 wrote: |
| Text:CHARACTER:Received event in a sequence group, which is being expired |
So what part of that sounds like a channel error?
If it works in dev but not in test, what else is different about your architecture? Does dev use the real sending application that test uses, or just a harness?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| SRIkanth1234 |
| Posted: Sun Oct 28, 2012 6:35 pm Post subject: |
|
|
Novice
Joined: 31 Aug 2011
Posts: 16
|
| The infrastructure is a new set up and only my project resides in Dev and Test environments and nothing else. Both Dev and Test are on Wndows and i use SOAPUI to test both environments. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Oct 29, 2012 5:30 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| SRIkanth1234 wrote: |
| i use SOAPUI to test both environments. |
If the flow (as per your original email) is taking 2 inputs and using a collector node, are you using SoapUI to provide both inputs??
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| SRIkanth1234 |
| Posted: Mon Oct 29, 2012 6:57 am Post subject: |
|
|
Novice
Joined: 31 Aug 2011
Posts: 16
|
| No, I sent a OTA request message thru SOAP UI and i save the message in env variable before calling a web service. The collector node receives response from web service and then the original request that i saved in the environment variables. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Oct 29, 2012 7:38 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| SRIkanth1234 wrote: |
| The collector node receives response from web service and then the original request that i saved in the environment variables. |
How does the collector node recieve something from the environment tree?
How do you expect anyone to help you if you keep drip feeding information like this?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| SRIkanth1234 |
| Posted: Mon Oct 29, 2012 8:06 am Post subject: |
|
|
Novice
Joined: 31 Aug 2011
Posts: 16
|
Sorry about that,
before i send the original request to the collector i retrieve the message from the env tree to the output root and propagate to the collector node.
Here is what i do on my flow, I receive a request from a SOAP input which i send it thru SOAPUI and then strip off the Envelope and save to Env tree send to a WTX map. I add the Envelope to the output of WTX map to call a webservice and sends the webservice response to a collector node. And then retreives the original request from the env tree to the output root and sends it to the collector node as the second input. The collector node fails at the very first message with the above mentioned error message. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Oct 29, 2012 8:29 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| SRIkanth1234 wrote: |
| And then retreives the original request from the env tree to the output root |
What retrieves the original request from the env tree? What triggers that process?
Indeed, if all you're trying to do is preserve data across a web service call, why are you using a collector node at all? What are you still failing to tell us?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| cutejigs |
| Posted: Wed Jan 09, 2013 4:27 pm Post subject: |
|
|
Novice
Joined: 20 Jan 2010
Posts: 20
|
hi gurus,
i am also getting the same error in my flows. my setup is:
MQInput Node(receives jms_object from SOAPUI) -> JavaCompute Node (transform the message to an XMLNSC) -> FlowOrder Node (first terminal connected to Collector Node's Request Terminal, second to another subflow) -> Collector Node (has two input terminal, Request and Response)
the Collector Node's Response input terminal receives a message in XMLNSC format. The message receive is the same message received by the Request's input terminal with one additional field.
I have verified that the message sent to the Response's input terminal is well-formatted and the expiry is within limit but still getting the same error.
any ideas about this error? thanks! |
|
| Back to top |
|
|
| cutejigs |
| Posted: Wed Jan 09, 2013 4:29 pm Post subject: |
|
|
Novice
Joined: 20 Jan 2010
Posts: 20
|
| btw, i am trying to use the Collector Node to merge a request/response transactions. i am also using WMB8 fix pack 8.0.0.1 |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jan 10, 2013 8:24 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
The second terminal of a FlowOrder node is not invoked until all the processing of the first terminal has finished. So if the first terminal ends in a Collector node which expects the collection to be completed by the subflow attached to the FlowOrder's second terminal it's out of luck.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jan 10, 2013 8:25 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
btw that's not a great way of doing what you claim to be doing. Why not a fan in / fan out? Or just hold the request in memory?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| cutejigs |
| Posted: Sun Jan 13, 2013 2:21 pm Post subject: |
|
|
Novice
Joined: 20 Jan 2010
Posts: 20
|
hi vitor,
thanks for the reply. finally figured out what is wrong, i am sending the same transactions and this was being compared to the previous transaction. after i clean up the queue (where the Collector node holds the message) everything worked out well.
i am trying different approach based on our business requirement and one of it is the Timeout which i found in the Collector node's expiry. i am currently looking on saving the message to a GlobalCache because of this issue. thank you for your help here.  |
|
| Back to top |
|
|
|
|
