im starting jboss(7.1.0) from eclipse(Kepler), but keeps freezing on starting state..
When after timeout, it gives a error saying that Jboss didnt start..
If i start Jboss from command line, works fine.
Just for info, im using java6, for runtime
Related
I am trying to run the JBOSS server in standalone mode. I have set up JBOSS_HOME, JAVA_HOME. When I try to run standalone in cmd(administrator), it just says calling standalone.conf.bat and then nothing happens.
I checked http:\localhost:8080, it is not opening which means server is not started.
Does anyone know how to troubleshoot?
To start JBoss 7 on windows use standalone.bat script and to access management console, default URL is localhost:9990.
I'm using eclipse 3.6 on windows 7 x64 and out of nowhere it failed starting one day. I see in the task manager that it begins and crashes after a second. No error message, nothing. I also extracted the files of eclipse again from the zip, and the problem is still there.
It starts though through windows troubleshoot compatibility. What's wrong?
Thanks
When I do on my app.js Debug As > Node Application it says
Launching STANDALONE_V8 has encountered a problem.
Failed to connect to Standalone V8 VM
connect timed out
It should start an app. Doing so directly on my terminal works fine.
When I start a debug session in my terminal and than try to debug it in Eclipse works fine too.
So is there anything that has to be done in order to make it work in Eclipse?
What exact error is in ErrorLog View on in Nodeclipse Console?
What is Java is used and Nodeclipse version?
Try to specify Java version: in eclipse.ini point to JDK 7
Check also
- toggleBreakpointsTargetFactory specified id is already registered
Installed Eclipse-Kepler on a Windows 8 box. Clojure and Leiningen already installed. Installed Counterclockwise. Started up, created test Clojure project, ran without debugger, and ran successfully under debugger. Messed with it a bit more, was in and out of the debugger several times. After one debugging session got "an error" (yes, I know I should have written it down, but failed to do so. Take pity upon the soul of this poor sinner...). After that every debugging session I tried to start (using "Debug As...Clojure Application") failed to start, eventually timing out with a "Timed out waiting for REPL to start" error. Messed with it a while, uninstalled CCW, re-installed CCW - no change, REPL still refused to start under the debugger. Could always start a REPL by "sending" the text of the project file to the REPL using Ctrl-Alt-S. Finally deleted all of Kepler, re-installed, re-installed CCW, and could then debug again.
My questions: has anyone else encountered this, and is there a better workaround than blowing away the entire Eclipse install and re-extracting from the .zip? I did do a check for updated versions of anything and nothing came up. Is this a Kepler issue, i.e. might this be more stable under Juno?
I am running a remote debug session in eclipse, connecting to weblogic (10)
In the 'Server Start' the parameters are specified:
-Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8115,server=y,suspend=n
...and in the Eclipse debug configuration, I have the port and server name specified.
This was working fine for more than a year for me. Today, with no changes on my part, an application I am trying to debug, is NOT hitting breakpoints. Basically it looks like debugger is NOT active, while everything seems as it is. Where can I look to diagnose and to mediate the problem?
Thanks