ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » IBM MQ Java / JMS » WebSphere MQ JMS Provider error on start up

Post new topic  Reply to topic
 WebSphere MQ JMS Provider error on start up « View previous topic :: View next topic » 
Author Message
mq_novice
PostPosted: Mon Jul 17, 2006 11:39 am    Post subject: WebSphere MQ JMS Provider error on start up Reply with quote

Novice

Joined: 26 Jun 2006
Posts: 13
Hi,

WebSphere MQ Queue Connection Factories is defined in WebSphere App Server v5 (on AIX).

The configuration has everything that needed except for Queue Manager name. Queue Manager name is automatically cmposed in the program.

The exactly same configuration works in one WAS and not in the others...

on start-up of the WAS (one that doesn't work), I get below error message..

[7/17/06 15:15:38:619 EDT] 13e7365d ContainerImpl E WSVR0501E: Error creating component null [class com.ibm.ws.runtime.component.ApplicationServerImpl]
com.ibm.ws.exception.RuntimeWarning
at com.ibm.ws.runtime.component.ResourceMgrImpl.installResourceProvider(ResourceMgrImpl.java:830)
at com.ibm.ws.runtime.component.ResourceMgrImpl.installResource(ResourceMgrImpl.java:737)
at com.ibm.ws.runtime.component.ResourceMgrImpl.installResources(ResourceMgrImpl.java:683)
at com.ibm.ws.runtime.component.ResourceMgrImpl.loadResources(ResourceMgrImpl.java:525)
at com.ibm.ws.runtime.component.ResourceMgrImpl.start(ResourceMgrImpl.java:442)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:536)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:413)
at com.ibm.ws.runtime.component.ApplicationServerImpl.start(ApplicationServerImpl.java:152)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:536)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:413)
at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:246)
at com.ibm.ws.runtime.WsServer.start(WsServer.java:128)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:5
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
at com.ibm.ws.bootstrap.WSLauncher.run(WSLauncher.java:222)
at java.lang.Thread.run(Thread.java:567)
Caused by: java.lang.NullPointerException
at com.ibm.ws.runtime.component.binder.MQQueueConnectionFactoryBinder.getBindingObject(MQQueueConnectionFactoryBinder.java:116)
at com.ibm.ws.runtime.component.ResourceMgrImpl.bind(ResourceMgrImpl.java:287)
at com.ibm.ws.runtime.component.ResourceMgrImpl.installResourceProvider(ResourceMgrImpl.java:812)
... 19 more
---- Begin backtrace for nested exception
java.lang.NullPointerException
at com.ibm.ws.runtime.component.binder.MQQueueConnectionFactoryBinder.getBindingObject(MQQueueConnectionFactoryBinder.java:116)
at com.ibm.ws.runtime.component.ResourceMgrImpl.bind(ResourceMgrImpl.java:287)
at com.ibm.ws.runtime.component.ResourceMgrImpl.installResourceProvider(ResourceMgrImpl.java:812)
at com.ibm.ws.runtime.component.ResourceMgrImpl.installResource(ResourceMgrImpl.java:737)
at com.ibm.ws.runtime.component.ResourceMgrImpl.installResources(ResourceMgrImpl.java:683)
at com.ibm.ws.runtime.component.ResourceMgrImpl.loadResources(ResourceMgrImpl.java:525)
at com.ibm.ws.runtime.component.ResourceMgrImpl.start(ResourceMgrImpl.java:442)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:536)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:413)
at com.ibm.ws.runtime.component.ApplicationServerImpl.start(ApplicationServerImpl.java:152)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:536)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:413)
at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:246)
at com.ibm.ws.runtime.WsServer.start(WsServer.java:128)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:5
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
at com.ibm.ws.bootstrap.WSLauncher.run(WSLauncher.java:222)
at java.lang.Thread.run(Thread.java:567)

[7/17/06 15:15:38:726 EDT] 13e7365d RMIConnectorC A ADMC0026I: RMI Connector available at port 2810
[7/17/06 15:15:38:843 EDT] 13e7365d WsServer A WSVR0002I: Server server1 open for e-business, problems occurred during startup


This is the exact error message. I didn't trim or truncate the message.

I have no idea what above error messages mean....
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Mon Jul 17, 2006 2:02 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
These appear to be the relevant lines
Quote:
Caused by: java.lang.NullPointerException
at com.ibm.ws.runtime.component.binder.MQQueueConnectionFactoryBinder.getBindingObject(MQQueueConnectionFactoryBinder.java:116)
at com.ibm.ws.runtime.component.ResourceMgrImpl.bind(ResourceMgrImpl.java:287)
at com.ibm.ws.runtime.component.ResourceMgrImpl.installResourceProvider(ResourceMgrImpl.java:812)
... 19 more
---- Begin backtrace for nested exception
java.lang.NullPointerException
at com.ibm.ws.runtime.component.binder.MQQueueConnectionFactoryBinder.getBindingObject(MQQueueConnectionFactoryBinder.java:116)

In other words you cannot attach to the same resource the same way from 2 different app servers as it resolves here in a null pointer!!
Imagine one is in (MQ) bindings mode the other would have to use (MQ) Client mode...

Enjoy
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
mq_novice
PostPosted: Wed Aug 09, 2006 9:10 am    Post subject: Thanks Reply with quote

Novice

Joined: 26 Jun 2006
Posts: 13
Thanks!

I got it.

it turns out to be it's MQ bug in WAS...

here is the resolution...

http://www-1.ibm.com/support/docview.wss?uid=swg1PK17866
http://www-1.ibm.com/support/docview.wss?uid=swg24012432
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Wed Aug 09, 2006 12:41 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
Thanks for sharing the resolution.
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » IBM MQ Java / JMS » WebSphere MQ JMS Provider error on start up
Jump to:  



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
Protected by Anti-Spam ACP
  
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.