| Author |
Message
|
| simon.starkie |
 Posted: Tue Aug 14, 2007 3:10 pm Post subject: Stack Overflow when importing HL7 V3 WSDL (large). |
 |
|
Disciple
Joined: 24 Mar 2002
Posts: 180
|
Using the "Create a new message definition file from a WSDL definition" wizard.
Clicked the "Select file from outsideworkspace:" radio button.
Browsed to where my WSDL file is located on my local drive.
Task Manager shows javaw.exe consuming 99% CPU for several minutes.
Eventually, a pop-up control appears indicatiing:
....Internal Error
....A Stack Overflow has occurred.
....etc etc
....Do you want to exit the workbench
So I click Yes (I tried No and it WMBT seemed to run OK afterwards).
My current Heap parameters are:
"C:\Program Files\IBM\MessageBrokersToolkit\6.0\wmbt.exe" -Xmx1024M -Xms512M
How can I solve this problem?
Thanks.
PS the HL7 V3 WSDL is large with lots of references to included schemata.
This problem only occurs with these large HL7 V3 WSDL files. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Aug 14, 2007 3:44 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You can try importing the included schemata first, so that there's less to do when you finally get around to importing the WSDL.
You can try increasing the JVM Heap even more...
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| simon.starkie |
| Posted: Tue Aug 14, 2007 4:10 pm Post subject: |
|
|
Disciple
Joined: 24 Mar 2002
Posts: 180
|
Thanks for the advice.
So I changed the Java Heap as follows but same problem:
"C:\Program Files\IBM\MessageBrokersToolkit\6.0\wmbt.exe" -Xmx2048M -Xms2048M
So I imported all the schemata and WSDL files into the workspace. The folder structure is correct since I can "Validate" successfully the WSDL file (i.e. it can find all the referenced schema includes).
But I get the same Stack Overflow problem when doing a "Create a new message definition file from a WSDL definition" and clicking the "Select file from workspace" radio button and selecting the imported WSDL file.
Are there any known fixes for Stack Overflow with WMBT?
I have been able to create a web service proxy client with Visual Studio (C#) and also with RAD6 (Java).
But I'd rather try and get the WMBT problem solved...in fact it's a requirement of the project...so any help would be appreciated. Thanks. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Aug 14, 2007 7:59 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Simon,
Try following:
- import all the dependant xsds, one by one, into the message set.
- At this point you really only need the wsdl definitions that are not contained in/referenced from a separate xsd file.
- try and see if you get the same problem trying to import the wsdl
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| simon.starkie |
| Posted: Mon Aug 20, 2007 3:48 pm Post subject: |
|
|
Disciple
Joined: 24 Mar 2002
Posts: 180
|
Using the following -Xss parameter to set the stack seemed to work.
"C:\Program Files\IBM\MessageBrokersToolkit\6.0\wmbt.exe" -vmargs -Xss128k -Xmx1024M -Xms512M
*EDIT 08-24-2007*
Oops, I had previously forgotton to include -vmargs...must have that for the parms to have any effect at all  |
|
| Back to top |
|
|
| simon.starkie |
| Posted: Tue Sep 25, 2007 2:54 pm Post subject: |
|
|
Disciple
Joined: 24 Mar 2002
Posts: 180
|
OK I got past the stack overflow.
And now, even when I exclude "-vmargs -Xss128k -Xmx1024M -Xms512M " it no longer blows up with a stack overflow. So I can't reproduce the original stack overflow problem, which seem a little odd.
Moving right along, I now have a worse problem. Now, WMBT just keeps running forever with the Windows Task Manager showing javaw.exe using 99% CPU and trivial changes to Mem Usage and/or Various I/O counts such as I/O Other.
In fact, it ran all of last night (over 12 hours).
I've tried the suggestion of pre-importing all of the necessary schemata (there are lots of them with HL7V3).
And prior to trying to generate the message set, I have successfully validated each and every one of the imported schemata files as well as WSDL files.
But when I try to "Start from WSDL or XSD files" wizard, after a couple of minutes, the Progress Window indicates it is stuck in the Message Broker Validation Build process with "Building: /ProblemListMessageSet - Processing added file: QUPC_IN0432000UV.mxsd" underneath. (i.e. it's building the ProblemListMessageSet from the QUPC_IN0432000UV.mxsd schema that was imported when the WSDL was referenced by the wizard.
I'm not seeing any other alerts, core dumps, Windows Events etc.
It just runs and runs...like the proverbial Energizer Bunny.
Is it possible that WMBT can't handle a very large/complex schema structure such as the HL7V3 problem I am dealing with (there are 83 schema files involved and they are all referenced so they must be available for successful validation). FWIW HL7V3 is huge.
Is there another way or another tool for creating a MessageSet ? I suspect MessageSet is proprietary to WMB6 but if the is an alternative, I'd be very interested. This in an important POC for WMB6 in our shop.
If none of the above, then should we open a PMR with IBM?
Cheers! |
|
| Back to top |
|
|
| mgk |
| Posted: Wed Sep 26, 2007 12:17 am Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1642
|
Hi,
Yes, it sounds like you should open a PMR...
_________________
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 |
|
|
| simon.starkie |
| Posted: Tue Oct 23, 2007 3:29 pm Post subject: |
|
|
Disciple
Joined: 24 Mar 2002
Posts: 180
|
Well, we opened a PMR and it turned out IBM already had a fix in the works.
I'm very pleased to confirm that the Fix010 solved our problem.
Confirming I can now import WSDL that is based on large HL7V3 schemata instead of the runaway CPU 99% loop previously seen.
Please thank IBM for providing and throughly testing this fix.
CHEERS  |
|
| Back to top |
|
|
|
|
