| Author |
Message
|
| cooldudes |
 Posted: Tue Oct 02, 2012 3:52 pm Post subject: SOAP iNPUT NODE ISSUE |
 |
|
Novice
Joined: 01 Oct 2012
Posts: 11
|
I am getting the below error when I invoke the webservice hosted by WMB.
Can you guys please help me on this why we are getting the below errors.
I have restarted the execution group and soap port is UP.
When I invoke its suddenly going down.
Same flow was working fine in but suddenly started receiving the below error.
I am pasting the syslogs error.I would really appreciate your help in resolving the issue.
Oct 2 11:48:42 user:err|error WebSphere Broker v7003[17432750]: ()[7968]BIP2121E: The thread bootstrap code caught an unhandled exception on thread '7968'. : .477b508e-3501-0000-0080-89b4e73ce198: /build/S700_P/src/CommonServices/rios_aix_4/ImbOsThread.cpp: 276: ImbOsThread::threadBootStrap: :
Oct 2 11:48:42 user:err|error WebSphere Broker v7003[17432750]: ()[7968]BIP2385E: Error updating the statistics message flow transaction container for message flow ' Flow Name :' and node 'flow name'. The terminal ' Node :' was not found. : BK01P3C.477b508e-3501-0000-0080-89b4e73ce198: /build/S700_P/src/DataFlowEngine/ImbDataFlowSMFT.cpp: 682: ImbDataFlowSMFT::incrementTerminal_Count: :
Oct 2 11:48:56 user:info WebSphere Broker v7003[17432750]: ()[1]BIP3133I: The HTTP Listener has stopped listening on port 'BK01P3/10.10.190.70:11040' for 'http' connections. : BK01P3C.477b508e-3501-0000-0080-89b4e73ce198: /build/S700_P/src/DataFlowEngine/NativeTrace/ImbNativeTrace.cpp: 828: TomcatInstanceManager::stopTomcatIfStarted: :
Oct 2 11:48:59 axscgpar0272 user:info WebSphere Broker v7003[17432750]: (BK01P3C.EBSS104)[1]BIP2204I: Execution group using process '17432750' thread '1' stopped. : .477b508e-3501-0000-0080-89b4e73ce198: /build/S700_P/src/DataFlowEngine/ImbMain.cpp: 1446: ImbMain::start: :
Oct 2 11:48:59 user:warn|warning WebSphere Broker v7003[19333206]: : The broker has detected that the Execution Group EBSS104, process ID 17432750, has shutdown. : BK01P3C.agent: /build/S700_P/src/AdminAgent/ImbAdminAgent.cpp: 5158: ImbAdminAgent::startAndMonitorADataFlowEngine: :
Oct 2 11:49:01 user:info WebSphere Broker v7003[17432754]: ()[1]BIP2208I: Execution group (64) started: process '17432754'; thread '1'; additional information: brokerName 'BK01P3C' (operation mode 'enterprise'); executionGroupUUID '477b508e-3501-0000-0080-89b4e73ce198'; executionGroupLabel 'EBSS104'; queueManagerName 'QM01P3C'; trusted 'false'; userId ''; migrationNeeded 'false'; brokerUUID 'b8081e76-920e-11e0-84ca-000000000000'; filePath '/opt/IBM/mqsi/7.0.0.3'; workPath '/MQHA/BK01C/mqsi'; ICU Converter Path ''. : BK01P3C.477b508e-3501-0000-0080-89b4e73ce198: /build/S700_P/src/DataFlowEngine/ImbMain.cpp: 751: ImbMain::start: :
Oct 2 11:49:21 user:info WebSphere Broker v7003[17432754]: ()[1]BIP3132I: The HTTP Listener has started listening on port 'BK01P3/10.10.190.70:11040' for 'http' connections. : BK01P3C.477b508e-3501-0000-0080-89b4e73ce198: /build/S700_P/src/DataFlowEngine/NativeTrace/ImbNativeTrace.cpp: 828: TomcatInstanceManager::startTomcatIfNecessary: :
Oct 2 11:49:25 user:info WebSphere Broker v7003[17432754]: ()[10281]BIP2152I: Configuration message received from broker. : BK01P3C.477b508e-3501-0000-0080-89b4e73ce198: /build/S700_P/src/DataFlowEngine/ImbConfigurationNode.cpp: 324: ImbConfigurationNode::evaluate: :
Oct 2 11:49:25 user:info WebSphere Broker v7003[17432754]: (BK01P3C.EBSS104)[10281]BIP2153I: About to 'start' an execution group. : BK01P3C.477b508e-3501-0000-0080-89b4e73ce198: /build/S700_P/src/DataFlowEngine/ImbConfigurationNode.cpp: 327: ImbConfigurationNode::evaluate: :
Oct 2 11:49:25 user:info WebSphere Broker v7003[17432754]: (BK01P3C.EBSS104)[10281]BIP2154I: Execution group finished with Configuration message. : BK01P3C.477b508e-3501-0000-0080-89b4e73ce198: /build/S700_P/src/DataFlowEngine/ImbConfigurationNode.cpp: 462: ImbConfigurationNode::evaluate: : |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed Oct 03, 2012 3:14 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
How are you invoking the web service?
Are you sure 11040 is the right port?
Do you have any intermediate hardware or software between you and the flow?
What changed between it working and it not working? Have you tried reveresing that?
Have you raised a PMR?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| cooldudes |
| Posted: Wed Oct 03, 2012 8:44 am Post subject: |
|
|
Novice
Joined: 01 Oct 2012
Posts: 11
|
I am invoking the service through SOAP UI.
Yes the sopa port is correct and it was working fine till 9/23 in production.
SUddenly started seeing this error.
RIght after the SOAP node I have a compute node which gets the data from database,and also have a java compute node.
I guess some maintaninance activity happned on the server on 9/21,if its having an issue with maintaninance activity then it should impact all other EG's also rite?
SInce I we have around 15 EG's are there in the broker.No issues with any of the SOAP nodes in other EG's.
I am planning to raise a PMR for this issue.
In our syslogs we found below logs.after that it never worked.
About to 'change ' the Message flow - 'com.metlife.usb.isg.wmb.revisions.EBSSRevision_ThreeDayTerminationReport'. : BK01P3C.477b508e-3501-0000-0080-89b4e73ce198: /build/S700_P/src/DataFlowEngine/ImbDataFlowDirector.cpp: 1007: ImbDataFlowDirector::changeResource: :
Sep 23 21:59:28 axscgpar0272 user:info last message repeated 4 times |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Oct 03, 2012 8:57 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| cooldudes wrote: |
| I guess some maintaninance activity happned on the server on 9/21,if its having an issue with maintaninance activity then it should impact all other EG's also rite? |
All depends what was being done. For example (and only as an example) a change to a port sniffer's configuration to bring this port into it's scanning range would affect this EG but no others. You should investigate (or just ask) what was done.
| cooldudes wrote: |
| I am planning to raise a PMR for this issue. |
Always wise.
| cooldudes wrote: |
In our syslogs we found below logs.after that it never worked.
About to 'change ' the Message flow - 'com.metlife.usb.isg.wmb.revisions.EBSSRevision_ThreeDayTerminationReport'. : BK01P3C.477b508e-3501-0000-0080-89b4e73ce198: /build/S700_P/src/DataFlowEngine/ImbDataFlowDirector.cpp: 1007: ImbDataFlowDirector::changeResource: :
Sep 23 21:59:28 axscgpar0272 user:info last message repeated 4 times |
So you have a log message saying something's doing something to WMB & yet still don't see a suspect? That namespace doesn't sound like IBM wrote it, but that it think's it's revising WMB in some way. I'd locate the author (or the owner) and ask what it did. Especially if that log message was emitted at or about the maintenance time.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Oct 03, 2012 9:00 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
This isn't a Java/JMS question, so this should be moved to broker forum.
The messages indicate that the EG can't start because it's having an issue processing a monitoring configuration to generate some statistics, and then indicate that someone is attempting to redeploy a flow a lot.
I'd start by creating a brand new EG and attempting to deploy all of the same artifacts that exist on the current EG to the new one. Then attempt to remove and delete the other EG. |
|
| Back to top |
|
|
| cooldudes |
| Posted: Wed Oct 03, 2012 11:24 am Post subject: |
|
|
Novice
Joined: 01 Oct 2012
Posts: 11
|
| Thanks everyone for your quick responses.After turming off the statistics monitoring it started working. |
|
| Back to top |
|
|
| cooldudes |
| Posted: Wed Oct 03, 2012 12:19 pm Post subject: |
|
|
Novice
Joined: 01 Oct 2012
Posts: 11
|
| By I still have some un answered questions like why it is having impact for only this specific message flow or EG.I have soap nodes in other eg's also but there is no impact to those. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Oct 03, 2012 1:17 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| cooldudes wrote: |
| By I still have some un answered questions like why it is having impact for only this specific message flow or EG.I have soap nodes in other eg's also but there is no impact to those. |
Because the monitoring configuration causing the problem refered to that flow?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
