aspose file tools
The moose likes Websphere and the fly likes Problem with JMS n WSAD Big Moose Saloon
  Search | Java FAQ | Recent Topics
Register / Login
JavaRanch » Java Forums » Products » Websphere
Reply Bookmark "Problem with JMS n WSAD" Watch "Problem with JMS n WSAD" New topic
Author

Problem with JMS n WSAD

anisha yunus
Greenhorn

Joined: Dec 30, 2003
Posts: 12
I have installed..WSAD5.1.2 with 5.0 Test Environment and IBM WebSphere MQ 5.3.

I have created a PointToPoint Messaging Client. with a QueueConnectionFactory n Queue JNDI name.

I am getting following problems during the server startup...

*** Starting the server ***
************ Start Display Current Environment ************
WebSphere Platform 5.0 [BASE 5.0.2 ptf2M0325.01] running with process name localhost\localhost\server1 and process id 2088
Host Operating System is Windows 2000, version 5.0
Java version = J2RE 1.3.1 IBM Windows 32 build cn131-20030711a (JIT enabled: jitc), Java Compiler = jitc, Java VM name = Classic VM
was.install.root = C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5
user.install.root = C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5
Java Home = C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5\java\jre
ws.ext.dirs = C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/java/lib;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/classes;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/classes;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/lib;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/lib/ext;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/web/help;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/deploytool/itp/plugins/com.ibm.etools.ejbdeploy/runtime;C:/IBM/WebSphere Studio/Application Developer/v5.1.2/wstools/eclipse/plugins/com.ibm.etools.webservice_5.1.2/runtime/worf.jar
Classpath = C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/properties;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/properties;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/lib/bootstrap.jar;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/lib/j2ee.jar;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/lib/lmproxy.jar;C:/IBM/WebSphere Studio/Application Developer/v5.1.2/wstools/eclipse/plugins/com.ibm.etools.websphere.tools.common_5.1.1.1/runtime/wteServers.jar;C:/IBM/WebSphere Studio/Application Developer/v5.1.2/wstools/eclipse/plugins/com.ibm.etools.websphere.tools.common_5.1.1.1/runtime/wasToolsCommon.jar
Java Library path = C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/bin;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/java/bin;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/java/jre/bin;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\eclipse\jre\bin;.;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\eclipse\jre\bin;C:\IBM\WebSphere MQ\Java\lib;C:\dev\MKS\IntegrityClient\bin;c:\dev\Perl\bin;C:\WINNT\system32;C:\WINNT;C:\WINNT\System32\Wbem;C:\dev\cygwin\bin;C:\dev\4NT302;C:\dev\apache-ant-1.5.4\bin;C:\dev\jdk1.3.1_08\bin;C:\dev\jakarta-tomcat-4.1.30\bin;C:\dev\mksscripts\src;C:\tbs\bin;C:\Program Files\IBM\WebSphere MQ\WEMPS\bin;c:\dev\MQ\bin;C:\IBM\WebSphere MQ\Java\bin;C:\IBM\WebSphere MQ\WEMPS\bin;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5\bin;C:\IBM\WebSphere MQ\bin;;C:\IBM\WebSphere MQ\bin;C:\IBM\WebSphere MQ\Java\bin;C:\IBM\WebSphere MQ\WEMPS\bin;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5\bin;.;C:\dev\NMake;C:\dev\ZipUnzip;
************* End Display Current Environment *************
[6/7/04 11:59:06:000 IST] 4eee356d ManagerAdmin I TRAS0017I: The startup trace state is *=all=disabled.
[6/7/04 11:59:06:516 IST] 4eee356d AdminInitiali A ADMN0015I: AdminService initialized
[6/7/04 11:59:07:500 IST] 4eee356d Configuration A SECJ0215I: Successfully set JAAS login provider configuration class to com.ibm.ws.security.auth.login.Configuration.
[6/7/04 11:59:07:547 IST] 4eee356d SecurityDM I SECJ0231I: The Security component's FFDC Diagnostic Module com.ibm.ws.security.core.SecurityDM registered successfully: true.
[6/7/04 11:59:07:641 IST] 4eee356d SecurityCompo I SECJ0309I: Java 2 Security is disabled.
[6/7/04 11:59:07:656 IST] 4eee356d SecurityCompo I SECJ0212I: WCCM JAAS configuration information successfully pushed to login provider class.
[6/7/04 11:59:07:656 IST] 4eee356d SecurityCompo I SECJ0240I: Security service initialization completed successfully
[6/7/04 11:59:09:797 IST] 4eee356d JMSEmbeddedPr A MSGS0050I: Starting the Queue Manager
[6/7/04 11:59:11:125 IST] 4eee356d JMSEmbeddedPr A MSGS0051I: Queue Manager open for business
[6/7/04 11:59:11:125 IST] 4eee356d JMSEmbeddedPr A MSGS0052I: Starting the Broker
[6/7/04 11:59:11:297 IST] 4eee356d SystemErr R MQJE001: Completion Code 2, Reason 2085
[6/7/04 11:59:11:297 IST] 4eee356d BrokerManager E MSGS0255E: Broker Manager unable to attach to Queue Manager - unknown Queue
[6/7/04 11:59:11:328 IST] 4eee356d JMSService E MSGS0001E: Starting the JMS Server failed with exception: com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2085
at com.ibm.mq.MQQueueManager.accessQueue(MQQueueManager.java:1527)
at com.ibm.mq.MQQueueManager.accessQueue(MQQueueManager.java:1579)
at com.ibm.ws.messaging.BrokerManager.attachToMQ(BrokerManager.java:439)
at com.ibm.ws.messaging.BrokerManager.startBroker(BrokerManager.java:234)
at com.ibm.ws.messaging.JMSEmbeddedProviderImpl.start(JMSEmbeddedProviderImpl.java:194)
at com.ibm.ws.messaging.JMSService.start(JMSService.java:288)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:543)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:418)
at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:183)
at com.ibm.ws.runtime.WsServer.start(WsServer.java:128)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
at com.ibm.etools.websphere.tools.runner.api.ServerRunnerV5$1.run(ServerRunnerV5.java:97)

