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 » Problem starting the listener in Websphere

Post new topic  Reply to topic
 Problem starting the listener in Websphere « View previous topic :: View next topic » 
Author Message
shantha
PostPosted: Thu Jun 09, 2005 10:32 pm    Post subject: Problem starting the listener in Websphere Reply with quote

Apprentice

Joined: 11 Dec 2003
Posts: 41
hi,

I have done the configuration in Websphere Application Server this way.
1 Created a Queue connection factory
I went to Resources->Websphere MQ JMS Provider ->Websphere MQ Queue Connection factories-> new->Here i have given the factory name ,and the MQ hostname QM etc...details of the MQ server where MQ series is installed.
secondly
2 Created a Queue in Websphere
I went to Websphere MQ JMS Provider -> Websphere MQ Queue Destinations->new (created a new JMS queue) with base queue name as a MQ queue and other MQ details are given.
3 Created a listener
Later on I went to the Servers->Applicationservers->myserver(where my application is deployed)->Message Listener service->listener ports->new->created a new listener

4 Starting the Listener Now I get the following error when I try to start the listener I get the following series of erros.CAn somebody help me on this




[6/9/05 18:27:09:030 IST] 1cd006 ConnectionMan E J2CA0020E: The Connection Pool Manager could not allocate a Managed Connection: javax.resource.spi.ResourceAllocationException: createQueueConnection failed
at com.ibm.ejs.j2c.poolmanager.FreePool.createManagedConnectionWithMCWrapper(FreePool.java:1264)
at com.ibm.ejs.j2c.poolmanager.FreePool.createOrWaitForConnection(FreePool.java:1032)
at com.ibm.ejs.j2c.poolmanager.PoolManager.reserve(PoolManager.java:1712)
at com.ibm.ejs.j2c.ConnectionManager.allocateMCWrapper(ConnectionManager.java:674)
at com.ibm.ejs.j2c.ConnectionManager.allocateConnection(ConnectionManager.java:456)
at com.ibm.ejs.jms.JMSQueueConnectionFactoryHandle.createQueueConnection(JMSQueueConnectionFactoryHandle.java:124)
at com.ibm.ejs.jms.listener.MDBListenerImpl.createResources(MDBListenerImpl.java:304)
at com.ibm.ejs.jms.listener.MDBListenerImpl.internalStart(MDBListenerImpl.java:573)
at com.ibm.ejs.jms.listener.MDBListenerImpl.restart(MDBListenerImpl.java:547)
at com.ibm.ejs.jms.listener.MDBListenerImpl.alarm(MDBListenerImpl.java:866)
at com.ibm.ejs.util.am._Alarm.run(_Alarm.java:80)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:672)
---- Begin backtrace for Nested Throwables
javax.resource.spi.ResourceAdapterInternalException: createQueueConnection failed
at com.ibm.ejs.jms.JMSCMUtils.mapToResourceException(JMSCMUtils.java:140)
at com.ibm.ejs.jms.JMSManagedQueueConnection.createConnection(JMSManagedQueueConnection.java:214)
at com.ibm.ejs.jms.JMSManagedConnection.<init>(JMSManagedConnection.java:192)
at com.ibm.ejs.jms.JMSManagedQueueConnection.<init>(JMSManagedQueueConnection.java:66)
at com.ibm.ejs.jms.WSJMSManagedQueueConnectionFactory.createManagedConnection(WSJMSManagedQueueConnectionFactory.java:93)
at com.ibm.ejs.jms.JMSManagedConnectionFactory.createManagedConnection(JMSManagedConnectionFactory.java:502)
at com.ibm.ejs.j2c.poolmanager.FreePool.createManagedConnectionWithMCWrapper(FreePool.java:1226)
at com.ibm.ejs.j2c.poolmanager.FreePool.createOrWaitForConnection(FreePool.java:1032)
at com.ibm.ejs.j2c.poolmanager.PoolManager.reserve(PoolManager.java:1712)
at com.ibm.ejs.j2c.ConnectionManager.allocateMCWrapper(ConnectionManager.java:674)
at com.ibm.ejs.j2c.ConnectionManager.allocateConnection(ConnectionManager.java:456)
at com.ibm.ejs.jms.JMSQueueConnectionFactoryHandle.createQueueConnection(JMSQueueConnectionFactoryHandle.java:124)
at com.ibm.ejs.jms.listener.MDBListenerImpl.createResources(MDBListenerImpl.java:304)
at com.ibm.ejs.jms.listener.MDBListenerImpl.internalStart(MDBListenerImpl.java:573)
at com.ibm.ejs.jms.listener.MDBListenerImpl.restart(MDBListenerImpl.java:547)
at com.ibm.ejs.jms.listener.MDBListenerImpl.alarm(MDBListenerImpl.java:866)
at com.ibm.ejs.util.am._Alarm.run(_Alarm.java:80)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:672)
---- Begin backtrace for Nested Throwables
javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for 'tytasun1:WAS_tytasun1_server3'
at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:556)
at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1736)
at com.ibm.mq.jms.MQConnection.createQMNonXA(MQConnection.java:1129)
at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:170)
at com.ibm.mq.jms.MQQueueConnectionFactory.createQueueConnection(MQQueueConnectionFactory.java:218)
at com.ibm.ejs.jms.JMSManagedQueueConnection.createConnection(JMSManagedQueueConnection.java:203)
at com.ibm.ejs.jms.JMSManagedConnection.<init>(JMSManagedConnection.java:192)
at com.ibm.ejs.jms.JMSManagedQueueConnection.<init>(JMSManagedQueueConnection.java:66)
at com.ibm.ejs.jms.WSJMSManagedQueueConnectionFactory.createManagedConnection(WSJMSManagedQueueConnectionFactory.java:93)
at com.ibm.ejs.jms.JMSManagedConnectionFactory.createManagedConnection(JMSManagedConnectionFactory.java:502)
at com.ibm.ejs.j2c.poolmanager.FreePool.createManagedConnectionWithMCWrapper(FreePool.java:1226)
at com.ibm.ejs.j2c.poolmanager.FreePool.createOrWaitForConnection(FreePool.java:1032)
at com.ibm.ejs.j2c.poolmanager.PoolManager.reserve(PoolManager.java:1712)
at com.ibm.ejs.j2c.ConnectionManager.allocateMCWrapper(ConnectionManager.java:674)
at com.ibm.ejs.j2c.ConnectionManager.allocateConnection(ConnectionManager.java:456)
at com.ibm.ejs.jms.JMSQueueConnectionFactoryHandle.createQueueConnection(JMSQueueConnectionFactoryHandle.java:124)
at com.ibm.ejs.jms.listener.MDBListenerImpl.createResources(MDBListenerImpl.java:304)
at com.ibm.ejs.jms.listener.MDBListenerImpl.internalStart(MDBListenerImpl.java:573)
at com.ibm.ejs.jms.listener.MDBListenerImpl.restart(MDBListenerImpl.java:547)
at com.ibm.ejs.jms.listener.MDBListenerImpl.alarm(MDBListenerImpl.java:866)
at com.ibm.ejs.util.am._Alarm.run(_Alarm.java:80)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:672)
---- Begin backtrace for Nested Throwables
com.ibm.mq.MQException: MQJE001: An MQException occurred: Completion Code 2, Reason 2059
MQJE011: Socket connection attempt refused
at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:239)
at com.ibm.mq.MQClientManagedConnectionFactoryJ11._createManagedConnection(MQClientManagedConnectionFactoryJ11.java:276)
at com.ibm.mq.MQClientManagedConnectionFactoryJ11.createManagedConnection(MQClientManagedConnectionFactoryJ11.java:296)
at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.java:80)
at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConnectionManager.java:171)
at com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.java:737)
at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:671)
at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:452)
at com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1659)
at com.ibm.mq.jms.MQConnection.createQMNonXA(MQConnection.java:1129)
at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:170)
at com.ibm.mq.jms.MQQueueConnectionFactory.createQueueConnection(MQQueueConnectionFactory.java:218)
at com.ibm.ejs.jms.JMSManagedQueueConnection.createConnection(JMSManagedQueueConnection.java:203)
at com.ibm.ejs.jms.JMSManagedConnection.<init>(JMSManagedConnection.java:192)
at com.ibm.ejs.jms.JMSManagedQueueConnection.<init>(JMSManagedQueueConnection.java:66)
at com.ibm.ejs.jms.WSJMSManagedQueueConnectionFactory.createManagedConnection(WSJMSManagedQueueConnectionFactory.java:93)
at com.ibm.ejs.jms.JMSManagedConnectionFactory.createManagedConnection(JMSManagedConnectionFactory.java:502)
at com.ibm.ejs.j2c.poolmanager.FreePool.createManagedConnectionWithMCWrapper(FreePool.java:1226)
at com.ibm.ejs.j2c.poolmanager.FreePool.createOrWaitForConnection(FreePool.java:1032)
at com.ibm.ejs.j2c.poolmanager.PoolManager.reserve(PoolManager.java:1712)
at com.ibm.ejs.j2c.ConnectionManager.allocateMCWrapper(ConnectionManager.java:674)
at com.ibm.ejs.j2c.ConnectionManager.allocateConnection(ConnectionManager.java:456)
at com.ibm.ejs.jms.JMSQueueConnectionFactoryHandle.createQueueConnection(JMSQueueConnectionFactoryHandle.java:124)
at com.ibm.ejs.jms.listener.MDBListenerImpl.createResources(MDBListenerImpl.java:304)
at com.ibm.ejs.jms.listener.MDBListenerImpl.internalStart(MDBListenerImpl.java:573)
at com.ibm.ejs.jms.listener.MDBListenerImpl.restart(MDBListenerImpl.java:547)
at com.ibm.ejs.jms.listener.MDBListenerImpl.alarm(MDBListenerImpl.java:866)
at com.ibm.ejs.util.am._Alarm.run(_Alarm.java:80)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:672)

