Closed arinban closed 14 years ago
arinban
commented
6 years ago arinban
commented
18 years ago @glassfishrobot Commented Reported by markmundy
arinban
commented
18 years ago @glassfishrobot Commented markmundy said: Hope I have submitted this correctly!
arinban
commented
18 years ago @glassfishrobot Commented rampsarathy said: This is not a issue with generic jms ra, a bug has been created across application server for the same http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6472921
This issue is also not reproducible with glassfish.
arinban
commented
18 years ago @glassfishrobot Commented Was assigned to binod
arinban
commented
7 years ago @glassfishrobot Commented This issue was imported from java.net JIRA GENERICJMSRA-28
arinban
commented
14 years ago @glassfishrobot Commented Marked as won't fix on Sunday, September 5th 2010, 8:21:08 pm
It has been discovered that in order to allow a different jndiproperty to be specified to lookup connection factories in LDAP with AS 8.1 U2 SP6 and higher a modification to the GRA ra.xml is required. (Bug in the Application Server).
When this is done overriding of the jndi properties at a connection pool level works fine.
However it has been discovered that in order to then utilise an admin object to be looked up from the base GRA config jndi property it too has to be overridden which should not be the case.
To reproduce:
1. Modify GRA ra.xml to include tag and deploy to AS 8.1 U2 with a jndi property for an ldap dn where the queue destinations are locatd BUT NOT THE Qcf's 2. Create a connector resource and connection pool with overridden property pointing to different LDAP node where QCF is located. 3. Attempt to utilise the pool and admin object from a simple application and it will be necessary to override the admin object definition with an additional jndi property rather than relying on the base GRA config.
Environment
Operating System: Solaris Platform: Sun
Affected Versions
[v1.5]