Please help me in solving this problem ASAP.
Jessica Sant
Sheriff

Joined: Oct 17, 2001
Posts: 4313

moving this to the websphere forum

Have you tried searching for that error code out on the web or in Web Sphere's documentation?
Anonymous
Ranch Hand

Joined: Nov 22, 2008
Posts: 18944
MSGS0255E: Broker Manager unable to attach to Queue Manager - unknown Queue

I think your problem is that your queue configuration in WAS is wrong.
Maybe this link helps you.

Wich Ressource Provider did you configure ? Which Connection mode are you using ? (Client or shared memory ?).
Can you provide some details of your configuration ?
[ June 16, 2004: Message edited by: Oliver Refle ]
Sivakumar Swaminathan
Greenhorn

Joined: May 26, 2004
Posts: 7
Check the name of the queue to which you are connecting.

if this is correct, then check the queue definition

excerpt from the manual:
2085
MQRC_UNKNOWN_OBJECT_NAME
Unknown object name.
On an MQOPEN or MQPUT1 call, the ObjectQMgrName field in the object descriptor MQOD is set to one of the following:


Blank

The name of the local queue manager

The name of a local definition of a remote queue (a queue-manager alias) in which the RemoteQMgrName attribute is the name of the local queue manager
However, the ObjectName in the object descriptor is not recognized for the specified object type.


Corrective action: Specify a valid object name. Ensure that the name is padded to the right with blanks if necessary. If this is correct, check the queue definitions
satnam sandhu
Greenhorn

Joined: Jun 17, 2005
Posts: 1
Hi Sivakumar,

I am new to JMS/MQ, can you please tell me in simple words what i need to do to resolve the above problem.

I am using WASD 5.1.2 with a 5.1 base server with the embedded JMS provider.

Does the queue manager and the queue suppose to be created automatically by the server or manually?

Thanks,

Satnam.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Problem with JMS n WSAD
 
Similar Threads
Problem starting WTE in WSAD 5.0.1
WMSG0017E: Unable to lookup JMS resources, JNDI lookup exception: jms/MyMDBQueue
A file does not exist for module element having uri ...
JMS WSAD 5.1.1 (Embedded JMS Server not started)
Problem while deploying EJBBANK ENTITY BEAN in wsad5.1