I've just tried the same thing on Windows platform only to find that the same issue appears.
Then, I tried a "workaround": at Preferences->Servers->Installed Runtime, this time I added a "JBoss 4.2 Runtime" (which is under the tree node of JBoss, a division of Red Hat) (INSTEAD OF what previously I've set "JBoss v5.0" under the JBoss tree node).
Oh. It started w/ some errors and warnings but at least it finally reaches as the status of "Started".
Does it mean that the only installed Runtime under the tree node of "JBoss, a division of Red Hat" work? Or jboss 5.0 not ready here or anything I mis-configured?
For the jboss 5 issue, the last message shown in console before the timeout error is "Binding Transaction Manager JNDI Reference".
thanks in advance,
anything outside of JBoss a division of Red Hat is the Eclipse WTP provided adapters - all some that have issues of various degress.
I confirmed recently that our jboss 4.2 will work with jboss5. We are working on having a "native" JBoss5 adpter in upcoming releases.
thanks for anderson's reply.
at least, I can confirm the limitations now.
long for the coming releases that solve the issue.