| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Error in core File BIP7053S |
« View previous topic :: View next topic » |
| Author |
Message
|
| SABCAS |
 Posted: Mon Nov 26, 2007 6:08 am Post subject: Error in core File BIP7053S |
 |
|
Acolyte
Joined: 09 Mar 2005
Posts: 60
Location: Switzerland
|
Hallo
every morning at 04:40 the broker saved the following error into core File
Nov 24 04:43:37 sbe6341 MQSIv500[111066]: (SBE6341.MPM_SERVICE_ID)[5398]BIP2121E: The thread bootstrap code caught an unhandled exception on thread '5398'. : SBE6341.fd6362a6-ff00-0000-0080-992047e1ce52: /build/S500_P/src/CommonServices/rios_aix_4/ImbOsThread.cpp: 229: ImbOsThread::threadBootStrap: :
Nov 24 04:43:37 sbe6341 MQSIv500[111066]: (SBE6341.MPM_SERVICE_ID)[5398]BIP7053S: Unexpected Java exception java.lang.IllegalArgumentException at com.ibm.disthub2.impl.util.TopicHandler.checkTopicSyntax(TopicHandler.java(Compiled Code)) at com.ibm.disthub2.impl.matching.MatchSpace.putInternal(MatchSpace.java(Compiled Code)) at com.ibm.disthub2.impl.matching.MatchSpace.put(MatchSpace.java(Compiled Code)) at com.ibm.broker.server.SubscriptionService.newSubscription(SubscriptionService.java:2345) at com.ibm.broker.server.SubscriptionService.subscribe(SubscriptionService.java(Compiled Code)) at com.ibm.broker.server.PubSubNode.subscribe(PubSubNode.java(Compiled Code)) . : SBE6341.fd6362a6-ff00-0000-0080-992047e1ce52: /build/S500_P/src/DataFlowEngine/JavaNodeLibrary/ImbPubSubException.cpp: 309: ImbPubSubJavaException::getJavaExceptionInformation: :
Nov 25 04:43:35 sbe6341 MQSIv500[111070]: (SBE6341.MPM_SERVICE_ID)[5398]BIP2121E: The thread bootstrap code caught an unhandled exception on thread '5398'. : SBE6341.fd6362a6-ff00-0000-0080-992047e1ce52: /build/S500_P/src/CommonServices/rios_aix_4/ImbOsThread.cpp: 229: ImbOsThread::threadBootStrap: :
Nov 25 04:43:35 sbe6341 MQSIv500[111070]: (SBE6341.MPM_SERVICE_ID)[5398]BIP7053S: Unexpected Java exception java.lang.IllegalArgumentException at com.ibm.disthub2.impl.util.TopicHandler.checkTopicSyntax(TopicHandler.java(Compiled Code)) at com.ibm.disthub2.impl.matching.MatchSpace.putInternal(MatchSpace.java:320) at com.ibm.disthub2.impl.matching.MatchSpace.put(MatchSpace.java:232) at com.ibm.broker.server.SubscriptionService.newSubscription(SubscriptionService.java:2345) at com.ibm.broker.server.SubscriptionService.subscribe(SubscriptionService.java(Compiled Code)) at com.ibm.broker.server.PubSubNode.subscribe(PubSubNode.java:3020) . : SBE6341.fd6362a6-ff00-0000-0080-992047e1ce52: /build/S500_P/src/DataFlowEngine/JavaNodeLibrary/ImbPubSubException.cpp: 309: ImbPubSubJavaException::getJavaExceptionInformation: :
The MsgFlow into ExcutionGroup: MPM_SERVICE_ID works fine, but I don't know the reason of this Error.
Somebody could explain what does it means ? 
Thanks a lot
Ciao
Sabato |
|
| Back to top |
|
 |
| bower5932 |
| Posted: Mon Nov 26, 2007 7:15 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
There's this:
http://www-1.ibm.com/support/docview.wss?uid=swg1IY86619
However, I don't think it is your error. The following:
| Code: |
| java.lang.IllegalArgumentException at com.ibm.disthub2.impl.util.TopicHandler.checkTopicSyntax(TopicHandler.java(Compiled Code)) |
makes me suspicious of your actual topic. What is it? |
|
| Back to top |
|
|
| SABCAS |
| Posted: Mon Nov 26, 2007 9:49 pm Post subject: |
|
|
Acolyte
Joined: 09 Mar 2005
Posts: 60
Location: Switzerland
|
Hallo
thanks you for your Help, about your question, the MessageFlow and the ExecutionGroup should be use the normal Topics
$SYS/Broker/+/Status/ExecutionGroup/#
But somebody made last time with Java application several Pub-Sub topics registration, I don't know but someone of these topics maybe it has a Syntax error.
If vou need more information tell me what I have send to you.
Ciao
Sabato |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Nov 27, 2007 3:06 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
What is occurring at 4:40 in the morning, that is causing Broker to decide to generate these errors?
Backups? Database maintenance? Applications running batch processing?
_________________
I am *not* the model of the modern major general. |
|
| 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
|
|
|
|
