| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Global Cache Issue in IIB v9 |
« View previous topic :: View next topic » |
| Author |
Message
|
| kastle |
 Posted: Wed Mar 05, 2014 11:38 pm Post subject: Global Cache Issue in IIB v9 |
 |
|
Novice
Joined: 28 Jan 2014
Posts: 14
|
I have implemented that global cache in IIB for the default it was working.
But if i want to configure the properties in broker then that command is not working .
I have Executed this command but exception is coming while executing the commands .
MQSI 9.0.0.0
C:\Program Files\IBM\MQSI\9.0.0.0
C:\Program Files\IBM\MQSI\9.0.0.0>mqsichangebroker BRK -b default
BIP8018E: Broker 'BRK' running.
This broker is running; the command you issued cannot be processed when a broker is running.
Stop the broker and reissue the command.
C:\Program Files\IBM\MQSI\9.0.0.0>mqsistop BRK
BIP8071I: Successful command completion.
C:\Program Files\IBM\MQSI\9.0.0.0>mqsichangebroker BRK -b default
BIP8071I: Successful command completion.
C:\Program Files\IBM\MQSI\9.0.0.0>mqsistart BRK
BIP8096I: Successful command initiation, check the system log to ensure that the component started w
ithout problem and that it continues to run without problem.
C:\Program Files\IBM\MQSI\9.0.0.0>mqsichangebroker BRK -b default
BIP8018E: Broker 'BRK' running.
This broker is running; the command you issued cannot be processed when a broker is running.
Stop the broker and reissue the command.
C:\Program Files\IBM\MQSI\9.0.0.0>mqsichangebroker BRK -b C:\Users\hp\Documents\test.xml
BIP8018E: Broker 'BRK' running.
This broker is running; the command you issued cannot be processed when a broker is running.
Stop the broker and reissue the command.
C:\Program Files\IBM\MQSI\9.0.0.0>mqsistop BRK
BIP8071I: Successful command completion.
C:\Program Files\IBM\MQSI\9.0.0.0>mqsichangebroker BRK -b default
BIP8071I: Successful command completion.
C:\Program Files\IBM\MQSI\9.0.0.0>mqsichangebroker BRK -b C:\Users\hp\Documents\test.xml
BIP7193E: The policy file ''C:\Users\hp\Documents\test.xml'', specified for the cache manager, is in
valid.
The policy file does not contain valid XML, or the XML does not validate against the XML schema for
policy files.
The broker configuration has not been changed.
Review previous messages to find out why the error occurred.
Ensure that the policy file specified for the cache manager is valid XML, and that it validates agai
nst the XML schema for policy files.
The XML schema for policy files is available in the installation directory.
BIP5902W: An error occurred in parser ''Root'' while parsing the field named ''XMLNSC'' on behalf of
the node or component 'cache manager'. The data being parsed was ''3c3f786d6c2076657273696f6e3d2231
2e302220656e636f64696e673d225554462d38223f3e0d0a3c4d6170733e0d0a3c4d6170206e616d653d224d617031223e0d
0a3c456e747279206b65793d224b657931223e56616c7565313c2f456e7472793e0d0a3c2f4d61703e0d0a3c4d6170206e61
6d653d224d617032223e0d0a3c456e747279206b65793d224b657932223e56616c7565323c2f456e7472793e0d0a3c456e74
7279206b65793d224b657933223e56616c7565333c2f456e7472793e0d0a3c2f4d61703e3c2f4d6170733e''.
This message gives the name of the field in the parser that was being parsed at the time the error o
ccurred.
For the full context of the error, check for other related messages.
BIP5009E: XML Parsing Errors have occurred.
Errors have occurred during parsing of XML.
Review further error messages for an indication to the cause of the errors.
BIP5025E: XML schema validation error ''Unexpected root tag. Element "Maps" is not a global element.
'' on line '2' column '7' when parsing element ''/Root/XMLNSC''.
Internal error codes: 5032, 2.
This error was reported by the XMLNSC parser. The XML document being parsed is not valid according t
o the message definitions in the message set.
The XML document has violated the rules expressed in the message definition files in the message set
.
BIP8081E: An error occurred while processing the command.
An error occurred while the command was running; the command has cleaned up and ended.
Use messages prior to this one to determine the cause of the error.
Check for some common problems:
Does the user id have the correct authorities (for example a member of the mqbrkrs group)?
Is any operating system limit set too low to allow the command to run?
Is the environment correctly set up?
Correct the problem and retry the command, otherwise, contact your IBM support center.
C:\Program Files\IBM\MQSI\9.0.0.0>mqsichangebroker BRK -b default -r 2809-2825
BIP7185E: The port range ''2809-2825'', specified for the cache manager, is invalid.
Only '17' ports are available in this port range. At least '20' ports are required.
The broker configuration has not been changed.
Ensure that the port range specified for the cache manager is of the form "startport-endport", and t
hat the following conditions are met:
1. The values for startport and endport are valid numbers between 1 and 65536.
2. The value for startport is less than that for endport.
3. Enough ports are available between startport and endport.
BIP8081E: An error occurred while processing the command.
An error occurred while the command was running; the command has cleaned up and ended.
Use messages prior to this one to determine the cause of the error.
Check for some common problems:
Does the user id have the correct authorities (for example a member of the mqbrkrs group)?
Is any operating system limit set too low to allow the command to run?
Is the environment correctly set up?
Correct the problem and retry the command, otherwise, contact your IBM support center.
C:\Program Files\IBM\MQSI\9.0.0.0>mqsichangebroker BRK -b C:\Users\hp\Documents\test.xml
BIP7193E: The policy file ''C:\Users\hp\Documents\test.xml'', specified for the cache manager, is in
valid.
The policy file does not contain valid XML, or the XML does not validate against the XML schema for
policy files.
The broker configuration has not been changed.
Review previous messages to find out why the error occurred.
Ensure that the policy file specified for the cache manager is valid XML, and that it validates agai
nst the XML schema for policy files.
The XML schema for policy files is available in the installation directory.
BIP5902W: An error occurred in parser ''Root'' while parsing the field named ''XMLNSC'' on behalf of
the node or component 'cache manager'. The data being parsed was ''3c3f786d6c2076657273696f6e3d2231
2e302220656e636f64696e673d225554462d38223f3e0d0a3c4d6170733e0d0a3c4d6170206e616d653d224d617031223e0d
0a3c456e747279206b65793d224b657931223e56616c7565313c2f456e7472793e0d0a3c2f4d61703e0d0a3c4d6170206e61
6d653d224d617032223e0d0a3c456e747279206b65793d224b657932223e56616c7565323c2f456e7472793e0d0a3c456e74
7279206b65793d224b657933223e56616c7565333c2f456e7472793e0d0a3c2f4d61703e3c2f4d6170733e''.
This message gives the name of the field in the parser that was being parsed at the time the error o
ccurred.
For the full context of the error, check for other related messages.
BIP5009E: XML Parsing Errors have occurred.
Errors have occurred during parsing of XML.
Review further error messages for an indication to the cause of the errors.
BIP5025E: XML schema validation error ''Unexpected root tag. Element "Maps" is not a global element.
'' on line '2' column '7' when parsing element ''/Root/XMLNSC''.
Internal error codes: 5032, 2.
This error was reported by the XMLNSC parser. The XML document being parsed is not valid according t
o the message definitions in the message set.
The XML document has violated the rules expressed in the message definition files in the message set
.
BIP8081E: An error occurred while processing the command.
An error occurred while the command was running; the command has cleaned up and ended.
Use messages prior to this one to determine the cause of the error.
Check for some common problems:
Does the user id have the correct authorities (for example a member of the mqbrkrs group)?
Is any operating system limit set too low to allow the command to run?
Is the environment correctly set up?
Correct the problem and retry the command, otherwise, contact your IBM support center.
C:\Program Files\IBM\MQSI\9.0.0.0>mqsireportproperties BRK -o CacheManager -a
BIP8019E: Broker 'BRK' stopped.
This broker is stopped; the command you issued cannot be processed when a broker is stopped.
A previous command has been issued to stop this broker, or this broker has never been started.
This broker can be started, changed, or deleted.
C:\Program Files\IBM\MQSI\9.0.0.0>mqsistart BRK
BIP8096I: Successful command initiation, check the system log to ensure that the component started w
ithout problem and that it continues to run without problem.
C:\Program Files\IBM\MQSI\9.0.0.0>mqsireportproperties BRK -o CacheManager -a
CacheManager
uuid='CacheManager'
policy='default'
portRange='2940-2959'
listenerHost=''
shutdownMode='fast'
BIP8071I: Successful command completion.
C:\Program Files\IBM\MQSI\9.0.0.0>mqsichangebroker BRK -b C:\Users\hp\Documents\test.xml
BIP8018E: Broker 'BRK' running.
This broker is running; the command you issued cannot be processed when a broker is running.
Stop the broker and reissue the command.
C:\Program Files\IBM\MQSI\9.0.0.0>mqsistop BRK
BIP8071I: Successful command completion.
C:\Program Files\IBM\MQSI\9.0.0.0>mqsichangebroker BRK -b C:\Users\hp\Documents\test.xml
BIP7193E: The policy file ''C:\Users\hp\Documents\test.xml'', specified for the cache manager, is in
valid.
The policy file does not contain valid XML, or the XML does not validate against the XML schema for
policy files.
The broker configuration has not been changed.
Review previous messages to find out why the error occurred.
Ensure that the policy file specified for the cache manager is valid XML, and that it validates agai
nst the XML schema for policy files.
The XML schema for policy files is available in the installation directory.
BIP5902W: An error occurred in parser ''Root'' while parsing the field named ''XMLNSC'' on behalf of
the node or component 'cache manager'. The data being parsed was ''3c3f786d6c2076657273696f6e3d2231
2e302220656e636f64696e673d225554462d38223f3e0d0a3c6361636865506f6c69637920786d6c6e733d22687474703a2f
2f7777772e69626d2e636f6d2f786d6c6e732f70726f642f7765627370686572652f6d65737361676562726f6b65722f676c
6f62616c200d0a63616368652f706f6c6963792d312e30223e200d0a3c4d6170733e0d0a3c4d6170206e616d653d224d6170
31223e0d0a3c456e747279206b65793d224b657931223e56616c7565313c2f456e7472793e0d0a3c2f4d61703e0d0a3c4d61
70206e616d653d224d617032223e0d0a3c456e747279206b65793d224b657932223e56616c7565323c2f456e7472793e0d0a
3c456e747279206b65793d224b657933223e56616c7565333c2f456e7472793e0d0a3c2f4d61703e3c2f4d6170733e''.
This message gives the name of the field in the parser that was being parsed at the time the error o
ccurred.
For the full context of the error, check for other related messages.
BIP5009E: XML Parsing Errors have occurred.
Errors have occurred during parsing of XML.
Review further error messages for an indication to the cause of the errors.
BIP5025E: XML schema validation error ''Unexpected root tag. Element "cachePolicy" is not a global e
lement.'' on line '3' column '19' when parsing element ''/Root/XMLNSC''.
Internal error codes: 5032, 2.
This error was reported by the XMLNSC parser. The XML document being parsed is not valid according t
o the message definitions in the message set.
The XML document has violated the rules expressed in the message definition files in the message set
.
BIP8081E: An error occurred while processing the command.
An error occurred while the command was running; the command has cleaned up and ended.
Use messages prior to this one to determine the cause of the error.
Check for some common problems:
Does the user id have the correct authorities (for example a member of the mqbrkrs group)?
Is any operating system limit set too low to allow the command to run?
Is the environment correctly set up?
Correct the problem and retry the command, otherwise, contact your IBM support center.
C:\Program Files\IBM\MQSI\9.0.0.0>mqsichangeproperties BRK -b cachemanager -o CacheManager -n policy
,portRange,listenerHost -v none,2800-2819,localhost
BIP8019E: Broker 'BRK' stopped.
This broker is stopped; the command you issued cannot be processed when a broker is stopped.
A previous command has been issued to stop this broker, or this broker has never been started.
This broker can be started, changed, or deleted.
C:\Program Files\IBM\MQSI\9.0.0.0>mqsistart BRK
BIP8096I: Successful command initiation, check the system log to ensure that the component started w
ithout problem and that it continues to run without problem.
C:\Program Files\IBM\MQSI\9.0.0.0>mqsichangeproperties BRK -b cachemanager -o CacheManager -n policy
,portRange,listenerHost -v none,2800-2819,localhost
BIP2051E: Broker BRK (UUID cdea581c-a2c4-4d66-9816-c41f645b531e) could not process an internal confi
guration message to completion, the problem was caused by 'cachemanager'.
The configuration message could not be processed and was rejected.
Use the inserts within this message to determine the cause of the problem. Correct the broker's con
figuration and redeploy using the Integration Toolkit, mqsideploy command or a CMP application. Cont
act your IBM support center if you are unable to resolve the problem.
BIP2087E: Broker 'BRK' 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 can
not be resolved after reviewing these messages, contact your IBM Support center. Enabling service tr
ace may help determine the cause of the failure.
BIP7176E: The port range '2800-2819', specified for the cache manager, is invalid.
This port range conflicts with that of broker 'DemoBroker' which uses the port range '2800-2819'.
The broker configuration has not been changed.
Change this broker so that its cache manager port range does not conflict with that of other brokers
on the system.
BIP8036E: Negative response received.
This command sends an internal configuration message to the broker, the response received indicated
that the internal configuration message was unsuccessful.
Check that the WebSphere MQ transport is available. Check the system log for further information.
C:\Program Files\IBM\MQSI\9.0.0.0>mqsistart BRK |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Thu Mar 06, 2014 3:30 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
How many times do you need the broker to tell you that the XML in your test file does not conform to the expected schema!
Your configuration entered in the test file is not valid xml as far as the broker is concerned. Show us the content of the file.
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| iShakir |
| Posted: Thu Mar 06, 2014 5:21 am Post subject: |
|
|
Apprentice
Joined: 07 Mar 2013
Posts: 47
|
Yes, if you could show us the contents of the test.xml file.
The final change properties command also shows that the port range you're trying to use is already in use by another Integration Node "DemoBroker" on the same system, so I'd try a different port range! |
|
| 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
|
|
|
|
