Bug 158579 - alternative JNDI port not setup properly
Summary: alternative JNDI port not setup properly
Status: NEW
Alias: None
Product: WTP ServerTools
Classification: WebTools
Component: jst.server (show other bugs)
Version: 1.5   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Naci Dai CLA
QA Contact: Tim deBoer CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-09-25 11:16 EDT by J.W. Janssen CLA
Modified: 2007-04-20 02:45 EDT (History)
2 users (show)

See Also:

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

Note You need to log in before you can comment on or make changes to this bug.
Description J.W. Janssen CLA 2006-09-25 11:16:49 EDT 
When adding a JBoss server whose JNDI port is NOT the default of 1099, the restart and stop configuration of the server is not correctly configured.

The solution is to add "-s ${serverAddress}:${jndiPort}" as additional parameter in the programArguments of the stop container of the JBoss server definitions file (jboss.serverdef and/or jboss323.serverdef). 

(As a sidenote: the '-s' parameter will always override the defaults set in the jndi.properties file included in the shutdown.jar file of JBoss).
Comment 1 Gabriele Garuglieri CLA 2007-04-20 02:45:24 EDT 
Problem still there in 2.0.0M6.
Could you please fix it before 2.0.0 release?
The solution is really simple and is given in the opening description.

Thanks.