| Author |
Message
|
| basva |
 Posted: Thu Mar 03, 2005 1:38 pm Post subject: WBI Migration - problem deploying |
 |
|
Apprentice
Joined: 27 Nov 2002
Posts: 39
|
Hi
We are in the process of migrating to WBI 5 fix pack 4. We tested deplying some simple flows and everything works. (Broker on AIX).
When we migrated existing flow and try to deploy using the bar file, tool kit reports deploy is successful. But in the execution group we have a message flow with the name "Compiled Message Flow" apears. And at the same time config manager crashes with "java.lang.nullPointer" exception. When I removed all the ESQL code from this flow then the deploy is successfull and everything looks good. This makes me believe that there is something in my ESQL which is causing the problem. (This ESQL works fine in 2.1 and in tool kit there are no syntax errors reported). I checked for the keywords in the ESQL but found none.
Anyone experienced similar isssues?
Thanks in advance for your help
Satish |
|
| Back to top |
|
 |
| basva |
| Posted: Mon Mar 07, 2005 7:21 am Post subject: |
|
|
Apprentice
Joined: 27 Nov 2002
Posts: 39
|
I found the problem after going through the process of elimination of the code. And what I found is quite surprising. Deploy is failing and the config manager crashing because of the following comment
"--Indicates it’s alpha .."
If you change the comment to the following it is working.
"--Indicates its alpha .."
So the apostrophe in comment is causing all the problems. We are going to inform IBM and ask them to fix this. |
|
| Back to top |
|
|
| Galichet |
| Posted: Tue Mar 28, 2006 2:31 am Post subject: |
|
|
Acolyte
Joined: 26 Jun 2001
Posts: 69
Location: Paris - France
|
Hi,
I've just had exactly the same problem with a flow (but not migrating it). It was developed from scratch and the deploy makes the configuration manager to crash.
I'm going to verify the comments as you have suggested as soon as the configuration manager is repaired...
Did you have news from IBM ?
Thanks
_________________
Eric Galichet
SMABTP
France |
|
| Back to top |
|
|
| Debadutta |
| Posted: Tue Mar 28, 2006 10:38 am Post subject: |
|
|
Newbie
Joined: 06 Dec 2002
Posts: 4
|
A service trace on the configuration manager should provide the information on the invalid character that might be making the configuration manager database to crash.
Regards,
Debadutta |
|
| Back to top |
|
|
| mqmatt |
| Posted: Wed Mar 29, 2006 12:17 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
(Presumably that character is the apostrophe!)
I think the problem might be the use of XML-special characters in the ESQL, but I'm surprised no-one else has seen this.
I specifically remember enountering the same problem during the v6 development cycle (and was fixed for GA), but the deployment algorithm is quite different so I don't expect the fix to be related.
Your best bet is to create a PMR. |
|
| Back to top |
|
|
| Galichet |
| Posted: Wed Mar 29, 2006 1:17 am Post subject: |
|
|
Acolyte
Joined: 26 Jun 2001
Posts: 69
Location: Paris - France
|
Indeed, I had the following comment in my esql :
-- Verify this: Document.Famille = ‘AA’
Replacing this comment with this one :
-- Verify this: Document.Famille = 'AA' (not the same quote character)
All works fine after that.
I've contacted the IBM support, they are trying to reproduce this problem (quite easy) and probably correct this in a next CSD.
_________________
Eric Galichet
SMABTP
France |
|
| Back to top |
|
|
|
|
