Topic
  • 5 replies
  • Latest Post - ‏2013-02-22T11:29:14Z by fjb_saper
SystemAdmin
SystemAdmin
8523 Posts

Pinned topic Tomcat+SpringJms+WebsphereMq

‏2013-02-09T08:17:28Z |
I am running spring jmslistener on tomcat. Its giving security error
WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2063' ('MQRC_SECURITY_ERROR').

Can anyone help me here.

Error mwssage: Tack trace

Feb 8, 2013 5:34:34 PM org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Program Files\Apache Software Foundation\Tomcat 6.0\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Program Files (x86)\IBM\WebSphere MQ\Java\lib;C:\Program Files (x86)\IBM\WebSphere MQ\Java\lib64;C:\instantclient_11_2;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Java\jdk1.6.0_33\bin;C:\apache-activemq-5.4.0\bin;C:\Program Files\TortoiseSVN\bin;C:\apache-ant-1.8.4\bin;C:\Program Files (x86)\IBM\WebSphere MQ\bin64;C:\Program Files (x86)\IBM\WebSphere MQ\bin;C:\Program Files (x86)\IBM\WebSphere MQ\tools\c\samples\bin;;.
Feb 8, 2013 5:34:34 PM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
Feb 8, 2013 5:34:34 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 412 ms
Feb 8, 2013 5:34:34 PM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Feb 8, 2013 5:34:34 PM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.35
Feb 8, 2013 5:34:34 PM org.apache.catalina.startup.HostConfig deployDescriptor
INFO: Deploying configuration descriptor consumer.xml
Feb 8, 2013 5:34:35 PM org.springframework.web.context.ContextLoader initWebApplicationContext
INFO: Root WebApplicationContext: initialization started
Feb 8, 2013 5:34:35 PM org.springframework.context.support.AbstractApplicationContext prepareRefresh
INFO: Refreshing Root WebApplicationContext: startup date Fri Feb 08 17:34:35 IST 2013; root of context hierarchy
Feb 8, 2013 5:34:35 PM org.springframework.beans.factory.xml.XmlBeanDefinitionReader loadBeanDefinitions
INFO: Loading XML bean definitions from ServletContext resource [/WEB-INF/beans-mq.xml]
Feb 8, 2013 5:34:35 PM org.springframework.beans.factory.support.DefaultListableBeanFactory preInstantiateSingletons
INFO: Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@e1bdb58: defining beans msgSender,msgReceiver,jmsConnectionFactory,destinationQueue,jmsDestinationResolver,jmsQueueTemplate,listenerContainer; root of factory hierarchy
Feb 8, 2013 5:34:36 PM org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup start
INFO: Starting beans in phase 2147483647
Feb 8, 2013 5:34:36 PM org.springframework.web.context.ContextLoader initWebApplicationContext
INFO: Root WebApplicationContext: initialization completed in 1417 ms
Feb 8, 2013 5:34:36 PM org.apache.catalina.startup.HostConfig deployDescriptor
INFO: Deploying configuration descriptor manager.xml
Feb 8, 2013 5:34:36 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory docs
Feb 8, 2013 5:34:36 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory ROOT
Feb 8, 2013 5:34:36 PM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8080
Feb 8, 2013 5:34:36 PM org.apache.jk.common.ChannelSocket init
INFO: JK: ajp13 listening on /0.0.0.0:8009
Feb 8, 2013 5:34:36 PM org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=0/15 config=null
Feb 8, 2013 5:34:36 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 2349 ms
Feb 8, 2013 5:34:41 PM org.springframework.jms.listener.DefaultMessageListenerContainer refreshConnectionUntilSuccessful
WARNING: Could not refresh JMS Connection for destination 'queue:///Q_SAA' - retrying in 5000 ms. Cause: JMSWMQ0018: Failed to connect to queue manager 'QM_SAA' with connection mode 'Client' and host name '10.24.198.91'.; nested exception is com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2063' ('MQRC_SECURITY_ERROR').
Feb 8, 2013 5:34:46 PM org.springframework.jms.listener.DefaultMessageListenerContainer refreshConnectionUntilSuccessful
WARNING: Could not refresh JMS Connection for destination 'queue:///Q_SAA' - retrying in 5000 ms. Cause: JMSWMQ0018: Failed to connect to queue manager 'QM_SAA' with connection mode 'Client' and host name '10.24.198.91'.; nested exception is com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2063' ('MQRC_SECURITY_ERROR').
Feb 8, 2013 5:34:51 PM org.springframework.jms.listener.DefaultMessageListenerContainer refreshConnectionUntilSuccessful
WARNING: Could not refresh JMS Connection for destination 'queue:///Q_SAA' - retrying in 5000 ms. Cause: JMSWMQ0018: Failed to connect to queue manager 'QM_SAA' with connection mode 'Client' and host name '10.24.198.91'.; nested exception is com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2063' ('MQRC_SECURITY_ERROR').
Feb 8, 2013 5:34:56 PM org.springframework.jms.listener.DefaultMessageListenerContainer refreshConnectionUntilSuccessful
WARNING: Could not refresh JMS Connection for destination 'queue:///Q_SAA' - retrying in 5000 ms. Cause: JMSWMQ0018: Failed to connect to queue manager 'QM_SAA' with connection mode 'Client' and host name '10.24.198.91'.; nested exception is com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2063' ('MQRC_SECURITY_ERROR').
Feb 8, 2013 5:35:01 PM org.springframework.jms.listener.DefaultMessageListenerContainer refreshConnectionUntilSuccessful
WARNING: Could not refresh JMS Connection for destination 'queue:///Q_SAA' - retrying in 5000 ms. Cause: JMSWMQ0018: Failed to connect to queue manager 'QM_SAA' with connection mode 'Client' and host name '10.24.198.91'.; nested exception is com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2063' ('MQRC_SECURITY_ERROR').
Feb 8, 2013 5:35:06 PM org.springframework.jms.listener.DefaultMessageListenerContainer refreshConnectionUntilSuccessful
WARNING: Could not refresh JMS Connection for destination 'queue:///Q_SAA' - retrying in 5000 ms. Cause: JMSWMQ0018: Failed to connect to queue manager 'QM_SAA' with connection mode 'Client' and host name '10.24.198.91'.; nested exception is com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2063' ('MQRC_SECURITY_ERROR').
Feb 8, 2013 5:35:11 PM org.springframework.jms.listener.DefaultMessageListenerContainer refreshConnectionUntilSuccessful
WARNING: Could not refresh JMS Connection for destination 'queue:///Q_SAA' - retrying in 5000 ms. Cause: JMSWMQ0018: Failed to connect to queue manager 'QM_SAA' with connection mode 'Client' and host name '10.24.198.91'.; nested exception is com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2063' ('MQRC_SECURITY_ERROR').
Feb 8, 2013 5:35:16 PM org.springframework.jms.listener.DefaultMessageListenerContainer refreshConnectionUntilSuccessful
WARNING: Could not refresh JMS Connection for destination 'queue:///Q_SAA' - retrying in 5000 ms. Cause: JMSWMQ0018: Failed to connect to queue manager 'QM_SAA' with connection mode 'Client' and host name '10.24.198.91'.; nested exception is com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2063' ('MQRC_SECURITY_ERROR').
Feb 8, 2013 5:35:21 PM org.springframework.jms.listener.DefaultMessageListenerContainer refreshConnectionUntilSuccessful
WARNING: Could not refresh JMS Connection for destination 'queue:///Q_SAA' - retrying in 5000 ms. Cause: JMSWMQ0018: Failed to connect to queue manager 'QM_SAA' with connection mode 'Client' and host name '10.24.198.91'.; nested exception is com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2063' ('MQRC_SECURITY_ERROR').
Feb 8, 2013 5:35:26 PM org.springframework.jms.listener.DefaultMessageListenerContainer refreshConnectionUntilSuccessful
WARNING: Could not refresh JMS Connection for destination 'queue:///Q_SAA' - retrying in 5000 ms. Cause: JMSWMQ0018: Failed to connect to queue manager 'QM_SAA' with connection mode 'Client' and host name '10.24.198.91'.; nested exception is com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2063' ('MQRC_SECURITY_ERROR').
Feb 8, 2013 5:35:31 PM org.springframework.jms.listener.DefaultMessageListenerContainer refreshConnectionUntilSuccessful
WARNING: Could not refresh JMS Connection for destination 'queue:///Q_SAA' - retrying in 5000 ms. Cause: JMSWMQ0018: Failed to connect to queue manager 'QM_SAA' with connection mode 'Client' and host name '10.24.198.91'.; nested exception is com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2063' ('MQRC_SECURITY_ERROR').
Feb 8, 2013 5:35:32 PM org.apache.coyote.http11.Http11Protocol pause
INFO: Pausing Coyote HTTP/1.1 on http-8080
Feb 8, 2013 5:35:33 PM org.apache.catalina.core.StandardService stop
INFO: Stopping service Catalina
Feb 8, 2013 5:35:33 PM org.springframework.context.support.AbstractApplicationContext doClose
INFO: Closing Root WebApplicationContext: startup date Fri Feb 08 17:34:35 IST 2013; root of context hierarchy
Feb 8, 2013 5:35:33 PM org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup stop
INFO: Stopping beans in phase 2147483647
Feb 8, 2013 5:35:36 PM org.springframework.beans.factory.support.DefaultSingletonBeanRegistry destroySingletons
INFO: Destroying singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@e1bdb58: defining beans msgSender,msgReceiver,jmsConnectionFactory,destinationQueue,jmsDestinationResolver,jmsQueueTemplate,listenerContainer; root of factory hierarchy
Feb 8, 2013 5:35:36 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/consumer] appears to have started a thread named WebSphere MQ Trace Monitor but has failed to stop it. This is very likely to create a memory leak.
Feb 8, 2013 5:35:36 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/consumer] appears to have started a thread named JMSCCThreadPoolMaster but has failed to stop it. This is very likely to create a memory leak.
Feb 8, 2013 5:35:36 PM org.apache.catalina.loader.WebappClassLoader clearThreadLocalMap
SEVERE: The web application [/consumer] created a ThreadLocal with key of type http://java.lang.ThreadLocal (value java.lang.ThreadLocal@f7f0d94) and a value of type http://com.ibm.mq.jmqi.system.JmqiComponentTls[] (value [Lcom.ibm.mq.jmqi.system.JmqiComponentTls;@5e54777e) but failed to remove it when the web application was stopped. This is very likely to create a memory leak.
Feb 8, 2013 5:35:37 PM org.apache.coyote.http11.Http11Protocol destroy
INFO: Stopping Coyote HTTP/1.1 on http-8080
Updated on 2013-02-22T11:29:14Z at 2013-02-22T11:29:14Z by fjb_saper
  • SystemAdmin
    SystemAdmin
    8523 Posts

    Re: Tomcat+SpringJms+WebsphereMq

    ‏2013-02-10T22:05:44Z  
    > WARNING: Could not refresh JMS Connection for destination 'queue:///Q_SAA' - retrying in 5000 ms. Cause: JMSWMQ0018: Failed to connect to queue manager 'QM_SAA' with connection mode 'Client' and host name '10.24.198.91'.; nested exception is com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2063' ('MQRC_SECURITY_ERROR').

    Did you look up MQRC_SECURITY_ERROR in the WMQ Infocenter?
    http://pic.dhe.ibm.com/infocenter/wmqv7/v7r5/topic/com.ibm.mq.doc/fm12650_.htm

    Did you check the queue manager error logs or security manager logs?

    HTH, G.
  • mbw
    mbw
    50 Posts

    Re: Tomcat+SpringJms+WebsphereMq

    ‏2013-02-11T11:18:35Z  
    > WARNING: Could not refresh JMS Connection for destination 'queue:///Q_SAA' - retrying in 5000 ms. Cause: JMSWMQ0018: Failed to connect to queue manager 'QM_SAA' with connection mode 'Client' and host name '10.24.198.91'.; nested exception is com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2063' ('MQRC_SECURITY_ERROR').

    Did you look up MQRC_SECURITY_ERROR in the WMQ Infocenter?
    http://pic.dhe.ibm.com/infocenter/wmqv7/v7r5/topic/com.ibm.mq.doc/fm12650_.htm

    Did you check the queue manager error logs or security manager logs?

    HTH, G.
    Hello;

    What level of queuemanager are you connecting to here? Could be the enhanced out-of-the-box security of WMQ 7.5.

    Some good discussion here on that topic http://stackoverflow.com/questions/12108372/issues-with-connecting-to-ibm-mq-7-5-using-java

    Matthew B Whitehttp://about.me/matthewbwhite
  • SystemAdmin
    SystemAdmin
    8523 Posts

    Re: Tomcat+SpringJms+WebsphereMq

    ‏2013-02-11T11:33:51Z  
    • mbw
    • ‏2013-02-11T11:18:35Z
    Hello;

    What level of queuemanager are you connecting to here? Could be the enhanced out-of-the-box security of WMQ 7.5.

    Some good discussion here on that topic http://stackoverflow.com/questions/12108372/issues-with-connecting-to-ibm-mq-7-5-using-java

    Matthew B Whitehttp://about.me/matthewbwhite
    CHLAUTH will give you a 2035 (MQRC_NOT_AUTHORIZED) not a 2063 (MQRC_SECURITY_ERROR). Read the help here if you believe it is CHLAUTH.

    https://www.ibm.com/developerworks/mydeveloperworks/blogs/aimsupport/entry/blocked_by_chlauth_why?lang=en

    Either way - we want to see what the error log says.

    Cheers
    Morag
  • SystemAdmin
    SystemAdmin
    8523 Posts

    Re: Tomcat+SpringJms+WebsphereMq

    ‏2013-02-13T06:30:14Z  
    CHLAUTH will give you a 2035 (MQRC_NOT_AUTHORIZED) not a 2063 (MQRC_SECURITY_ERROR). Read the help here if you believe it is CHLAUTH.

    https://www.ibm.com/developerworks/mydeveloperworks/blogs/aimsupport/entry/blocked_by_chlauth_why?lang=en

    Either way - we want to see what the error log says.

    Cheers
    Morag
    This is error log info. How to achieve resolve this...somebody please suggest.


    amqzfubn.c : 3827
    2/13/2013 11:05:20 - Process(1496.2) User(MUSR_MQADMIN) Program(amqzlaa0.exe)
    AMQ8079: Access was denied when attempting to retrieve group membership
    information for user 'in-kamalr$@internal'.

    EXPLANATION:
    WebSphere MQ, running with the authority of user 'musr_mqadmin@in-kamalr', was
    unable to retrieve group membership information for the specified user.
    ACTION:
    Ensure Active Directory access permissions allow user 'musr_mqadmin@in-kamalr'
    to read group memberships for user 'in-kamalr$@internal'. To retrieve group
    membership information for a domain user, MQ must run with the authority of a
    domain user.
    amqzfubn.c : 3827
    2/13/2013 11:05:25 - Process(1496.2) User(MUSR_MQADMIN) Program(amqzlaa0.exe)
    AMQ8079: Access was denied when attempting to retrieve group membership
    information for user 'in-kamalr$@internal'.

    EXPLANATION:
    WebSphere MQ, running with the authority of user 'musr_mqadmin@in-kamalr', was
    unable to retrieve group membership information for the specified user.
    ACTION:
    Ensure Active Directory access permissions allow user 'musr_mqadmin@in-kamalr'
    to read group memberships for user 'in-kamalr$@internal'. To retrieve group
    membership information for a domain user, MQ must run with the authority of a
    domain user.
    amqzfubn.c : 3827
    2/13/2013 11:05:30 - Process(1496.2) User(MUSR_MQADMIN) Program(amqzlaa0.exe)
    AMQ8079: Access was denied when attempting to retrieve group membership
    information for user 'in-kamalr$@internal'.

    EXPLANATION:
    WebSphere MQ, running with the authority of user 'musr_mqadmin@in-kamalr', was
    unable to retrieve group membership information for the specified user.
    ACTION:
    Ensure Active Directory access permissions allow user 'musr_mqadmin@in-kamalr'
    to read group memberships for user 'in-kamalr$@internal'. To retrieve group
    membership information for a domain user, MQ must run with the authority of a
    domain user.
    amqzfubn.c : 3827
  • fjb_saper
    fjb_saper
    177 Posts

    Re: Tomcat+SpringJms+WebsphereMq

    ‏2013-02-22T11:29:14Z  
    This is error log info. How to achieve resolve this...somebody please suggest.


    amqzfubn.c : 3827
    2/13/2013 11:05:20 - Process(1496.2) User(MUSR_MQADMIN) Program(amqzlaa0.exe)
    AMQ8079: Access was denied when attempting to retrieve group membership
    information for user 'in-kamalr$@internal'.

    EXPLANATION:
    WebSphere MQ, running with the authority of user 'musr_mqadmin@in-kamalr', was
    unable to retrieve group membership information for the specified user.
    ACTION:
    Ensure Active Directory access permissions allow user 'musr_mqadmin@in-kamalr'
    to read group memberships for user 'in-kamalr$@internal'. To retrieve group
    membership information for a domain user, MQ must run with the authority of a
    domain user.
    amqzfubn.c : 3827
    2/13/2013 11:05:25 - Process(1496.2) User(MUSR_MQADMIN) Program(amqzlaa0.exe)
    AMQ8079: Access was denied when attempting to retrieve group membership
    information for user 'in-kamalr$@internal'.

    EXPLANATION:
    WebSphere MQ, running with the authority of user 'musr_mqadmin@in-kamalr', was
    unable to retrieve group membership information for the specified user.
    ACTION:
    Ensure Active Directory access permissions allow user 'musr_mqadmin@in-kamalr'
    to read group memberships for user 'in-kamalr$@internal'. To retrieve group
    membership information for a domain user, MQ must run with the authority of a
    domain user.
    amqzfubn.c : 3827
    2/13/2013 11:05:30 - Process(1496.2) User(MUSR_MQADMIN) Program(amqzlaa0.exe)
    AMQ8079: Access was denied when attempting to retrieve group membership
    information for user 'in-kamalr$@internal'.

    EXPLANATION:
    WebSphere MQ, running with the authority of user 'musr_mqadmin@in-kamalr', was
    unable to retrieve group membership information for the specified user.
    ACTION:
    Ensure Active Directory access permissions allow user 'musr_mqadmin@in-kamalr'
    to read group memberships for user 'in-kamalr$@internal'. To retrieve group
    membership information for a domain user, MQ must run with the authority of a
    domain user.
    amqzfubn.c : 3827
    The error is quite clear:

    2/13/2013 11:05:20 - Process(1496.2) User(MUSR_MQADMIN) Program(amqzlaa0.exe)
    AMQ8079: Access was denied when attempting to retrieve group membership
    information for user 'in-kamalr$@internal'.

    EXPLANATION:
    WebSphere MQ, running with the authority of user 'musr_mqadmin@in-kamalr', was
    unable to retrieve group membership information for the specified user.
    ACTION:
    Ensure Active Directory access permissions allow user 'musr_mqadmin@in-kamalr'
    to read group memberships for user 'in-kamalr$@internal'. To retrieve group
    membership information for a domain user, MQ must run with the authority of a
    domain user.

    The MQ service user must have authorization to check the domain group membership if you authorized a domain group.