-
1. Re: Unable to start a JBAS 4.2.0.GA with JBossTools-20070630
rhodan76 Jul 2, 2007 3:40 AM (in response to sunfire)Same problem here with JBossTools-200706300254-nightly-ALL-win32.zip and Eclipse-Europa GA release. Any hint to fix this ?
-
2. Re: Unable to start a JBAS 4.2.0.GA with JBossTools-20070630
rhodan76 Jul 2, 2007 4:51 AM (in response to sunfire)Opened Jira-Issue: http://jira.jboss.com/jira/browse/JBIDE-501
-
3. Re: Unable to start a JBAS 4.2.0.GA with JBossTools-20070630
baz Jul 3, 2007 4:27 AM (in response to sunfire)I am using this nightly: JBossTools-200706290355-nightly-ALL-win32.zip
When setting up the configuration for a server there are 2 possibilities.
In the dialog New Server (Define a New Server)
one can choose a Jboss Serverfrom 2 subfolders. One is named JBoss and the second is named JBoss, a division of Red Hat
When choosing a server from the second choise (JBoss, a division of Red Hat) than i am not able to start rthe server.
After that i setup a server from the Folder JBoss and...
this server starts up.
Qustions: What are the different folders for?
Why does one start and the other not?
Ciao
Carsten -
4. Re: Unable to start a JBAS 4.2.0.GA with JBossTools-20070630
maxandersen Jul 3, 2007 5:43 AM (in response to sunfire)JBoss is the WTP jboss adapter
JBoss a division of Red Hat
Which version of jboss where you trying to use ?
The Red Hat one should (at least it does for me) work better with 4.x. -
5. Re: Unable to start a JBAS 4.2.0.GA with JBossTools-20070630
baz Jul 3, 2007 6:14 AM (in response to sunfire)Hello Max,
i tried (and have) installed Jboss 4.2GA
Installed Eclipse3.3 and JBossTools.
Choosing a server from 'JBoss a division of Red Hat' and named it 'jboss server'.
And getting the described erroneus behaviour.
So i added a new server (with the same runtime) from JBoss, which is named by default as 'JBOSS 4.2'.
The 'JBOSS 4.2' server started. -
6. Re: Unable to start a JBAS 4.2.0.GA with JBossTools-20070630
maxandersen Jul 3, 2007 8:14 AM (in response to sunfire)the problem is most likely that we actually try and verify that the server has started where as the default jboss wtp implementation just assumes it started...
Rob is the right one to comment/investigate on it.