Posted: Tue Aug 05, 2014 10:09 pm Post subject: Process id getting killed and reload the execution group
Novice
Joined: 15 Jan 2014 Posts: 10
Hi All,
I am working on a TCPIP Calll.
In this flow i will be hitting the TCPIP repeatedly until the required output is received but after certain hits my execution group is restarting before.
Find the logs that are generating at this point below
May 8 17:03:31 web WebSphere Broker v7003[2324]: (Broker.Group02)[30]BIP2121E:
The thread bootstrap code caught an unhandled exception on thread '30'. :
Broker.545a6b82-3a01-0000-0080-87763457e91a: /build/S700_P/src/CommonServices/HPUX/ImbOsThread.cpp: 284:
ImbOsThread::threadBootStrap: :
May 8 17:03:31 web WebSphere Broker v7003[2324]:
(Broker.Group02)[30]BIP4374S: An unexpected exception has occurred in the Java API framework. :
Broker.545a6b82-3a01-0000-0080-87763457e91a:
/build/S700_P/src/DataFlowEngine/PluginInterface/com_ibm_broker_plugin_CMbService.cpp: 1815:
ImbJavaExceptionUtils::throwableToNativeException: :
May 8 17:03:38 web WebSphere Broker v7003[2324]:
(Broker.Group02)[1]BIP3133I: The HTTP Listener has stopped listening on port '28702' for 'http' connections. :
Broker.545a6b82-3a01-0000-0080-87763457e91a: /build/S700_P/src/DataFlowEngine/NativeTrace/ImbNativeTrace.cpp: 828:
May 8
17:03:47 web syslog: rm_log_init: fopen of file /etc/opt/resmon/log/client.log failed:
Permission denied
May 8
17:04:01 web WebSphere Broker v7003[2324]:
(Broker.Group02)[1]BIP2204I: Execution group using process '2324' thread '1' stopped. :
Broker.545a6b82-3a01-0000-0080-87763457e91a: /build/S700_P/src/DataFlowEngine/ImbMain.cpp: 1441: ImbMain::start: :
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
Firstly, apply some maintenance - WMBv7.0.0.3 is a lot of fixes in the past.
Secondly, my eye is drawn to this:
satheesh.k wrote:
17:03:47 web syslog: rm_log_init: fopen of file /etc/opt/resmon/log/client.log failed:
Permission denied
That's not a broker error, and something that lives in a directory called "resmon" sounds like a resource monitoring tool to me. Explain what steps you've taken to demonstrate this is a broker issue and not a 3rd party tool that reacts to
satheesh.k wrote:
hitting the TCPIP repeatedly until the required output is received
as if it's a port scan or DDoS attack and causing the abend as a defensive measure.
Also explain why
satheesh.k wrote:
hitting the TCPIP repeatedly until the required output is received
sounds like a good design to you..... _________________ Honesty is the best policy.
Insanity is the best defence.
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