Author |
Message
|
kbsiva |
Posted: Fri May 28, 2010 8:58 am Post subject: XMLNSC parser issue WMBV7 |
|
|
 Newbie
Joined: 29 Jun 2009 Posts: 6
|
We are trying to deploy a bar file to Message broker version 7 and it is failing with the error given below.
Now to some other facts - we are upgrading from version 6.1.0.4 to 7 and in some of the other test instances we were able to deploy the same bar file with out issues. In instances where we were able to deploy we used the migratecomponents command to migrate the broker. Here the broker was created new. This also will sound weird but we deleted the broker a few times and then we were able to deploy, it makes no sense.
Any changes in xmlnsc parser for version 7? Any other ideas why this might not work? Appreciate any input on this,
BIP1039I: Deploying BAR file '/var/mqsi/src/test_BATCH_IB_FILE_NOTF.bar' to broker 'TEST_BROKER' (execution group 'test_websphere_interface') ...
BIP1093E: The broker rejected the deployment request and reported the following error(s):
BIP2087E: Broker TEST_BROKER was unable to process the internal configuration message.
The entire internal configuration message failed to be processed successfully.
Use the messages following this message to determine the reasons for the failure. If the problem cannot be resolved after reviewing these messages, contact your IBM Support center. Enabling service trace may help determine the cause of the failure.
BIP4041E: Execution group 'test_websphere_interface' received an invalid configuration message. See the following messages for details of the error.
The broker was asked to deploy a message flow which contained properties that were not recognized by the broker. This typically results from a message flow requiring a version or type of node that is not supported by the broker installation.
Check that the message flow is only using properties or nodes that are supported on the broker. Check that all necessary user-defined extensions are installed and that they are of a version that is compatible with the message flow.
BIP5024E: The creation and preprocessing of the XML schemas in message set 'COMMON_AUDIT_CLIENT_SOAP_MS' has failed.
Review previous messages to find out why the error occurred.
BIP5029E: Error 'The prefix "xsd" for element "xsd:schema" is not bound.' was encountered at line '2' while preprocessing XML Schema file 'CommonAudit_InlineSchema1.xsd' in message set 'COMMON_AUDIT_CLIENT_SOAP_MS'
The XMLNSC parser is preprocessing the XML Schemas for the message set and it has encountered an error.
Check that the XML Schemas in the message set are valid.
BIP2871I: The request made by user 'wmq' to 'deploy' the resource '/var/mqsi/src/test_BATCH_IB_FILE_NOTF.bar' of type 'BAR' on parent 'test_websphere_interface' of type 'ExecutionGroup' has the status of 'FAILED'
An administration request has been received and is being processed. |
|
Back to top |
|
 |
mqjeff |
Posted: Fri May 28, 2010 9:16 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
Deploy BAR files created by Broker 6.1 Toolkit only to Broker 6.1 and later versions of runtime.
Deploy BAR files created by Broker 7.0 Toolkit only to Broker 7.0 and later versions of runtime.
mqsimigratecomponents will migrate ONLY the deployed resources, and makes no change to any Toolkit resources. |
|
Back to top |
|
 |
kbsiva |
Posted: Fri May 28, 2010 10:31 am Post subject: |
|
|
 Newbie
Joined: 29 Jun 2009 Posts: 6
|
Thanks but the bar files were re-created using the wmb version 7 tool kit. |
|
Back to top |
|
 |
kimbert |
Posted: Sun May 30, 2010 2:33 pm Post subject: |
|
|
 Jedi Council
Joined: 29 Jul 2003 Posts: 5542 Location: Southampton
|
Quote: |
BIP5029E: Error 'The prefix "xsd" for element "xsd:schema" is not bound.' was encountered at line '2' while preprocessing XML Schema file 'CommonAudit_InlineSchema1.xsd' in message set 'COMMON_AUDIT_CLIENT_SOAP_MS' |
Can you please post the first few lines of CommonAudit_InlineSchema1.xsd.
Please be kind and enclose the xsd snippet in [code] tags to make it readable. |
|
Back to top |
|
 |
kimbert |
Posted: Mon Jun 07, 2010 2:21 am Post subject: |
|
|
 Jedi Council
Joined: 29 Jul 2003 Posts: 5542 Location: Southampton
|
I see that a PMR has been opened. Please look for updates to the PMR. |
|
Back to top |
|
 |
kbsiva |
Posted: Mon Jun 07, 2010 8:40 am Post subject: |
|
|
 Newbie
Joined: 29 Jun 2009 Posts: 6
|
All,
The problem has been resolved. We were setting the wrong library path in our JDBC configurable service. The path should have been $ORACL_HOME/jdbc/lib instead of $ORACLE_HOME/lib.
This problem is now resolved. Apparently with the incorrect path the classes from this jar file get picked up /d04/oracle/oracle10g/lib/xmlparserv2.jar which causes this.
Hope this helps. Thanks to mqjeff,kimbert for their insight. |
|
Back to top |
|
 |
|