Issue Details (XML | Word | Printable)

Key: MULE-3567
Type: Patch submission Patch submission
Status: Open Open
Priority: Critical Critical
Assignee: Unassigned
Reporter: Yuen-Chi Lian
Votes: 0
Watchers: 0
Operations

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

getJndiContext of JndiConnector does not "renew" the provider URL

Created: 22/Jul/08 01:24 AM   Updated: 30/Nov/08 06:15 PM
Component/s: Core: Transports
Affects Version/s: 2.0.2
Fix Version/s: 2.1.x Backlog

Time Tracking:
Not Specified

File Attachments: 1. Java Source File AbstractJndiConnector.java (4 kB)
2. Java Source File AbstractJndiConnectorTestCase.java (1 kB)
3. Text File DIFF.txt (2 kB)


Labels:
User impact: Medium


 Description  « Hide
When you call the getJndiContext(jndiProviderUrl) method, supposed, the JNDI provider url is updated not just at the connector but also its value in the JNDI context. The latter is not updated however, see patch and test case for details.

I discovered this while writing a test case for RMI transport.



 All   Comments   Work Log   Change History   Transitions   FishEye      Sort Order: Ascending order - Click to sort in descending order
Ross Mason added a comment - 15/Nov/08 11:13 AM
Again, thanks for the patch!

Whoever takes this on, I think the JNDI Connext setup should happen in the doConnect method so we can also do reties if the server becomes unavailable