Use default provider URL in JMSReplication

Type: Bug
Status: Open
Priority: 3 Minor
Resolution:
Component/s: ehcache-jmsreplication
Labels:

Assignee:
Reporter: sourceforgetracker
Created: September 21, 2009
Votes: 0
Watchers: 1
Updated:
January 06, 2010
Resolved:

Attachments

carrja99 (2.00 k) text/plain ActiveMQJMSReplicationTest.patch
carrja99 (2.00 k) text/plain default-provider-url.patch

Description

The “providerURL” configuration attribute is mandatory. It should be optional and, in case it isn’t defined, it’ll use the default provider URL, which is the running application server itself.

We need this because in our company we can’t make this infrastructure configuration (application server’s URLs) inside the application and the JMS server is the application server itself. Sourceforge Ticket ID: 2841318 - Opened By: pperboires - 20 Aug 2009 19:01 UTC

Comments

Sourceforge Tracker 2009-09-21

I’ve developed a patch for this feature and it’s running fine in a clustered Weblogic AS 10.3. The code is attached. Comment by: pperboires - 20 Aug 2009 19:13 UTC

James Carr 2010-01-05

I went ahead and made the change myself. Just check to see if providerURL is null and if it is, don’t pass it to the intialContext. Essentially, the behavior varies amongst MQ implementations but as far as I know ActiveMQ and OracleAQ (at least) will fill a default in itself if one is not provided.

I’ve deployed this code on weblogic 10.3 and it works well.

James Carr 2010-01-05

Sorry… I uploaded the wrong patch. This one is correct.

Fiona OShea 2010-01-06

Assigning these issues to Greg, so that he can decide what to do with them.