| View previous topic :: View next topic |
| Author |
Message |
mschraff
Tux's lil' helper
Joined: 08 Jun 2008
Posts: 105
|
 Posted: Tue Dec 29, 2009 1:57 pm Post subject: Java blocks port 9080 |
 |
|
I use the gcaldaemon to google calendar with kontact. Yesterday I recognized, that gcaldaemon is unable to start and I assume it's a problem with java.
When I run "/opt/gcaldaemon/bin/standalone-start.sh" I see some error messages in the terminal
| Code: |
[...]
WARN | Set the 'ldap.allowed.hostnames' parameter to limit remote access.
INFO | LDAP server starting on port 9080...
FATAL | ADDRESS ALREADY IN USE
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
[...]
|
I checked, which service uses the port 9080 and
| Code: |
# lsof -i :9080
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
java 2941 michael 26u IPv6 17230 0t0 TCP *:9080 (LISTEN)
|
as you can see, java is using it.
A few days ago I had a problem with my system beside some other things I checked, which java-jdk I am using. The system-vm and the vm for every user were set properly to
| Code: |
# java-config-2 -L
The following VMs are available for generation-2:
1) Sun JDK 1.5.0.22 [sun-jdk-1.5]
*) Sun JDK 1.6.0.17 [sun-jdk-1.6]
|
Nevertheless I set the VMs again to sun-jdk-1-6 to ensure that this VM is really used by my system. Perhaps I made a mistake and this is the reason for my problem with the gcaldaemon.
_________________
DELL Latitude 5550 intel Core i5-5300 CPU @ 2.30GHz
gentoo genkernel-5.4.38 gcc 9.3.0 portage 2.3.89-r3 |
|
| Back to top |
|
 |
TJNII
l33t
Joined: 09 Nov 2003
Posts: 648
Location: for(;;);
|
| Posted: Tue Dec 29, 2009 7:40 pm Post subject: |
|
|
| I'm not familiar with those applications, but it looks like the application you are trying to start is also written in Java. In that case, I would suggest making sure it shuts down cleanly. More than likely the service was not stopped cleanly and the daemon is still listening and bound to the port. You should be safe to kill the blocking process. You can also verify this by making a note of the listening process then next time you start this app. If my hypothesis is correct, if you run into this problem in the future the process ID will be the same as the listener you started. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Networking & Security
