java - JMS MQ binding problem -
i have strange issue jms binding on mq queue mdb
the message-driven ejb:
crbeventmessageasynchronousservice
unable connect jms destination:queue.contratto.crb.input.publicqueue
. error was:
javax.jms.jmsexception
:mqjms1017
: non-local mq queue not valid receiving or browsing>
i checked on queuemanager
, mq queue defined local , not remote said exception.
it may top-most queue application opening reading defined locally. however, queue wmq resolving not. example, if define local alias on remote clustered queue, resolved queue non-local. possible cause queue intend open output being opened input well. quite common.
finally, common wmq client connected different queue manager expected. example, connection qmgra , queue object specifies fully-qualified name queue@qmgrb. though queue lives on qmgrb , jndi object specifies queue manager name, connection on qmgra resolves transmit queue , therefore sees non-local.
one of best ways nail kind of error down in dev use supportpac ma0w. supportpac runs api exit or channel exit , lists in human-readable language of api calls , of options selected call. unequivocally show object name opened, resolved , options used.
alternatively, can turn on trace using strmqtrc. don't forget disable endmqtrc when done! these traces enabled , disabled on qmgr server , trace wmq api calls. there equivalent traces run on client side these may not show level of detail require.
finally, advisable print exceptions linked jms exceptions. jms exception multi-level data structure linked exception holds provider-specific values. example, jms security exception might wmq authorization error. again, might error in keystore or filesystem. if linked exception not show wmq 2035 reason code, it's not wmq security error. infocenter describes how print linked exception data in section named exceptions in websphere mq classes jms.
note i've provided links v7.0 wmq docs. if coding in v6 these may not accurate , want in v6.0 infocenter instead. since v6.0 of wmq end-of-life of september 2011 highly recommended new development on v7.0. if need v7.0 client downloadable supportpac mqc7 , backward compatible v6.0 wmq servers.
Comments
Post a Comment