| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| BIP2329E exceptions |
« View previous topic :: View next topic » |
| Author |
Message
|
| p.cradwick |
 Posted: Thu Mar 09, 2006 6:10 pm Post subject: BIP2329E exceptions |
 |
|
Acolyte
Joined: 16 May 2001
Posts: 56
|
Hi,
I have a requirement to access a two Databases from a node so wrote a Java f() to access the second.
When I connected this into the compute node I started getting the exception
"BIP2329E: An unexpected NULL value was encountered" after the "return true"
statement of the PREVIOUS compute node which had never previously shown an error.
All this node does basically is parse InputRoot.BLOB.BLOB to MRM which is then attached to the OutputRoot.
The input msg (BLOB) went off to the exception handler and the next compute node in there ALSO gave a (second) 2329 exception.
The msg finally 'died' in a third compute node within the exception handler, logging the failure and the msg, and this node
did NOT throw a 2329 exception.
I then removed all trace of the Java code from the flow, deleted jar files, restarted everything, re-booted,
started with wmbt -clean but I still get the 2329 at the same place.
Anyone seen this behaviour before, or better still got a fix for it??
Peter |
|
| Back to top |
|
 |
| elvis_gn |
| Posted: Fri Mar 10, 2006 12:00 am Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi p.cradwick,
Which version of MB are u using.
Can u post the code please.
Regards. |
|
| Back to top |
|
|
| mgk |
| Posted: Fri Mar 10, 2006 1:44 am Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1642
|
Hi,
Also 2329 states:
| Quote: |
"This message will be accompanied with others which will give the higher level context for this error.
Look at these other messages to determine the root source of the problem." |
Can you post any other messages in full as well please.
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. |
|
| Back to top |
|
|
| p.cradwick |
| Posted: Sun Mar 12, 2006 2:03 pm Post subject: |
|
|
Acolyte
Joined: 16 May 2001
Posts: 56
|
I am using Broker v6.0 with no CSD.
Well marvellous what difference a weekend makes! In case it helps someone else, here's what happened:
I tried the same code on another machine (laptop) and found the same error, however thanks to 'Source Safe' I was able to go back a couple of days to code that did not give the error. When I carefully brought this up to date commenting out the 'bad' Java routine, I was able to get code that worked to completion (minus a few data items!!) with no exceptions. This code included another Java routine that worked fine. So come Monday I migrated this code to the desktop and all was well. Have re-introduced the 'bad' Java function and still no exception problem (apart from the fact that I don't get the data I want!).
So it looks like the problem was definitely code related, but don't really know how...
One last thing, the last run I did before starting to get the 2329 exception, I erroneously had a "throws MbException" on the Java function called from esql. From then on all went to custard! Maybe that had something to do with it... 
Anyway guess I can take it from here - thanks for responding and listening!
Peter |
|
| 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
|
|
|
|
