[
http://jira.jboss.com/jira/browse/JBESB-1698?page=comments#action_12414415 ]
Len DiMaggio commented on JBESB-1698:
-------------------------------------
The error message:
Caused by: javax.naming.NamingException: Unable to communicate with the queue manager
while looking up object __dummy2@#$%
Does look like a communication error, but it's very different from the (expected)
error if I try to deploy the ESB archive configured for IBM MQ if the WebSphere MQ queue
manager is not running:
Caused by: javax.naming.ServiceUnavailableException: Unable to connect to the target queue
manager localhost:1414/SYSTEM.DEF.SVRCONN [Root exception is com.ibm.mq.MQException:
MQJE001: An MQException occurred: Completion Code 2, Reason 2059
MQJE011: Socket connection attempt refused]
SOA-P/ESB with IBM MQ 6 = javax.naming.NotContextException
----------------------------------------------------------
Key: JBESB-1698
URL:
http://jira.jboss.com/jira/browse/JBESB-1698
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Registry and Repository
Affects Versions: 4.2.1 CP2, 4.2.1
Reporter: Len DiMaggio
Assigned To: Kevin Conner
Fix For: 4.3, 4.2.1 CP3
Project JIRA for SOA-P JIRA:
http://jira.jboss.com/jira/browse/SOA-535
See user forum post for details:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=134669
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira