Philip!!!
Thank you very much! It works fine. I can enter to my applications in
Tomcat and the Index page of Tomcat.
Best regards!
Are these connections the problem? How can I close them?
The top line shows a java process listening on port 8180. It has a PID
of 24027. So I would proba
> Are these connections the problem? How can I close them?
The top line shows a java process listening on port 8180. It has a PID
of 24027. So I would probably just murder it with a:-
kill -9 24027
and then you should be fine.
Cheers,
Phil.
This is the last output from catalina log when I start tomcat:
Apr 14, 2008 11:30:55 AM org.apache.catalina.core.AprLifecycleListener
lifecycleEvent
INFO: The Apache Tomcat Native library which allows optimal performance
in production environments was not found on the java.library.path:
/usr/l
Hello Philip.
When Tomcat is stopped. Netstat returns this:
tcp6 0 0 :::8180 :::*
LISTEN 24027/java
tcp6 552 0 :::217.116.20.:8180 :::84.126.238.:1137
CLOSE_WAIT -
tcp6 592 0 :::217.116.2
> I've removed Tomcat, including --purge with apt-get and I've reinstalled,
> but I still having the same problem.
What's the result of running:-
netstat -tanp | grep 8180
as root. Surely something is holding that port open?
-
I've removed Tomcat, including --purge with apt-get and I've
reinstalled, but I still having the same problem.
Yes, that is the first I thougth. But 8180 port doesn't appear in my
nmap localhost, even If tomcat status is running. I must to say that
when I stop tomcat in my command line appear
Yes, that is the first I thougth. But 8180 port doesn't appear in my
nmap localhost, even If tomcat status is running. I must to say that
when I stop tomcat in my command line appears several dots . . . . and
at the end (Killing) twice. It seems that tomcat can't stop (as we see
in the log) an
> From: Toni Tortosa [mailto:[EMAIL PROTECTED]
[...]
> When I start tomcat 5.5.:
[...]
> java.net.BindException: Address already in use:8180
Something's hanging onto port 8180. It's probably an old Tomcat instance that
hasn't properly closed down, but it may be something else. Find the process