在Spring4 + STOMP + SockJS應用程序中配置外部代理（RabbitMQ）

Question

我正在開發一個使用Spring4消息傳遞和使用SockJS實現的STOMP開發的聊天應用程序。

config.enableSimpleBroker("/queue/", "/topic/"); 

但是，現在我們必須使用相同的應用程序中使用外部代理（RabbitMQ的）要求：當我使用簡單的Message Broker應用程序工作正常。對於這一點，我改變了上面的代碼與以下：

// config.enableSimpleBroker("/queue/", "/topic/"); 
config.enableStompBrokerRelay("/queue", "/topic"); 

我的客戶端使用如下STOMP客戶端連接：

stompClient.connect({}, function(frame) { 
    // subscribe to topics or queues and other stuff 
}); 

但是，我得到了以下異常：

2014-05-09 11:13:13,567 ERROR  o.s.s.support.TaskUtils$LoggingErrorHandler - Unexpected error occurred in scheduled task. 
org.springframework.messaging.MessageDeliveryException: Message broker is not active. 
at org.springframework.messaging.simp.stomp.StompBrokerRelayMessageHandler.handleMessageInternal(StompBrokerRelayMessageHandler.java:378) ~[spring-messaging-4.0.3.RELEASE.jar:4.0.3.RELEASE] 
at org.springframework.messaging.simp.broker.AbstractBrokerMessageHandler.handleMessage(AbstractBrokerMessageHandler.java:171) ~[spring-messaging-4.0.3.RELEASE.jar:4.0.3.RELEASE] 
at org.springframework.messaging.support.ExecutorSubscribableChannel.sendInternal(ExecutorSubscribableChannel.java:64) ~[spring-messaging-4.0.3.RELEASE.jar:4.0.3.RELEASE] 
at org.springframework.messaging.support.AbstractMessageChannel.send(AbstractMessageChannel.java:116) ~[spring-messaging-4.0.3.RELEASE.jar:4.0.3.RELEASE] 
at org.springframework.messaging.support.AbstractMessageChannel.send(AbstractMessageChannel.java:98) ~[spring-messaging-4.0.3.RELEASE.jar:4.0.3.RELEASE] 
at org.springframework.messaging.simp.SimpMessagingTemplate.doSend(SimpMessagingTemplate.java:129) ~[spring-messaging-4.0.3.RELEASE.jar:4.0.3.RELEASE] 
at org.springframework.messaging.simp.SimpMessagingTemplate.doSend(SimpMessagingTemplate.java:48) ~[spring-messaging-4.0.3.RELEASE.jar:4.0.3.RELEASE] 
at org.springframework.messaging.core.AbstractMessageSendingTemplate.send(AbstractMessageSendingTemplate.java:93) ~[spring-messaging-4.0.3.RELEASE.jar:4.0.3.RELEASE] 
at org.springframework.messaging.core.AbstractMessageSendingTemplate.convertAndSend(AbstractMessageSendingTemplate.java:146) ~[spring-messaging-4.0.3.RELEASE.jar:4.0.3.RELEASE] 
at org.springframework.messaging.core.AbstractMessageSendingTemplate.convertAndSend(AbstractMessageSendingTemplate.java:112) ~[spring-messaging-4.0.3.RELEASE.jar:4.0.3.RELEASE] 
at org.springframework.messaging.core.AbstractMessageSendingTemplate.convertAndSend(AbstractMessageSendingTemplate.java:106) ~[spring-messaging-4.0.3.RELEASE.jar:4.0.3.RELEASE] 
at com.attomic.chat.service.ActiveUserPinger.pingUsers(ActiveUserPinger.java:24) ~[ActiveUserPinger.class:na] 
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.7.0_05] 
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) ~[na:1.7.0_05] 
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.7.0_05] 
at java.lang.reflect.Method.invoke(Method.java:601) ~[na:1.7.0_05] 
at org.springframework.scheduling.support.ScheduledMethodRunnable.run(ScheduledMethodRunnable.java:65) ~[spring-context-4.0.3.RELEASE.jar:4.0.3.RELEASE] 
at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54) ~[spring-context-4.0.3.RELEASE.jar:4.0.3.RELEASE] 
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [na:1.7.0_05] 
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351) [na:1.7.0_05] 
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178) [na:1.7.0_05] 
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) [na:1.7.0_05] 
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [na:1.7.0_05] 
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [na:1.7.0_05] 
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [na:1.7.0_05] 
at java.lang.Thread.run(Thread.java:722) [na:1.7.0_05] 

我檢查了RabbitMQ，它已啓動並正在運行。該STOMP插件也安裝在RabbitMQ.I做工精細也試過如下：

1. config.enableStompBrokerRelay("/queue", "/topic").setSystemLogin("guest").setSystemPasscode("guest"); 
2. config.enableStompBrokerRelay("/queue", "/topic").setClientLogin("guest").setClientPasscode("guest"); 
3. config.enableStompBrokerRelay("/queue", "/topic").setRelayHost("localhost").setRelayPort("15672"); 

我已經做了相當多的搜索，但仍然未能解決這個問題。有人可以對此有所瞭解嗎？

Answer 1

經過一番研究和一些實驗，如預期的那樣，我發現問題出在客戶端。更改

stompClient.connect({}, function(frame) { 
    // subscribe to topics or queues and other stuff 
}); 

到

stompClient.connect('guest', 'guest', function(frame) { 
    // subscribe to topics or queues and other stuff 
}); 

工作就像一個魅力。在這裏，第一個參數客人是用戶名和第二個參數客人是的RabbitMQ服務器的密碼。因此，這裏的基本要點是，無論何時配置外部代理，您都需要傳遞服務器的用戶名和密碼。在簡單經紀人的情況下，不需要傳遞憑證。乾杯！！