[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-501) Unable to start JBoss-Server 4.2GA
[ http://jira.jboss.com/jira/browse/JBIDE-501?page=comments#action_12367606 ]
Rob Stryker commented on JBIDE-501:
-----------------------------------
>meaning that the user could easily move common configuration like
JNDI ports and other MBeans into their own configuration file (that we'd have no
knowledge of).
Current implementation *does* check only service.xml. I suppose I can look to change this
in the future after much thought on a decent structure.
Change invalidating the NamingException from stopping the startup has been committed.
I encourage both of you, Perry and Carsten, to try again with a "JBoss, a division of
Red Hat" server once more. The WTP-provided servers have problems with changing
command line arguments or custom JNDI ports.
Unable to start JBoss-Server 4.2GA
----------------------------------
Key: JBIDE-501
URL: http://jira.jboss.com/jira/browse/JBIDE-501
Project: JBoss Tools
Issue Type: Bug
Components: JBoss Tools Core
Affects Versions: 2.0.0.GA, 2.0.0.Beta3
Environment: Windows-XP, Eclipse 3.3 Europa,
JBossTools-200706300254-nightly-ALL-win32.zip
Reporter: Perry Rhodan
Assigned To: Rob Stryker
It's impossible to start a Jboss 4.2GA Server with
JBossTools-200706300254-nightly-ALL-win32.zip under Eclipse Europa release. Every time the
startup will be interrupted by an <problem occured> dialog with "Server
<servername> failed to start" as detail.
In the event-log will this failure be logged:
Failure: NamingException: Could not obtain connection to any of these urls:
localhost:1099 and discovery failed with error: javax.naming.CommunicatinException:
Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out.]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira