Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.8.2.GA, 1.8.2.GA_P01
-
Fix Version/s: 1.8.2.GA_P02
-
Component/s: Enterprise Push Server
-
Labels:None
-
Environment:Tomcat 6.x, ActiveMQ 5.3.1, ICEfaces Core, ICEfaces EPS
-
Affects:Documentation (User Guide, Ref. Guide, etc.)
-
Workaround Exists:Yes
-
Workaround Description:Use ActiveMQ 5.3.0 instead as the latest supported version of ActiveMQ
Description
(Status-Line) HTTP/1.1 404 Not Found
Date Tue, 30 Mar 2010 22:33:16 GMT
X-Powered-By ICEfaces Enterprise Push Server, Thread Blocking Adapting Servlet
Set-Cookie JSESSIONID=AB83754579C85EAF672596FAA0387255.lntest8; Path=/eps
Content-Type text/plain;charset=UTF-8
Content-Length 0
Keep-Alive timeout=5, max=97
Connection Keep-Alive
There are no exceptions in the Tomcat and ActiveMQ logs.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
This seems to be due to ActiveMQ 5.3.1 not automatically being clustered where previous versions of ActiveMQ did. Though the documentation states it supports automatic clustering, I'll have to investigate why it isn't working for me.
The newer ActiveMQ 5.4.1 seems to have the same results as I had with 5.3.1.
Looks like a simple configuration change is all that is required. Ensure the [active-mq-home]/conf/activemq.xml file contains the following:
...
<networkConnectors>
<networkConnector name="default-nc" uri="multicast://default"/>
</networkConnectors>
<transportConnectors>
<transportConnector name="openwire" uri="tcp://0.0.0.0:61616" discoveryUri="multicast://default" />
</transportConnectors>
...
Note that the "default-nc" is new to the file, but the "openwire" is already there. It just needs the additional discoveryUri attribute. I'll need to update the documentation with this information.
Affects documentation.
Documentation has been updated at http://wiki.icesoft.domain/. Marking this one as FIXED.
Changed the Fix Version/s to 1.8.2.GA_P02