Issue Details (XML | Word | Printable)

Key: AMQ-950
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Minor Minor
Assignee: Unassigned
Reporter: Renaud Bruyeron
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
ActiveMQ

createConnector="false" has no effect on Tiger

Created: 02/Oct/06 05:11 AM   Updated: 03/Oct/06 03:12 AM
Return to search
Component/s: Broker
Affects Version/s: 4.1.0
Fix Version/s: 4.1.0

Time Tracking:
Not Specified

Environment: JDK 1.5.0_08


 Description  « Hide

On Tiger, activemq always creates a rmi connector on port 1099 no matter what I do with -Djavax.management... and <managementContext/>
In particular, setting createConnector="false" should prevent AMQ from setting up its own connector, but it does not.

The problem is in the findMBeanServer() method:
if (result == null && createMBeanServer) { result = createMBeanServer(); }
else { createConnector(result); }

result is not null on Tiger with useJmx="true", and createConnector is not protected by if(createConnector) like it is on the non-Tiger flow.
The fix (I think) is simply to do this:
if (result == null && createMBeanServer) { result = createMBeanServer(); } }
else {
if(createConnector){ createConnector(result); }
}



 All   Comments   Work Log   Change History   Subversion Commits   FishEye   Crucible      Sort Order: Ascending order - Click to sort in descending order
No related reviews found.