连接与JMS经纪人失败



我有一个玻璃鱼服务器(4.1.2(,然后遵循本教程,我将Apache ActiveMQ集成到服务器上。之后,我开发了一个独立的客户端,以根据同一教程的这一部分发送消息传递。结束于此,我遵循本教程的最后一部分,以开发一个MessagedrivenBean,听取之前使用的队列。

一切都很好。ActiveMQ也在运行。但是,每当我部署EJB时,以下内容都在我的GF服务器日志中记录:

Info:   visiting unvisited references
Info:   visiting unvisited references
Info:   JTS5014: Recoverable JTS instance, serverId = [3700]
Warning:   RAR8000 : The method setDestinationLookup is not present in the class : org.apache.activemq.ra.ActiveMQActivationSpec
Warning:   RAR7097: No setter method present for the property destinationLookup in the class org.apache.activemq.ra.ActiveMQActivationSpec
Info:   2017-06-06 11:43:00,675 [min-listener(1)] INFO  ActiveMQEndpointWorker         - Starting
Info:   2017-06-06 11:43:00,682 [ad-pool-1; w: 4] INFO  ActiveMQEndpointWorker         - Establishing connection to broker [vm://0.0.0.0:6616]
Info:   WELD-000900: 2.2.13 (Final)
WARN:   WELD-001700: Interceptor annotation class javax.ejb.PostActivate not found, interception based on it is not enabled
WARN:   WELD-001700: Interceptor annotation class javax.ejb.PrePassivate not found, interception based on it is not enabled
WARN:   WELD-000411: Observer method [BackedAnnotatedMethod] public org.glassfish.jms.injection.JMSCDIExtension.processAnnotatedType(@Observes ProcessAnnotatedType<Object>) receives events for all annotated types. Consider restricting events using @WithAnnotations or a generic type with bounds.
WARN:   WELD-000411: Observer method [BackedAnnotatedMethod] org.glassfish.sse.impl.ServerSentEventCdiExtension.processAnnotatedType(@Observes ProcessAnnotatedType<Object>, BeanManager) receives events for all annotated types. Consider restricting events using @WithAnnotations or a generic type with bounds.
WARN:   WELD-000411: Observer method [BackedAnnotatedMethod] private org.glassfish.jersey.ext.cdi1x.internal.CdiComponentProvider.processAnnotatedType(@Observes ProcessAnnotatedType<Object>) receives events for all annotated types. Consider restricting events using @WithAnnotations or a generic type with bounds.
Info:   AmdMDB was successfully deployed in 5.290 milliseconds.
Info:   2017-06-06 11:43:31,695 [ad-pool-1; w: 4] ERROR ActiveMQEndpointWorker         - Failed to connect to broker [vm://0.0.0.0:6616]: Could not create Transport. Reason: java.net.URISyntaxException: Illegal character in scheme name at index 0: 0.0.0.0:6616
javax.jms.JMSException: Could not create Transport. Reason: java.net.URISyntaxException: Illegal character in scheme name at index 0: 0.0.0.0:6616
    at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:36)
    at org.apache.activemq.ActiveMQConnectionFactory.createTransport(ActiveMQConnectionFactory.java:260)
    at org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:273)
    at org.apache.activemq.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:194)
    at org.apache.activemq.ra.ActiveMQResourceAdapter.makeConnection(ActiveMQResourceAdapter.java:132)
    at org.apache.activemq.ra.ActiveMQEndpointWorker$1.run(ActiveMQEndpointWorker.java:109)
    at com.sun.enterprise.connectors.work.OneWork.doWork(OneWork.java:107)
    at com.sun.corba.ee.impl.threadpool.ThreadPoolImpl$WorkerThread.performWork(ThreadPoolImpl.java:497)
    at com.sun.corba.ee.impl.threadpool.ThreadPoolImpl$WorkerThread.run(ThreadPoolImpl.java:540)
Caused by: java.net.URISyntaxException: Illegal character in scheme name at index 0: 0.0.0.0:6616
    at java.net.URI$Parser.fail(URI.java:2848)
    at java.net.URI$Parser.checkChars(URI.java:3021)
    at java.net.URI$Parser.checkChar(URI.java:3031)
    at java.net.URI$Parser.parse(URI.java:3047)
    at java.net.URI.<init>(URI.java:588)
    at org.apache.activemq.util.URISupport.parseComposite(URISupport.java:390)
    at org.apache.activemq.util.URISupport.parseComposite(URISupport.java:279)
    at org.apache.activemq.transport.vm.VMTransportFactory.doCompositeConnect(VMTransportFactory.java:63)
    at org.apache.activemq.transport.vm.VMTransportFactory.doConnect(VMTransportFactory.java:54)
    at org.apache.activemq.transport.TransportFactory.connect(TransportFactory.java:64)
    at org.apache.activemq.ActiveMQConnectionFactory.createTransport(ActiveMQConnectionFactory.java:258)
    ... 7 more
Info:   2017-06-06 11:43:31,697 [ad-pool-1; w: 4] ERROR ActiveMQEndpointWorker         - Endpoint will try to reconnect to the JMS broker in 30 seconds
Info:   2017-06-06 11:43:40,060 [jb-thread-pool1] INFO  ActiveMQEndpointWorker         - Stopping

最后停止是由于我所做的不依赖造成的,因为重新连接尝试每三十秒都会出现同样的错误。

我不太确定错误在哪里。端口为6616,顺便说一句,这是ActiveMQ正在运行的实际端口,因为另一个过程正在使用端口61616。

您能给我一个暗示,在哪里寻找错误?

顺便说一句:当我与独立客户端一起向队列发送消息时,没有例外(所以这似乎在起作用。(但是,我也无法通过ActiveMQ Admin Console发送消息服务器。

非常感谢...

根据http://activemq.apache.org/vm-transport-reference.html,当使用ActiveMQ VM Tranport时,它应该是" VM://"之后的经纪人名称。。

如果要使用IP和端口,请以这种方式进行配置:

vm:(broker:(tcp://localhost:6000)?persistent=false)?marshal=false

相关内容

  • 没有找到相关文章

最新更新