Can you please tell me if I m wrong anywhere

Thanks and regards
Shantha
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Fri Jun 10, 2005 3:38 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981
Since this is actually the right place for you to have posted this question, I'm going to use it to remind you not to post multiple times.

And suggest that reading the error messages, and thinking about them, and looking at the documentation will be a good place to start.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
shantha
PostPosted: Fri Jun 10, 2005 3:49 am    Post subject: Reply with quote

Apprentice

Joined: 11 Dec 2003
Posts: 41
I thought I told that I am sorry for posting it at the wrong place and I stopped that topic at that place.
This would be my actual posting.
And going through documentation did not help me.
So I am trying to find if anybody has faced this problem and if anybody has a solution that would really help me

Thanks a lot
regards
Shantha
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Fri Jun 10, 2005 3:54 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981
shantha wrote:
I thought I told that I am sorry for posting it at the wrong place and I stopped that topic at that place.


And still posted it twice more:
http://www.mqseries.net/phpBB2/viewtopic.php?p=97992&highlight=#97992
http://www.mqseries.net/phpBB2/viewtopic.php?p=97991&highlight=#97991

And again, if you read the errors you posted, noting in particular the Reason and Completion codes you get, and look those up in the documentation, and then think about it, and maybe search here a bit, I'm sure you'll find an answer.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Fri Jun 10, 2005 7:37 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
Quote:
---- Begin backtrace for Nested Throwables
com.ibm.mq.MQException: MQJE001: An MQException occurred: Completion Code 2, Reason 2059
MQJE011: Socket connection attempt refused

