| Author |
Message
|
| fitzcaraldo |
 Posted: Fri Jul 16, 2004 9:07 pm Post subject: WBIMB 5.0 - ESQL level is undetermined message on deploy. |
 |
|
Voyager
Joined: 05 May 2003
Posts: 98
|
WBIMB 5.0 CSD 3.
Does anyone have any idea why you get the 'ESQL level for message flow X is undetermined' when trying add a flow to a BAR?
It seems to be a generic error that something is wrong with the flow.
The flow complies OK and everything.
Any ideas? |
|
| Back to top |
|
 |
| kirani |
| Posted: Fri Jul 16, 2004 9:35 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
What is the BIP error number?
_________________
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 |
|
|
| fitzcaraldo |
| Posted: Fri Jul 16, 2004 11:13 pm Post subject: |
|
|
Voyager
Joined: 05 May 2003
Posts: 98
|
There is no BIP number. It's happens when you add a messageflow to a BAR file. It comes back and you click on the Details button to see the message.
Don't get as far as deploying. |
|
| Back to top |
|
|
| kirani |
| Posted: Fri Jul 16, 2004 11:23 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Are ther errors logged in event viewer or eclipse error log?
_________________
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 |
|
|
| JLRowe |
| Posted: Sat Jul 17, 2004 4:35 am Post subject: |
|
|
Yatiri
Joined: 25 May 2002
Posts: 664
Location: South East London
|
The tooling does not recognise your ESQL as 2.1 or 5.0, there was a similar bug that was fixed in CSD02.
Try playing with the ESQL by adding a BROKER SCHEMA statement or some other 5.0 specific syntax and try again. |
|
| Back to top |
|
|
| fitzcaraldo |
| Posted: Sat Jul 17, 2004 4:49 pm Post subject: |
|
|
Voyager
Joined: 05 May 2003
Posts: 98
|
I think I have found the problem. And the problem is that I need a bigger screen than my 14" laptop one.
The message I was seeing was preceeded by another innocuous enough looking message that if I scrolled right far enough gave the actual error condition.  |
|
| Back to top |
|
|
| kirani |
| Posted: Sat Jul 17, 2004 7:54 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
You might want to increase the resolution of the screen so that you can see complete message.
_________________
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 |
|
|
| jensinaus |
| Posted: Thu Nov 11, 2004 2:48 pm Post subject: |
|
|
Newbie
Joined: 04 May 2004
Posts: 5
|
We narrowed it down to a bug in mqsimigratemsgflows. When migrating a flow with a promoted destination mode the migration utility creates the
following xml in the .msgflow file:
</eMetaObjects>
<eMetaObjects xmi:type="ecore:EEnum" xmi:id="EEnum_1">
<eLiterals xmi:id="DestMode.fixed" name="fixed" intLiteral="0"
stringLiteral="fixed"/>
<eLiterals xmi:id="DestMode.reply" name="reply" intLiteral="1"
stringLiteral="reply"/>
<eLiterals xmi:id="DestMode.list" name="list" intLiteral="2"
stringLiteral="list"/>
</eMetaObjects>
By deleting and recreating the promoted destination mode in v5
we get the following generated code in the .msgflow file:
<eMetaObjects xmi:type="ecore:EEnum" xmi:id="EEnum_1">
<eLiterals xmi:id="DestMode.list" name="list" intLiteral="0"
stringLiteral="list"/>
<eLiterals xmi:id="DestMode.reply" name="reply" intLiteral="1"
stringLiteral="reply"/>
<eLiterals xmi:id="DestMode.fixed" name="fixed" intLiteral="2"
stringLiteral="fixed"/>
</eMetaObjects>
That is when it fails the order is fixed, reply then list. If they are
reordered to list, reply, fixed as above then it compiles.
We have written an XSLT script to do this for us following
mqsimigratemsgflows. I've also made IBM aware of this defect.
See http://www.mqseries.net/phpBB2/viewtopic.php?t=15163&highlight=undetermined
Regards
Jens |
|
| Back to top |
|
|
| DaveCanto |
| Posted: Thu Feb 07, 2008 1:26 am Post subject: |
|
|
Novice
Joined: 01 Feb 2008
Posts: 11
Location: Belgium - EU
|
Yesterday I've had the same error message when creating a new .bar-file and adding my messageflow and 2 messagesets.
This problem is caused by the fact I'm using a subflow in my messageflow which was not yet checked out as project from cvs or which still contained an error.
The broker v5.1.0 is not able to notify you in a proper way when there's something wrong in a subflow of your messageflow. So keep this in mind when developping new messageflows.
_________________
Do not underestimate the power of ... unit testing and continuous integration. |
|
| Back to top |
|
|
|
|
