Jms 在activemq上调试单元测试时获取nullpointer异常
我有下面的单元测试,它给了我一个空指针异常。调试器将转到创建连接工厂的行后面的finally块。以下是测试:Jms 在activemq上调试单元测试时获取nullpointer异常,jms,activemq,junit4,Jms,Activemq,Junit4,我有下面的单元测试,它给了我一个空指针异常。调试器将转到创建连接工厂的行后面的finally块。以下是测试: @Test public void receiveMessage() throws Exception { MessageConsumer consumer = null; ConnectionFactory connectionFactory = null; Connection connection = null
@Test
public void receiveMessage() throws Exception {
MessageConsumer consumer = null;
ConnectionFactory connectionFactory = null;
Connection connection = null;
Session session = null;
Destination destination = null;
try {
connectionFactory = new ActiveMQConnectionFactory(
"tcp://localhost:61616");
connection = connectionFactory.createConnection("username","pwd");
connection.start();
session = connection.createSession(true,
Session.AUTO_ACKNOWLEDGE);
destination = session
.createQueue("myQueue");
logger.info("Starting consumer");
consumer = session
.createConsumer(destination);
Message m = consumer.receive();
logger.info("Received message:" + m);
}
} catch (Exception e) {
logger.error("", e);
} finally {
consumer.close();
session.close();
connection.stop();
connection.close();
}
}
以下是堆栈跟踪:
位于的java.lang.NullPointerException
ClassName.receiveMessageClassName.java:62
在sun.reflect.NativeMethodAccessorImpl.invoke0Native方法在
sun.reflect.NativeMethodAccessorImpl.invokeUnknown源位于
sun.reflect.DelegatingMethodAccessorImpl.invokeUnknown源位于
java.lang.reflect.Method.invokeUnknown源代码位于
org.junit.runners.model.FrameworkMethod$1.runReflectVeCallFrameworkMethod.java:47
在
org.junit.internal.runners.model.ReflectiveCallable.runReflectiveCallable.java:12
在
org.junit.runners.model.FrameworkMethod.invokeeexplosivelyframeworkmethod.java:44
在
org.junit.internal.runners.statements.InvokeMethod.evaluateInvokeMethod.java:17
在
org.junit.internal.runners.statements.runafter.evaluaterUnders.java:27
位于org.junit.runners.ParentRunner.runLeafParentRunner.java:271处
org.junit.runners.BlockJUnit4ClassRunner.runChildBlockJUnit4ClassRunner.java:70
在
org.junit.runners.BlockJUnit4ClassRunner.runChildBlockJUnit4ClassRunner.java:50
位于org.junit.runners.ParentRunner$3.runParentRunner.java:238处
org.junit.runners.ParentRunner$1.scheduleParentRunner.java:63 at
org.junit.runners.ParentRunner.runChildrenParentRunner.java:236 at
org.junit.runners.ParentRunner.access$000ParentRunner.java:53
org.junit.runners.ParentRunner$2.evaluateParentRunner.java:229 at
org.junit.runners.ParentRunner.runParentRunner.java:309 at
org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.runJUnit4TestReference.java:50
在
org.eclipse.jdt.internal.junit.runner.TestExecution.runTestExecution.java:38
在
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTestsRemoteTestRunner.java:459
在
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTestsRemoteTestRunner.java:675
在
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runRemoteTestRunner.java:382
在
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.mainRemoteTestRunner.java:192
在单元测试中,不应使用实际连接,即在单元测试用例中尝试连接到BrokerURL,这不是单元测试的目的 在这种情况下,需要使用Easymock+Powermock或Mockito等库模拟外部连接 关于空指针异常,您的代理启动了吗?用户名和密码正确,请检查这些