H2db jar not working on port other than 8082 - java

I have a h2db jar which i want to run on port other than 8082.
I tried java -jar -Dserver.port=XXXX but it is still running on 8082.
Is there any way to run it on other port?

You can use
java -jar h2-*.jar -webPort 9999
where h2-*.jar is the name of H2's jar file and 9999 is a port number.
There are also -tcpPort, -pgPort and other parameters.
If you want to start the web server only without other open ports for JDBC and ODBC clients and open a browser window, use
java -jar h2-*.jar -web -webPort 9999 -browser

I think the parameter to be used is webPort and not server.port.
Also you might have to provide this parameter in the .h2.server.properties file as stated in the documentation:
http://www.h2database.com/html/tutorial.html#console_settings

Related

Is there a way to change micronaut server port from CLI?

As the title suggested, i'm having trouble configuring the port for a micronaut server. I would like the port to be configured from the CLI or from a properties file, not from inside the java application (i don't want to rebuild the project each time i want to change the port). I have seen that using spring the following command can be used:
java -jar server.jar --server.port=8888
Is there any similar CLI command for micronaut? Or can someone help me out configure a properties file to change the port?
As mentioned in Run Micronaut service on port provided from commandline there are these two opions.
$ java -Dmicronaut.server.port=7070 -jar foo-0.1-all.jar
or
$ MICRONAUT_SERVER_PORT=7070 java -jar foo-0.1-all.jar
This is the solution i was searching for. However, only the first option worked for me. Thank you PeterMmm!

Is there a way to specify port number running Uber/Fat JARs?

I'm being able to run a Spring Web Application on browsers by executing an Uber/Fat JAR using java -jar JAR-file command but I don't know whether I can specify the port number to run on like in Angular using --port?
you can use server.port property in command line to specify the port number.
java -jar JAR-file --server.port=8083
or
java -jar -Dserver.port=8083 JAR-file

OpenTripPlanner: How to run standalone instance on a port different from default 8080?

I use this command to get the Grizzly server running:
java -Xmx6G -jar otp-0.19.0-shaded.jar --build Data --inMemory
and it successfuly runs the Grizzly server on 8080. But because I have want to now use it on a machine that has 8080 occupied I need to run it on e.g. 9090.
when i try:
java -Xmx6G -jar otp-0.19.0-shaded.jar -p 9090 --build Data --inMemory
Which is suggested in numerous places in the web I will get an error that claims that "-p" is an unsupported command. Any ideas on how I should proceed with this?
I use --port to define the http port (and --securePort for the https port). OTP will open both http and https, so if you want to run multiple instances on a single machine, you have to keep both unique per instance.
This works for me:
java -jar otp*.jar -server --port 55555 --securePort 55556 --router "" --graphs Graph.obj
BTW, the help dialog lists a few other options:
java -jar otp*.jar --help

Glassfish Server start-domain domain1 won't start

I recently downloaded Glassfish 4.0 and I want to use it in NetBeans for making some Web Applications, but when I want to start the domain1 (asadmin> start-domain domain1) I keep getting this error:"There is a process already using the admin port 4848 -- it probably is another instance of a GlassFish server". Any clue what could be the problem?
Glassfish could not resolve the host name. Diagnose the problem (on Linux) as follows:
Open a Terminal.
Type hostname.
Type: ping $(hostname)
If the ping command fails (could not find the host), then add the host name to /etc/hosts. This can be accomplished as follows:
Switch to root: sudo su -
Type: echo "127.0.0.1 $(hostname)" >> /etc/hosts
Kill GlassFish
Restart GlassFish
your system using port 4848 that is why.
when glassfish starts its need three port numbers one for administrations, one for http applications other for https.
so in you system 4848 is already reserved by some program or server.
Or you can change default port number as per your need like below.
type in command prompt.
To change the HTTP port to 10080:
asadmin set server.http-service.http-listener.http-listener-1.port=10080
To change the HTTPS port to 10443:
asadmin set server.http-service.http-listener.http-listener-2.port=10443
To change the administration server port to 14848:
asadmin set server.http-service.http-listener.admin-listener.port=14848
Try lsof -i:4848 on the terminal.
Kill the java processes listed using the command kill -9 <PID>.
If you have a GUI task manager, say like Activity Monitor on OSX, then you can just kill the java processes listed there.
Hope this works for anyone facing this problem.
1- Go to the config folder inside your domain.
(In my case: C:\Glassfish\glassfish\domains\mydomain\config\ )
2-Open the file domain
3-Update the port number on these three lines:
4-Restart your domain:
--Note
For restarting the domain:
1-Open cmd console
2-Navigate yo your domain
3-Execute: asadmin restart-domain mydomain
--I hope it helps :-)
Solution can be this:
in console type:
echo $HOSTNAME
then make sure the output follows 127.0.0.1 string in
/etc/hosts
For example:
127.0.0.1 dev.myserv.pl
Do a
netstat -aon
from command line and check which process is using your port.
If it's not important, kill it as a quick'n'dirty solution.

Several ports (8005, 8080, 8009) required by Tomcat Server at localhost are already in use

I'm getting the following error when I try to run a simple JSP program on Tomcat in Eclipse.
Several ports (8005, 8080, 8009) required by Tomcat v6.0 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 is this caused and how can I solve it?
You've another instance of Tomcat already running. You can confirm this by going to http://localhost:8080 in your webbrowser and check if you get the Tomcat default home page or a Tomcat-specific 404 error page. Both are equally valid evidence that Tomcat runs fine; if it didn't, then you would have gotten a browser specific HTTP connection timeout error message.
You need to shutdown it. Go to /bin subfolder of the Tomcat installation folder and execute the shutdown.bat (Windows) or shutdown.sh (Unix) script. If in vain, close Eclipse and then open the task manager and kill all java and/or javaw processes.
Or if you actually installed it as a Windows service for some reason (this is namely intented for production and is unhelpful when you're just developing), open the services manager (Start > Run > services.msc) and stop the Tomcat service. If necessary, uninstall the Windows service altogether. For development, just the ZIP file is sufficient.
Or if your actual intent is to run two instances of Tomcat simultaneously, then you have to configure the second instance to listen on different ports. Consult the Tomcat documentation for more detail.
kill $(ps -aef | grep java | grep apache | awk '{print $2}')
no need to restart Eclipse
if you get the above error, just enter this line in terminal
again start the tomcat in Eclipse.
works only in Linux based system ( Ubuntu ..etc )
If you are running on windows try this in the command line prompt:
netstat -ano
This will show all ports in use and the process id PID # of the process that is using that port.
Then Ctrl+Alt+Del and open Task Manager to see which process is that.
You can then choose either to close/stop it or configure your server to use another port.
To check if the new choosen port (let's say 8010) is available do this:
netstat -ano | grep 8010
If it does not return any lines then you are fine.
To change the port go to the Server view, open server.xml and change the port there.
Mine has this entry:
Connector port="8010" protocol="AJP/1.3" redirectPort="8443"
If you are on mac environment, here is what I did.
Find the process id running on this port from terminal, eg, 8080:
lsof -i :8080
and kill it:
kill -9 <PID>
Example:
You may see following result:
MacSys:bin krunal.$ lsof -i :8080
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
java 21347 krunal 52u IPv6 XXX 0t0 TCP *:http-xxx (LISTEN)
and kill it: (kill -9 21347)
Steps to free port which is already used to run tomcat server in Eclipse
For example , suppose 8080 port is used , we need to make free 8080 to run tomcat
Step 1:
C:\Users\username>netstat -o -n -a | findstr 0.0:8080
TCP 0.0.0.0:3000 0.0.0.0:0 LISTENING 3116
Now , we can see that LISTENING port is 3116 for 8080 ,
We need to kill 3116 now
Step 2:-
C:\Users\username>taskkill /F /PID 3116
Step 3:
Go to Eclipse and start Server , it will run
If you use Eclipse then double click on servers and double click on tomcat server then one file will open. In that file change HTTP port to some other port number and save(Ctrl+S) then again start the server.
If Eclipse says
Several ports (8005, 8080, 8009) required by Tomcat v6.0 Server at localhost are already in use
This error comes because tomcat may be running in background so first stop that server..follow the below details.
Solution is:
Open the "console" view (window->show view->Console)
Then stop the tomcat server.
Then open the "server" view and start the server it will work.
Thanks!
I have no another instance of Tomcat running ad no other process using "Tomcat port" (in my case, the 8088 port).
Eclipse send the same message on starting Tomcat:
....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).
I solve the problem in this way:
go to bin of tomcat by prompt
launch startup.bat
launch shutdown.bat
start tomcat by Eclipse
What I did after reading all the suggested answer and as I know my port was already in use. I double clicked on Tomcat under the Servers tab in eclipse and it opened overview information and then find port information. Just changed conflicting port as mine was 8009 port (error mentioned during starting the server). I have changed it to 8008 and it works fine. Give a try if the changed port would not be in use server will start.
Step 1: netstat -a -o -n and it will bring up a network list,search for the local address like 127.0.0.1:8080 and note the PID (eq 3624)
C:\>netstat -a -o -n
Step2 : taskkill /F /PID 3624 . Run this command to kill that process.
C:\>taskkill /F /PID 3624
link to post
On Windows use command for stopping the already running tomcat instance and try running it again in eclipse, it may work.
net stop tomcat7
Or you can change the port in server's XML if you just want to run on some other ports.
Easy way to solve your problem:
The server may already be running in another process, or a system process may be using the port. In order to kill that port, do the following:
1) Download TCPView(only 285kb) from following link.
http://technet.microsoft.com/en-in/sysinternals/bb897437.aspx
2) Extract folder and start TCPView application.
3) Right click on java.exe(because 8009,8005 ports are commonly used by java process) and select End Process option.
this would stop another process easily..
NOTE: Running TOMCATPATH/bin/shutdown.bat may not shutdown Tomcat when it contains some demon or unmanaged
threads. In such cases TCPView works fine without any issues.
I checked all the answers but informing only to kill PID.
In case if you have terminal access shared by all it will not help or maybe you do not have permission to kill PID.
In this case what you can do is:
Double click on server
Go to Overview and change ports in Ports like this:
If you are in Java EE prospective in Eclipse and trying to start the Tomcat Server in Eclipse in debug mode, then you will get such errors. You must switch to debug prospective in Eclipse. I have solved my problem like this.
Sometimes if the ports are not freed even after attempting shutdown.bat what #BalusC suggested,you can kill the javaw process. Do following steps :
Click on Start Menu and open "Windows powershell"
Right click before opening and select "Run as administrator"
Enter command ps. You may see a image as follows :
See the process number of process "javaw".The process number is the rightmost number in the columns, I have highlighted in the image process number of javaw for example.
Enter command kill . javaw is killed and now you must be able to run the program.
Here's one more option to try if none of the efforts above helped. You might be using Eclipse from a Shared Drive (for eg, H:). If so, move/copy it the entire Eclipse directory to C: and try again.
My Eclipse could not open ports for Tomcat server (with the above error), nor even connect to internet. I also tried another Tomcat plugin (Sysdeo) which failed to open the ports too.
These are the options I tried:
Check and Kill Other Tomcat Instances
In command prompt, netstat -ano and check if any other processes are using the conflicted ports.
Find the PID and kill it
Try starting the server again.
Change Tomcat Ports in Eclipse
In Eclipse Server tab, double click the Tomcat instance. This will open the configuration tab.
Under Ports, change the port numbers. (for eg, 18080).
Kill java.exe and javaw
In Task Manager, find and kill java.exe and javaw (see https://stackoverflow.com/a/25334782/4212710 and https://stackoverflow.com/a/26136890/4212710)
Try starting the server again.
See my other answer for Eclipse not connecting to Internet (https://stackoverflow.com/a/37246087/4212710).
For windows users:
Go to Task Manager directly with CTRL+SHIFT+ESC key combination.
Kill the "java.exe" processes by right clicking and selecting "End Task".
The simpler fix that works for me is deleting my current deployed webapps from tomcat through the "Server" tab. Once I remove them the problem goes away. Simply re-deploy your project by going on Run As > Run on Server.
The problem often arises when Apache Tomcat fails to terminate, properly, even though a shutdown instruction was sent. In my case, using Tomcat 8, this happens with annoying regularity. Luckily, you can use Windows PowerShell and the netstat command to create a simple script to kill the process.
The following PowerShell script will parse the output from netstat to find any process that is listening on 127.0.0.1:8005, extract its PID and then kill that process:
netstat -a -o -n `
| select -skip 4 `
| % {$a = $_ -split ' {3,}'; New-Object 'PSObject' -Property #{Original=$_;Fields=$a}} `
| ? {$_.Fields[1] -match '127\.0\.0\.1\:8005$'} `
| % {Write-Host "Killing PID" $_.Fields[4] "..."; taskkill /F /PID $_.Fields[4] }
If your server.xml configures Tomcat to use a different port or IP, edit the regular expression on the script's fourth line accordingly.
Finally, I should point out that the situation is better on Linux because you can instruct Tomcat to save its PID to a file at startup-time and use a switch to force the shutdown, later - the shutdown script for 'nix systems already features the ability to kill the process and the sleuth-work with netstat is not required.
If the above issue occurs in Windows 7 or 10 based OS, the problem occurs because Tomcat is running as Windows Service. To stop Tomcat running as Windows Services, Open Windows Control Panel. Find the service "Apache Tomcat" and Stop it.
The Another way is to kill the process running on port 8080 using cmd.
Open cmd running it as administrator.
C:\users\username>netstat -o -n -a|findstr 0.0:8080
TCP 0.0.0.0:8080 0.0.0.0:0 LISTENING 2160.
The above 2160 is process id of process running on port 8080 and kill that process using the following command
C:\users\username>taskkill /F /PID 2160
Go to IDE and start Server, it will run
It may be because you are not stopping your tomcat service properly. To do that, Open your task manager there you can see a javaw.exe service. First stop that service. Now restart your tomcat it works fine.
In my case, it was giving me the error: Port 8005 required by Tomcat v8.0 Server at localhost is already in use
I changed 8005 port in apache-tomcat-8.0.39\conf\server.xml but changes were not getting reflected. Then I did these changes from eclipse. by double clicking server and modifying the port from 8005 to 8006 and it works.
Before putting 8006 I checked in windows shell if this port is available or not. By executing following command:
netstat -a -o -n | findstr 8006
I face the same problem and after searching the answer as shown below:
1. open Monitor Tomcat as shown below:
Simply press stop as shown in below picure:
Finally it works with me after many trials and suggested solutions.
Best Regards,
Kerelos Mikhail
On Eclipse make a raw delete of Tomcat configuration folder under project "Servers".
I tried it as last hope and it worked.
In case of windows, I experienced a new stuff...
stopping tomcat from /bin folder will immediately not releasing the port 8080. It takes around 5-10 mins to release the port. After 10 mins again if i try to run my project
Run-> Run on server .. it allows to run.
I'm unsure whether my understanding is correct!
Refer to the following blog "how to kill tomcat without have to restart your computer"
http://stanicblog.blogspot.fr/2012/01/how-to-kill-apache-tomcat-without.html
Hope this will help someone in the future.
It occurs when others in the project are also using the same port numbers as you are using!
double click tomcat server, change port numbers to anything 8585 or whatever. The code will now begin to run!
How to kill a windows service using PID -
open command prompt and type netstat -ano
find the PID of the ports which are in used, in this case, it will be 8080, 8005,8009. Let's say PID of these ports are 5760.
Now Type taskkill /f /pid 5760
it will close the PID and ports will be available for use. Now you can start tomcat as normal by Windows services or by eclipse itself.
Thanks
kill a Windows service that's stuck on stopping or starting
Several ports (8005, 8080, 8009) required by Tomcat vX.X Server at localhost are already in use
To check whether another instance of Tomcat already running or some other process is using the ports you can use:
netstat -b -a in command prompt for windows. This lists the ports in use and gives you the executable that's using each one. You need to be in the admin group to do this.
You might get something like this:
TCP 192.168.0.1:8009 192.168.0.1:0 LISTENING 196 [Tomcat7.exe]
TCP 192.168.0.1:8080 192.168.0.1:0 LISTENING 196 [Tomcat7.exe]
TCP 192.168.0.1:8005 192.168.0.1:0 LISTENING 196 [Tomcat7.exe]
Open task manager Ctrl+Shift+Esc, and kill Tomcat7.exe or any other process using these ports.
Your Tomcat is probably running already. That's why you have got an error. I've had the same problem before. I solved it very simply:
Restart your computer
Open Eclipse
Run your Tomcat
That's all.

Categories

Resources