[
http://jira.jboss.com/jira/browse/JBIDE-501?page=comments#action_12367482 ]
Marshall Culpepper commented on JBIDE-501:
------------------------------------------
One of the problems with JBoss is that configuration files are pretty fluid, ... 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). That being said, the
"default" location for all this info is 9 times out of 10 the place it's in,
and I think Rob already uses that default config for the Ports section in the JBoss
Servers View to edit the JNDI port. So, it would be possible to have a reasonable default
here I think, as well as give off a warning if that default can't be found and the
config the user gave us is wrong.
Rob?
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: JBossIDE 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