| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| A BIP5035E XMLNSC validation failure during deployment |
« View previous topic :: View next topic » |
| Author |
Message
|
| jfecq |
 Posted: Tue Dec 18, 2012 6:39 am Post subject: A BIP5035E XMLNSC validation failure during deployment |
 |
|
Apprentice
Joined: 24 Sep 2012
Posts: 36
|
I encountered a weird problem during deployment. I am using MQ 7.5 and Broker 8.0. Queue manager is on MSCS, Windows 2008.
I created a broker using
| Code: |
| mqsicreatebroker mybroker -q myqm -e e:\wmb |
where e:\ is cluster disk.
I tried deploying the broker app 1) with broker under MSCS control 2) without MSCS control, but both failed with the error below.
| Quote: |
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 'default' 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.
BIP5049E: A failure occurred when the execution group was preparing XML and DFDL schema files for use as part of the deployment of a library.
A failure occurred when the execution group was preparing XML and DFDL schema files for use as part of the deployment of a library. The deployment of the library has failed, and the deployment will be rolled back.
Review previous messages to find out why the error occurred. Be aware that DFDL schema files must also be valid XML Schema files, and that all DFDL schema files are prepared for use by the XMLNSC domain before being prepared for use by the DFDL domain.
BIP5048E: XMLNSC validation was stopped because errors have occurred while deploying a library to an execution group.
Errors have occurred during the validation of XML schemas that are contained in a library. This has caused XMLNSC validation to stop.
Review further error messages in the event log, syslog or user trace for an indication of the cause of the errors.
BIP5035E: The XMLNSC validator signalled that an error occurred at line 5 while validating a XML schema. The file being processed was IBMdefined\org\xmlsoap\schemas\soap\envelope\soapenv11.xsd in library ICMSLib. The message from the XMLNSC validator is: sch-props-correct.2: A schema cannot contain two global components with the same name this schema contains two occurrences of 'http://schemas.xmlsoap.org/soap/envelope/,Envelope'.
Errors have occurred during the validation of a XML schema.
Review and resolve the problems that are indicated in the message from the XMLNSC validator.
BIP5035E: The XMLNSC validator signalled that an error occurred at line 6 while validating a XML schema. The file being processed was IBMdefined\org\xmlsoap\schemas\soap\envelope\soapenv11.xsd in library ICMSLib. The message from the XMLNSC validator is: sch-props-correct.2: A schema cannot contain two global components with the same name this schema contains two occurrences of 'http://schemas.xmlsoap.org/soap/envelope/,Envelope'.
Errors have occurred during the validation of a XML schema.
Review and resolve the problems that are indicated in the message from the XMLNSC validator.
BIP5035E: The XMLNSC validator signalled that an error occurred at line 15 while validating a XML schema. The file being processed was IBMdefined\org\xmlsoap\schemas\soap\envelope\soapenv11.xsd in library ICMSLib. The message from the XMLNSC validator is: sch-props-correct.2: A schema cannot contain two global components with the same name this schema contains two occurrences of 'http://schemas.xmlsoap.org/soap/envelope/,Header'.
Errors have occurred during the validation of a XML schema.
Review and resolve the problems that are indicated in the message from the XMLNSC validator.
BIP5035E: The XMLNSC validator signalled that an error occurred at line 16 while validating a XML schema. The file being processed was IBMdefined\org\xmlsoap\schemas\soap\envelope\soapenv11.xsd in library ICMSLib. The message from the XMLNSC validator is: sch-props-correct.2: A schema cannot contain two global components with the same name this schema contains two occurrences of 'http://schemas.xmlsoap.org/soap/envelope/,Header'.
Errors have occurred during the validation of a XML schema.
Review and resolve the problems that are indicated in the message from the XMLNSC validator.
BIP5035E: The XMLNSC validator signalled that an error occurred at line 23 while validating a XML schema. The file being processed was IBMdefined\org\xmlsoap\schemas\soap\envelope\soapenv11.xsd in library ICMSLib. The message from the XMLNSC validator is: sch-props-correct.2: A schema cannot contain two global components with the same name this schema contains two occurrences of 'http://schemas.xmlsoap.org/soap/envelope/,Body'.
Errors have occurred during the validation of a XML schema.
Review and resolve the problems that are indicated in the message from the XMLNSC validator.
BIP5035E: The XMLNSC validator signalled that an error occurred at line 24 while validating a XML schema. The file being processed was IBMdefined\org\xmlsoap\schemas\soap\envelope\soapenv11.xsd in library ICMSLib. The message from the XMLNSC validator is: sch-props-correct.2: A schema cannot contain two global components with the same name this schema contains two occurrences of 'http://schemas.xmlsoap.org/soap/envelope/,Body'.
Errors have occurred during the validation of a XML schema.
Review and resolve the problems that are indicated in the message from the XMLNSC validator.
BIP5035E: The XMLNSC validator signalled that an error occurred at line 39 while validating a XML schema. The file being processed was IBMdefined\org\xmlsoap\schemas\soap\envelope\soapenv11.xsd in library ICMSLib. The message from the XMLNSC validator is: sch-props-correct.2: A schema cannot contain two global components with the same name this schema contains two occurrences of 'http://schemas.xmlsoap.org/soap/envelope/,mustUnderstand'.
Errors have occurred during the validation of a XML schema.
Review and resolve the problems that are indicated in the message from the XMLNSC validator.
BIP5035E: The XMLNSC validator signalled that an error occurred at line 46 while validating a XML schema. The file being processed was IBMdefined\org\xmlsoap\schemas\soap\envelope\soapenv11.xsd in library ICMSLib. The message from the XMLNSC validator is: sch-props-correct.2: A schema cannot contain two global components with the same name this schema contains two occurrences of 'http://schemas.xmlsoap.org/soap/envelope/,actor'.
Errors have occurred during the validation of a XML schema.
Review and resolve the problems that are indicated in the message from the XMLNSC validator.
BIP5035E: The XMLNSC validator signalled that an error occurred at line 48 while validating a XML schema. The file being processed was IBMdefined\org\xmlsoap\schemas\soap\envelope\soapenv11.xsd in library ICMSLib. The message from the XMLNSC validator is: sch-props-correct.2: A schema cannot contain two global components with the same name this schema contains two occurrences of 'http://schemas.xmlsoap.org/soap/envelope/,encodingStyle'.
Errors have occurred during the validation of a XML schema.
Review and resolve the problems that are indicated in the message from the XMLNSC validator.
BIP5035E: The XMLNSC validator signalled that an error occurred at line 57 while validating a XML schema. The file being processed was IBMdefined\org\xmlsoap\schemas\soap\envelope\soapenv11.xsd in library ICMSLib. The message from the XMLNSC validator is: sch-props-correct.2: A schema cannot contain two global components with the same name this schema contains two occurrences of 'http://schemas.xmlsoap.org/soap/envelope/,encodingStyle'.
Errors have occurred during the validation of a XML schema.
Review and resolve the problems that are indicated in the message from the XMLNSC validator.
BIP5035E: The XMLNSC validator signalled that an error occurred at line 58 while validating a XML schema. The file being processed was IBMdefined\org\xmlsoap\schemas\soap\envelope\soapenv11.xsd in library ICMSLib. The message from the XMLNSC validator is: sch-props-correct.2: A schema cannot contain two global components with the same name this schema contains two occurrences of 'http://schemas.xmlsoap.org/soap/envelope/,encodingStyle'.
Errors have occurred during the validation of a XML schema.
Review and resolve the problems that are indicated in the message from the XMLNSC validator.
BIP5035E: The XMLNSC validator signalled that an error occurred at line 62 while validating a XML schema. The file being processed was IBMdefined\org\xmlsoap\schemas\soap\envelope\soapenv11.xsd in library ICMSLib. The message from the XMLNSC validator is: sch-props-correct.2: A schema cannot contain two global components with the same name this schema contains two occurrences of 'http://schemas.xmlsoap.org/soap/envelope/,Fault'.
Errors have occurred during the validation of a XML schema.
Review and resolve the problems that are indicated in the message from the XMLNSC validator.
BIP5035E: The XMLNSC validator signalled that an error occurred at line 63 while validating a XML schema. The file being processed was IBMdefined\org\xmlsoap\schemas\soap\envelope\soapenv11.xsd in library ICMSLib. The message from the XMLNSC validator is: sch-props-correct.2: A schema cannot contain two global components with the same name this schema contains two occurrences of 'http://schemas.xmlsoap.org/soap/envelope/,Fault'.
Errors have occurred during the validation of a XML schema.
Review and resolve the problems that are indicated in the message from the XMLNSC validator.
BIP5035E: The XMLNSC validator signalled that an error occurred at line 77 while validating a XML schema. The file being processed was IBMdefined\org\xmlsoap\schemas\soap\envelope\soapenv11.xsd in library ICMSLib. The message from the XMLNSC validator is: sch-props-correct.2: A schema cannot contain two global components with the same name this schema contains two occurrences of 'http://schemas.xmlsoap.org/soap/envelope/,detail'.
Errors have occurred during the validation of a XML schema.
Review and resolve the problems that are indicated in the message from the XMLNSC validator.
|
But if I create a local broker, deployment of the same app is successful. So I thought it shouldn't be the message flow / app problems.
I also googled http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg1IC81112 but read the Windows is not affected.
Anyone shed light on this? |
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Tue Dec 18, 2012 6:46 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
How many nodes in your cluster? Did you clear the cluster cache before creating the broker/qmgr? Had there been any previous failed attempts ?
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| McueMart |
| Posted: Tue Dec 18, 2012 6:56 am Post subject: |
|
|
Chevalier
Joined: 29 Nov 2011
Posts: 490
Location: UK...somewhere
|
| Have you applied 8.0.0.1? The linked APAR was only mentioning unix systems but the symptoms do look very similar to what you are experiencing. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Tue Dec 18, 2012 7:04 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
Also, what was the output of the haregtyp command? Did you ensure that the disk you pointed to was nonquorum disk ? Also, does the domain user for the broker service id exist in the local mqbrkrs group on all nodes MSCS nodes? And are you using a service Id that is not mqm (mqm should never be used as the broker service id).
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| jfecq |
| Posted: Tue Dec 18, 2012 5:26 pm Post subject: |
|
|
Apprentice
Joined: 24 Sep 2012
Posts: 36
|
| lancelotlinc wrote: |
| Also, what was the output of the haregtyp command? Did you ensure that the disk you pointed to was nonquorum disk ? Also, does the domain user for the broker service id exist in the local mqbrkrs group on all nodes MSCS nodes? And are you using a service Id that is not mqm (mqm should never be used as the broker service id). |
I will check it out again. But how do I use a different service Id that is not mqm? Does it affect the deployment?
Also, for MQ MSCS, I will need to enable domain inbound rules for runmqlsr, so that I can access the port. Is there a need to do something for Broker because I can't seem to access 7800. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Dec 19, 2012 3:20 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| jfecq wrote: |
| how do I use a different service Id that is not mqm? |
The same way you use a different service id for SQLServer. It's not a problem on Windows as on Unix platforms (due to OS differences) but it's still not a bad idea.
| jfecq wrote: |
| Does it affect the deployment? |
Well whatever id does deployment will need security.
| jfecq wrote: |
| Also, for MQ MSCS, I will need to enable domain inbound rules for runmqlsr, so that I can access the port. Is there a need to do something for Broker because I can't seem to access 7800. |
Only if you're using nodes with TCP/IP components and have elected to use that port rather than another you can access.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| jfecq |
| Posted: Wed Dec 19, 2012 5:36 pm Post subject: |
|
|
Apprentice
Joined: 24 Sep 2012
Posts: 36
|
I managed to apply the fix pack and solve the deployment issue. But I took a long time to realise under the toolkit, I can, and have to, change the runtime of the broker.
| Quote: |
| Only if you're using nodes with TCP/IP components and have elected to use that port rather than another you can access. |
I am using soap input node which requires 7800. What program should I allow for inbound firewall rules? |
|
| 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
|
|
|
|
