MQSeries.net :: View topic

jani

Hi All,

WAS 5.1 (embeded MQ)....my JMS server is not running ( i am new to this)

error

(MSGS0255E: Broker Manager unable to attach to Queue Manager - unknown Queue)...

i thought to recreate QM with same name before this i have deleted old one and created new one with same name (got some error).

F:\ibm\WebSphere\AppServer\bin>createmq "f:\ibm\websphere\appserver" USEOMAPD529 USEOMAPD529 jmsserver "f:\ibm\websphere mq" "f:\ibm\websphe
re mq\wemps"
Using: "f:\ibm\websphere\appserver" USEOMAPD529 USEOMAPD529 jmsserver "f:\ibm\websphere mq" "f:\ibm\websphere mq\wemps"
Issuing: crtmqm -c "WebSphere Application Server queue manager - do not delete" -lf 512 -ls 60 -u SYSTEM.DEAD.LETTER.QUEUE -oc amqwasoa -om
amqwasoa -os 32 -od port=0,ExitReason=16 WAS_USEOMAPD529_jmsserver
WebSphere MQ queue manager created.
rc=536892949
Issuing: strmqm -od port=0,ExitReason=16 WAS_USEOMAPD529_jmsserver
AMQ5615: Default objects cannot be created: CompCode = 0 Reason = 0.rc=71
Issuing: runmqsc -e WAS_USEOMAPD529_jmsserver
Using input from: f:\ibm\WebSphere\AppServer\bin\createmq.mqsc
5724-B41 (C) Copyright IBM Corp. 1994, 2002. ALL RIGHTS RESERVED.
Starting MQSC for queue manager WAS_USEOMAPD529_jmsserver.
AMQ8146: WebSphere MQ queue manager not available.
No MQSC commands read.
No commands have a syntax error.
All valid MQSC commands were processed.
rc=20
Issuing: wempsdeletebroker WAS_USEOMAPD529_jmsserver -w
AMQ5615: Default objects cannot be created: CompCode = 0 Reason = 0. BIP8048E: Unable to start MQSeries Queue Manager 'WAS_USEOMAPD529_jmsserver'.
This command attempts to start an MQSeries Queue Manager, the Queue Manager could not be started.
Locate and resolve the problem and retry the command.
rc=48
Issuing: wempscreatebroker WAS_USEOMAPD529_jmsserver -i dummy -a dummy -q WAS_USEOMAPD529_jmsserver -n "" -u "" -p "" -b -j
BIP8087E: WAS_USEOMAPD529_jmsserver already exists and cannot be created.
An attempt was made to create a component that already exists.
Ensure that the component name you have selected for creation is the correct one. Investigate the reasons why this component name already
exists.
rc=87
Issuing: wempsservice WAS_USEOMAPD529_jmsserver -r BrokerUUID=FFFFFFFF-0000-0000-0000-000000000000
WEMPSv210 en US
ucnv Console CCSID 437 dft ucnv CCSID 5348
OS cp1252 ICUW ibm-5348 ICUA ibm-5348
Install Path = F:/IBM/WebSphere MQ/WEMPS
Working Path = F:/IBM/WebSphere MQ/WEMPS
Component UUID = ffffffff-0000-0000-0000-000000000000
queue manager = WAS_USEOMAPD529_jmsserver
pubsub migration = no
fastpath Queue Manager = no
configuration timeout = 300
configuration delay timeout = 60
BIP8071I: Successful command completion.
rc=0
Issuing: endmqm -i WAS_USEOMAPD529_jmsserver
AMQ8146: WebSphere MQ queue manager not available.
rc=40
F:\ibm\WebSphere\AppServer\bin>dspmq
QMNAME(WAS_USEOMAPD529_jmsserver) STATUS(Ended normally)

If i create QM with some other name its able to create without error..

but my JMS server looking same OLD QM name.......is there any way to change with new one.
plz any help (how to resolve ).