[
http://jira.jboss.com/jira/browse/JBIDE-501?page=comments#action_12367511 ]
Perry Rhodan commented on JBIDE-501:
------------------------------------
Sorry, but we are using a jboss 4.2 with all values set to default, there is nothing
special in the configuration. Especially the naming service is running on 1099, see log:
08:43:01,136 DEBUG [ServiceCreator] Created bean: jboss:service=Naming
08:43:01,136 DEBUG [ServiceConfigurator] CallByValue set to false in jboss:service=Naming
08:43:01,153 DEBUG [ServiceConfigurator] Port set to 1099 in jboss:service=Naming
08:43:01,153 DEBUG [ServiceConfigurator] BindAddress set to 127.0.0.1 in
jboss:service=Naming
I don't know, but could it be possible, that it has todo with the changed binding
behaivor of jboss since 4.2, meaning binding only to local-interface per default ?
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