| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| BIP2599E |
« View previous topic :: View next topic » |
| Author |
Message
|
| QueenBee |
 Posted: Mon Sep 20, 2004 10:19 am Post subject: BIP2599E |
 |
|
Apprentice
Joined: 28 May 2003
Posts: 43
Location: Grand Rapids, MICHIGAN
|
Getting the following error:
BIP2599E: The ESQL deployed to the node 'BLAHBLAHBLAH' is invalid.
Anyone experience this error/any ideas? |
|
| Back to top |
|
 |
| vennela |
| Posted: Mon Sep 20, 2004 10:32 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
It is self explanatory
Is your ESQL right? If you think yes then post it here if possible and somebody will help |
|
| Back to top |
|
|
| kirani |
| Posted: Mon Sep 20, 2004 4:51 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
What is your WMQI version?
If using 5.0 your ESQL editor should flag those errors.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| mverh |
| Posted: Wed Dec 15, 2004 10:37 am Post subject: |
|
|
Voyager
Joined: 06 Mar 2002
Posts: 97
|
This error is not so self explanatory. We've had instances where flows work one invokation and then fail the next. We opened an ETR with support and here is an explanation. I think it is important for everyone developing and supporting WBIMB to understand this.
This is cut right from our ETR...
====>
A user can only encounter a BIP2599E error message when they first
process a message through a message flow after it has been deployed or
the broker has been (re)started. When a message flow first processes an
input message, then it will cause its nodes to be processed for the
first time. At this point the run time objects for the node will be
generated. These runtime objects will then be cached for the life of the
Execution group and so this only needs to happen once after a deploy or
on restarted of the broker. If a node accesses a database, then
preliminary checks will be performed against the datasource to ensure
that the necessary resources exist that we are accessing. Therefore as
part of the generation of these run-time checks an attempt will be made
to access the specified datasource(s).
.
Unfortunately because of the nature of the generation of run-time
objects, this can only be attempted once. If this fails at some point
during its processing then the ESQL parse tree and runtime objects will
be in an unknown state, and therefore cannot be used. If a failure does
occur, then the objects are flagged as being in an invalid state and
this means that if a second attempt is made to generate them, then an
error is thrown immediately. This is the BIP2599E error that can be seen
by customers.
.
So if a customer encounters a BIP2599E error message then this means
that the generation of the runtime objects failed the first time around
and it has tried to do them again. This means that some other error has
occured the first time and the BIP2599E is a secondary error.
.
Therefore when investigating such an error, there is no point tracing
the BIP2599E error message because this won't show why this originally
failed. To analyse such an error the broker needs to be restarted or a
deploy performed, and then tracing needs to be activated before the
first message is sent through the message flow. This will capture the
initial error that is actually causing the error. Alternatively, if the
user does not have catch and failure terminals wired, then the local
error log may contain the original error. Since the node interacts with
a database, then it is likely that some database error has occured to
cause the initial failure.
<===
HTH,
Marc Verhiel |
|
| Back to top |
|
|
| CoolDude |
| Posted: Sat Nov 19, 2005 10:20 am Post subject: |
|
|
Apprentice
Joined: 17 Jan 2004
Posts: 39
|
Did this fix your problem or not? Thanks
_________________
Correct Me from Wrong  . If i am correct Appreciate Me  |
|
| Back to top |
|
|
| elvis_gn |
| Posted: Sun Nov 20, 2005 4:52 am Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi guys,
Ok, i have replied to such a post some time back and even i felt for some time that the Error was self explanatory....i.e the ESQL u have deployed to the Compute node is not the correct one.
But this it seems is not the only possible reason....
Check out the data source name that u have entered in the compute node...When i moved my Test flows to the Production I failed to change the DSN names(in the Bar) and found this error......I would have expected something like DataSource name is invalid or Communication error or some kind of SQL Error....But this is what I got....
I'm not saying these are the two possibilities only 
Hope it fixes ur pproblem
Regards. |
|
| 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
|
|
|
|
