• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Error "failed to create MQQueueManager" In WAS5.0

 
Ranch Hand
Posts: 37
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hie,
I Have configured WAS5.0 for network deployment.
I created JMSProviders properly.
I have checked WebsphereMQ is running.
Installed the application, i got following errors:
1) FreePool E J2CA0046E: Method createManagedConnctionWithMCWrapper caught an exception during creation of the ManagedConnection for resource JMS$JMSXAQueueConnectionFactory, throwing ResourceAllocationException. Original exception: javax.resource.spi.ResourceAdapterInternalException: createQueueConnection failed
2)MQJMS2005: failed to create MQQueueManager for 'localhost:WAS_sysxxManager_jmsserver'
3)com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2058
at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:172)
4)J2CA0020E: The Connection Pool Manager could not allocate a Managed Connection: javax.resource.spi.ResourceAllocationException: Caught ResourceException thrown during creation of the ManagedConnection.
Regards
Juzar
 
author
Posts: 3892
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I've had this happen to me before, and I've found that it seemed to always be related to missing one or more setup parameters for the QCF or the JMS Provider. For instance, take a look at Sheldon Wosnick's MQJD Article. Yes, I know you're using WebSphere MQ instead of MQ-JD, but going through his setup and making sure you've entered something in everywhere he has is a useful exercise. It's saved my butt a couple of times.
Kyle
 
Ranch Hand
Posts: 57
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi
I'm posting this reply for my future reference and for others who come across the following exception.

[20/11/05 12:49:19:772 GMT] 521880b5 FreePool E J2CA0046E: Method createManagedConnctionWithMCWrapper caught an exception during creation of the ManagedConnection for resource jms/QCFMLAXEP28, throwing ResourceAllocationException. Original exception: javax.resource.spi.ResourceAdapterInternalException: createQueueConnection failed

I have an MDB on start up that gave me this error. The reason was due to one of the parameters used to create a channel/connection on the Qmanager we had running on AIX to a QMangager on an IBMR mainframe. The channel has a connection id or MCA userid , this needs to be a user account on AIX but also corresponds to a RACF userid on the mainframe. We had this id set to be the name of the QManager instead of the MCA id . The message above also gave us the following exception


javax.jms.JMSSecurityException: MQJMS2013: invalid security authentication supplied for MQQueueManager
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic