JBOSS is not starting using standalone - jboss

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.

Related

Tomcat hangs and prevents Eclipse from shutting down after running some time

I'm running Eclipse 4.6.1 with in-IDE Tomcat 8.5.6 on Windows 10 Professional 64-bit Anniversary Edition.
After Tomcat is left running in Eclipse after some time, the Tomcat embedded in Eclipse can no longer be stopped. I press the red "Stop" button in the "Servers" tab, but nothing happens. Eventually Eclipse will ask me if I want to terminate Tomcat:
Server Tomcat v8.5 Server at localhost is not responding. Do you want to terminate this server? Click OK to terminate the server or click Cancel to continue waiting.
I click "OK to terminate the server... but Tomcat keeps running.
Unfortunately when I then try to close Eclipse, it hangs on "Saving workbench state." Finally I have to kill Eclipse, thereby losing my workbench state. Even worse, if I then start Eclipse back up and try to restart the embedded Tomcat, I get the following error:
'Starting Tomcat v8.5 Server at localhost' has encountered a problem.
Several ports (8005, 8080, 8009) required by Tomcat v8.5 Server at localhost are already in use. The server may already be running in another process, or a system process may be using the port. To start this server you will need to stop the other process or change the port number(s).
How can I surgically go in and really kill Tomcat so that it doesn't hang Eclipse and keep ports open? (Unfortunately the only thing that shows up in the task manager is Eclipse.exe. There is no Tomcat to be seen. I've tried killing the javaw.exe subprocess, but that doesn't help.)
(At one point I thought this was related to a VPN connection going down, but today this happened with no VPN connection at all.)
I've filed Eclipse Bug 511342. We'll see if anything comes of it.
i've tried locally but i couldn't recreate the bug .
im not sure that this answers your question but it is for sure something worth trying , in any case this might show some features to other users....
in the window menu you have the SHOW VIEW , there you can choose other
this open the future window with search bar and all the available views for the ide .
in the debug view , you can do actions not only on applications , but on servers also . the menu here is different from the view you see in the server, and you can do advanced termination other things.
welp , hope that helps .
*note , you don't need the server to run in debug mode .
Find your Tomcat installation directory, navigate to bin folder, open a command window there and execute an .bat file named shutdown.bat, this way you can kill tomcat directly, make sure to locate the appropiate Tomcat installation directory which Eclipse is using.
UPDATE - Expected output:
I have not used it in the same way you have, but this may help.
On a command prompt (Cmd.exe) execute:
netstat -a -o | find "8080"
That will list all IP/PORT in use alongside the PID (process id) filtering by port # 8080 (change it to meet your needs or remove the find if you want to list all)
Open Task Manager, and using the PID you should be able to find the particular
process that is using the ports you need to release.
updated:
Once you find the port (8080) you can try using the command
taskkill /f /pid [port number]
Found a related issue with this command: Stack overflow - Tomcat not shutting down eclipse
Again, I use this when I need to find a rogue thing that I need to kill, and I don't know if the embedded environment will show it separate but its worth a try.
In tomcat's console inside Eclipse, there's a red button that can stop it. Albert also stated that in task manager it appears as javaw.exe, however Eclipse itself also appears as javaw.exe, so be careful when killing each one. Eclipse should be the one that takes more memory.

node.js express app won't start (or debug) in Eclipse (Nodeclipse)

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

how to restart jboss server using command prompt

I have a maven script which is connecting to SVN and checking out the code and it is deployed to the deployment folder of JBoss. Can anyone tell me how to restart the JBoss server please using the command prompt?? I am using JBoss 6.0.0.GA.
Thanks in advance
From you JBOSS_HOME dir /bin/standalone.sh or /bin/standalone.bat.
You can shut it down with CTRL-c.
That is the specific answer to the specific question you asked. Is there more going on here?
In jBoss AS 7.1.1 Final and all new versions after, including the Current version, WildFly 17 (JBoss is now WildFly) you can actually re-start.
You do not need to shut down with CTRL-C
Open a new command window and keep it side by side with the current running command window, so that you can see the re-start.
from command prompt goto WildFly installation folder
(eg. "C:\Program Files\WildFly\wildfly-17.0.0.Final\bin\" ) and execute
jboss-cli.bat --connect command=:reload
(eg. C:\Program Files\WildFly\wildfly-17.0.0.Final\bin\>jboss-cli.bat --connect command=:reload )
In Linux: $ ./jboss-cli.sh --connect command=:reload
I know this is not the exact answer to the question, but is the first result for mine:
How to restart wildfly?
sudo service wildfly restart
There are also top, start and so on options

Run Tomcat within Eclipse as a different user

I am running Eclipse Indigo EE on Windows 7, logged in as me.. I have Tomcat running within eclipse right now (under Servers view) but it's running under my user. I'd like to run it as a different user. How do I go about achieving that? I don't want to run it as a Windows service or outside of Eclipse, I want to continue to manage it through Eclipse which makes debugging, shutting down, starting up a lot simpler for me.
Any ideas how to go about setting that up or if it's even possible?
Thanks
I could not find a way to start the Tomcat server as a different user. Whereas you can achieve this by opening eclipse as a different user. Following are the steps for the same
Open command prompt.
Run following command with intended user name and eclipse exe's location
runas /user:domainName\userName C:\eclipse-jee-mars-R-win32-x86_64\eclipse\eclipse.exe
Thanks,
Sabeer

Debug remote PHP CLI scripts

Here is my situation:
I am developing PHP CLI scripts on a distant server using Eclipse IDE with the RSE plugin (allows to edit files directly on the server).
Now I need to debug these scripts in a similar fashion than in Java (break points, show the variables content, ...).
I found something that could do the job: XDebug and PDT (Eclipse plugin). The problem is that when I try to launch the debug mode Eclipse says that there is no PHP debugger on the local machine. I guess it should be installed on the server machine.
I would like to know if it's possible to use PDT and XDebug to debug remote scripts and, if it's the case, how to configure them to do so. If not, I'd like to know if other solutions exist. It seems like XDebug uses TCP so it should be possible to debug remotely. I can change my IDE if necessary.
The server runs Ubuntu 10.04 with php5-cli and the dev machine with eclipse runs Win7 32bit.
Thanks
Yes this is possible, you need to enable xdebug in the remote server's PHP.ini file and make sure that the xdebug port (default 9000) is not blocked by any firewalls.
xdebug's page on setting up remote debugging.
Here is the complete procedure for the people who have the same problem:
First, install RSE by following the instructions on this website: http://help.eclipse.org/galileo/index.jsp?topic=/org.eclipse.rse.doc.user/gettingstarted/g1installing.html
Follow the instructions on this HowTo to install XDebug on the server:
http://ubuntuforums.org/showthread.php?t=525257
Install PDT on Eclipse and do the following changes:
- under Windows/Preferences, go under PHP/Debug and change PHP Debugger to XDebug
- under Windows/Preferences, go under PHP/Debug/Installed Debuggers and configure XDebug. Change the field "Accept remote session (JIT)" to "any".
Open the Remote System Explorer perspective, select your scripts directories and create a project from them (Right Click, Create Remote Project). It will now appear in the PHP perspective.
Let Eclipse run and go to the server (e.g. via SSH). Run the script you want to debug. A Window will then appear on Eclipse proposing you to choose with which "local" (remote via RSE in our case) file you want to link the running script to. Normally, the default script proposed should be the correct one, because it is the one running on the server.
You should now have visual debugging with Eclipse for your PHP-CLI scripts!
Do you want to debug while being able to interact with the script on CLI or do you just want to start it and then step through the code? I guess your question is referring to the problem that you can't access the script directly through a URL. If that's your problem, then I guess the easiest solution would be to debug a usual PHP-web-site which requires your script. Then you can launch XDebug with that web-site initially and step into the script through the require/include-statement.
index.php:
<?php require_once("../../../../../dir1/[...]/cliscript.php");
Best regards
Raffael