春季3.0懒惰 - 不为DefaultMessageListEnercontainer感到荣幸吗?
-
08-10-2019 - |
题
我已经为JMS设置了弹簧配置。事情正常,除了我似乎无法将其延伸到懒惰的负载(请注意以下代码中的默认液体内置)。如果我从下面的配置中评论JMScontainer(DMLC),则懒惰加载可根据预期工作。否则,它将实例化DMLC,从而创建队列和连接工厂。
我想念什么?
JMScontext.xml:
<?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:p="http://www.springframework.org/schema/p"
xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd"
default-lazy-init="true">
<bean id="jndiTemplate" class="org.springframework.jndi.JndiTemplate">
<property name="environment">
<props>
<prop key="java.naming.factory.initial">weblogic.jndi.WLInitialContextFactory</prop>
<prop key="java.naming.provider.url">t3:localhost:7001</prop>
</props>
</property>
</bean>
<bean id="queue" class="org.springframework.jndi.JndiObjectFactoryBean"
p:jndiTemplate-ref="jndiTemplate" p:jndiName="jms/queue"/>
<bean id="connectionFactory" class="org.springframework.jndi.JndiObjectFactoryBean"
p:jndiTemplate-ref="jndiTemplate" p:jndiName="jms/connectionfactory"/>
<bean id="jmsDestinationResolver" class="org.springframework.jms.support.destination.JndiDestinationResolver"
p:jndiTemplate-ref="jndiTemplate" p:cache="true" />
<bean id="jmsContainer" class="org.springframework.jms.listener.DefaultMessageListenerContainer"
p:autoStartup="false"
p:destination-ref="queue"
p:destinationResolver-ref="jmsDestinationResolver"
p:connectionFactory-ref="connectionFactory"
p:messageListener-ref="queueListener" />
<bean id="queueListener" class="com.blah.QueueListener"/>
</beans>
和我用来驱动它的测试,dummytest.java:
package blah;
import org.junit.Test;
import org.junit.runner.RunWith;
import org.springframework.test.context.ContextConfiguration;
import org.springframework.test.context.junit4.SpringJUnit4ClassRunner;
@RunWith(SpringJUnit4ClassRunner.class)
@ContextConfiguration("classpath:jmsContext.xml")
public class DummyTest {
@Test
public void shouldDoSomething() {
}
}
当jmscontainer发表评论时,上面的测试通过。否则,我明白了:
java.lang.IllegalStateException: Failed to load ApplicationContext
Caused by: org.springframework.beans.factory.BeanCreationException:
Error creating bean with name 'jmsContainer' defined in class path resource [com/blah/config/jmsContext.xml]:
Cannot resolve reference to bean 'connectionFactory' while setting bean property 'connectionFactory';
nested exception is org.springframework.beans.factory.BeanCreationException:
Error creating bean with name 'connectionFactory' defined in class path resource [com/blah/config/jmsContext.xml]:
Invocation of init method failed; nested exception is javax.naming.NameNotFoundException:
Exception in lookup.: `jms/connectionfactory' could not be found.
[Root exception is weblogic.corba.cos.naming.NamingContextAnyPackage.NotFound: IDL:weblogic/corba/cos/naming/NamingContextAny/NotFound:1.0]
“ ConnectionFactory” Bean被实例化为“ JMScontainer”的依赖性,并且失败。随着“ JMScontainer”的评论,“ ConnectionFactory”不会实例化。
JMS代码工作正常,但是我故意重命名了JNDI名称,因此我可以看到何时开始工作。
解决方案
好的,这很晦涩,但是 DefaultMessageListenerContainer
实现 Lifecycle
接口和实现此目标的bean与上下文自己的生命周期相关 - 当上下文启动时, Lifecycle
- 启用豆是初始化的,并开始。这意味着您的懒惰配置本质上被忽略了。
其他提示
解决方案是使用autoStartup作为false。请参阅下面的代码。
<bean id="listenerContainer"
class="org.springframework.jms.listener.DefaultMessageListenerContainer">
........
<property name="autoStartup" value="false"/>
</bean>
〜Shyam
不隶属于 StackOverflow