jms - Weblogic Deployment Unable to Resolve Local Queue -
we have spring-based application failing deploy on weblogic 10.3 container. upon deployment, application attempts 2 local jms queues within weblogic container's jms module and, when deployment takes place, application locates 1 local queue okay not other.
both queues configured same except names different. why application locate 1 queue okay not other???
i've checked queue names jndi names many times on , can't see spelling errors or that.
i have turned trace logging on , can see connection factory used both queues same, spring jms configuration same both queues yet 1 finds other not.
i don't know else check establish problem might be... ideas?
this error when fails 1 of queues in weblogic jndi tree:
caused by: javax.naming.namenotfoundexception: unable resolve 'queue_name'. resolved ''; remaining name 'queue_name' @ weblogic.jndi.internal.basicnamingnode.newnamenotfoundexception(basicnamingnode.java:1139)
ps: both queues have same subdeployment , same targets configured.
---- edited add artifact's spring xml configuration snippet below ----
<?xml version="1.0" encoding="utf-8"?> <beans xmlns="http://www.springframework.org/schema/beans" xmlns:xsi="http://www.w3.org/2001/xmlschema-instance" xmlns:context="http://www.springframework.org/schema/context" xmlns:tx="http://www.springframework.org/schema/tx" xmlns:security="http://www.springframework.org/schema/security" xmlns:lang="http://www.springframework.org/schema/lang" xsi:schemalocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-3.0.xsd http://www.springframework.org/schema/tx http://www.springframework.org/schema/tx/spring-tx-3.0.xsd http://www.springframework.org/schema/context http://www.springframework.org/schema/context/spring-context-3.0.xsd http://www.springframework.org/schema/security http://www.springframework.org/schema/security/spring-security-3.0.xsd http://www.springframework.org/schema/lang http://www.springframework.org/schema/lang/spring-lang-3.0.xsd"> <context:component-scan base-package="com.company.service" /> <bean id="jnditemplate" class="org.springframework.jndi.jnditemplate"> <property name="environment"> <props> <prop key="java.naming.factory.initial">weblogic.jndi.wlinitialcontextfactory</prop> </props> </property> </bean> <!-- message driven pojo (mdp) --> <bean id="messagelistener" class="com.company.service.controller.servicejmslistener" /> <!-- message listener container --> <bean id="jmscontainer" class="org.springframework.jms.listener.defaultmessagelistenercontainer"> <property name="connectionfactory" ref="queueconnectionfactory" /> <property name="destination" ref="inboundqueue" /> <property name="messagelistener" ref="messagelistener" /> <property name="concurrentconsumers" value="1" /> </bean> <!-- jndi connection factory --> <bean id="queueconnectionfactory" class="org.springframework.jndi.jndiobjectfactorybean"> <property name="jnditemplate"> <ref bean="jnditemplate" /> </property> <property name="jndiname"> <value>service_qcf</value> </property> </bean> <!-- queue listen --> <bean id="inboundqueue" class="org.springframework.jndi.jndiobjectfactorybean"> <property name="jnditemplate"> <ref bean="jnditemplate" /> </property> <property name="jndiname"> <value>queue_a</value> </property> </bean> <bean id="outboundqueue" class="org.springframework.jndi.jndiobjectfactorybean"> <property name="jnditemplate"> <ref bean="jnditemplate" /> </property> <property name="jndiname"> <value>queue_b</value> </property> </bean> <bean id="queuetemplate" class="org.springframework.jms.core.jmstemplate"> <property name="connectionfactory"> <ref bean="queueconnectionfactory" /> </property> <property name="destinationresolver"> <ref bean="jmsdestinationresolver" /> </property> </bean> <bean id="jmsdestinationresolver" class="org.springframework.jms.support.destination.jndidestinationresolver"> <property name="jnditemplate"> <ref bean="jnditemplate" /> </property> <property name="cache"> <value>true</value> </property> </bean> </beans>
can have jdni tree in running server check if queue created or not, , jndi name bound ? use admin console purpose.
Comments
Post a Comment