Bug 779088 (SOA-1487) - JuddiRMIService overrides JNDI properties
Summary: JuddiRMIService overrides JNDI properties
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-1487
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: JBossESB
Version: 4.3 CP01
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.3 CP02
Assignee: Kevin Conner
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-09-11 08:45 UTC by Kevin Conner
Modified: 2009-09-25 15:31 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-09-25 15:31:20 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-1487 0 None None None Never

Description Kevin Conner 2009-09-11 08:45:43 UTC 
Date of First Response: 2009-09-24 22:13:59
project_key: SOA
Comment 1 Kevin Conner 2009-09-11 08:46:03 UTC 
Link: Added: This issue depends JBESB-2819
Comment 2 Kevin Conner 2009-09-16 10:27:31 UTC 
The JuddiRMIService previously initialised the JNDI properties when started, using the values within its configuration file.

It should be possible to verify this no longer occurs by checking the properties through the jmx-console, the SystemProperties bean method showAll, and searching for the following properties.

java.naming.factory.initial, java.naming.provider.url, java.naming.factory.url.pkgs.

Their values should differ from the ones within the juddi configuration file.
Comment 3 Dana Mison 2009-09-25 02:13:59 UTC 
added as resolved in 4.3.CP02:

JBESB-2819
The JBoss application server's JNDI properties were being set by the JuddiRMIService.  This had the side-effect of over-writing any optimizations made in the application server's configuration.  JuddiRMIService no longer does this.  The JNDI properties for jUDDI and the JBoss application server can be maintained independently.
Comment 4 Kevin Conner 2009-09-25 15:31:09 UTC 
From jmx-console

java.naming.factory.initial	org.jnp.interfaces.NamingContextFactory
java.naming.factory.url.pkgs	org.jboss.naming:org.jnp.interfaces

java.naming.provider.url is no longer set.
Note You need to log in before you can comment on or make changes to this bug.