Are you attempting a client connection but the qmgr you are trying to connect to is not available:
a) not running
b) running but no MQ Listener (runmqlsr (Unix))
c) running but the user running the listener has no permissions on the qmgr

Enjoy
Back to top
View user's profile Send private message Send e-mail
bower5932
PostPosted: Fri Jun 10, 2005 7:41 am    Post subject: Reply with quote

Jedi Knight

Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
Well, I saw the other append first and thought 'why hasn't anybody posted an answer?' Then I saw this one and had my answer. As everybody else has pointed out, you probably don't have your WMQ listener (runmqlsr) running.
Back to top
View user's profile Send private message Send e-mail Visit poster's website AIM Address Yahoo Messenger
shantha
PostPosted: Tue Jun 14, 2005 8:16 pm    Post subject: Reply with quote

Apprentice

Joined: 11 Dec 2003
Posts: 41
HI,


I Have a default listener on MQ which is running on 1414 port.
Should I explicitly create another listener for this.
Also the websphere is installed on UNix and the MQSeries which I am trying to connect to is on windows.
Is there any problem in connecting between Unix and Windows.
Please suggest


Thanks and regards
Shantha
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Wed Jun 15, 2005 3:49 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981
Have you confirmed that you can make a regular client connection to the Unix machine, using one of the sample programs?
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
bower5932
PostPosted: Wed Jun 15, 2005 4:53 am    Post subject: Reply with quote

Jedi Knight

Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
I'd definitely go with getting a sample to work. It will confirm your environment.

However, did you ever look at the errors subdirectory on both sides to see if you have a tcp/ip return code that might shed some light on what is wrong?
Back to top
View user's profile Send private message Send e-mail Visit poster's website AIM Address Yahoo Messenger
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » IBM MQ Java / JMS » Problem starting the listener in Websphere
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.