Errors in catalina log - address already in use: bind

[Ivan Rotrekl]

 Hi,

 I  have noticed strange errors  in my catalina log in tomcat which appear after each server startup.

These don't look pretty, but I have not noticed any specific issues so far,  apart from the errors themselves:

SEVERE [main] org.apache.coyote.AbstractProtocol.init Failed to initialize end point associated with ProtocolHandler ["http-nio-8888"]
java.net.BindException: Address already in use: bind

SEVERE [main] org.apache.catalina.core.StandardService.initInternal Failed to initialize connector [Connector[HTTP/1.1-8888]]
Caused by: org.apache.catalina.LifecycleException: Protocol handler initialization failed
Caused by: java.net.BindException: Address already in use: bind

and so on...

I am running the latest stable Lucee on IIS 7 and could see this happening on my install of Lucee on Tomcat 7 / Java 1.7 and after upgrading to Tomcat 8/ Java 1.8  also.

I thought something else might be blocking the port and  runned:
netstat -nao | findstr ":8888"

which resulted in:
TCP    0.0.0.0:8888           0.0.0.0:0              LISTENING       344 
TCP    [::]:8888              [::]:0                 LISTENING       344

where 344 is the id of the tomcat8.exe process


Would anybody know what is going on here ?


Regards

Ivan

[Jordan Michaels]

Is the error preventing you from running Lucee properly? Are the errors recent - IE: a current issue that happens regularly and not something that has happened in the past?

-Jordan

----- Original Message -----
From: "Ivan Rotrekl" <rot...@smartway.cz>
To: "Lucee" <lu...@googlegroups.com>
Sent: Thursday, September 3, 2015 4:10:50 AM
Subject: [Lucee] Errors in catalina log - address already in use: bind

Hi,

I have noticed strange errors in my catalina log in tomcat which appear
after each server startup.

These don't look pretty, but I have not noticed any specific issues so
far, apart from the errors themselves:

*SEVERE [main] org.apache.coyote.AbstractProtocol.init Failed to initialize

end point associated with ProtocolHandler
["http-nio-8888"]java.net.BindException: Address already in use: bindSEVERE
[main] org.apache.catalina.core.StandardService.initInternal Failed to
initialize connector [Connector[HTTP/1.1-8888]]Caused by:
org.apache.catalina.LifecycleException: Protocol handler initialization

failedCaused by: java.net.BindException: Address already in use: bindand so
on... *I am running the latest stable Lucee on IIS 7 and could see this

happening on my install of Lucee on Tomcat 7 / Java 1.7 and after upgrading
to Tomcat 8/ Java 1.8 also.

I thought something else might be blocking the port and runned:

*netstat -nao | findstr ":8888"*

which resulted in:

*TCP 0.0.0.0:8888 0.0.0.0:0 LISTENING 344
TCP [::]:8888 [::]:0 LISTENING 344*

where 344 is the id of the tomcat8.exe process


Would anybody know what is going on here ?


Regards

Ivan

--
See Lucee at CFCamp Oct 22 & 23 2015 @ Munich Airport, Germany - Get your ticket NOW - http://www.cfcamp.org/
---
You received this message because you are subscribed to the Google Groups "Lucee" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lucee+un...@googlegroups.com.
To post to this group, send email to lu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/9e749332-9502-458b-ae27-eafcbb35d4d1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Ivan Rotrekl]

Hi Jordan,

thanks for response. Well, I have seen this error  in the log on my dev machine as well as the production sever, for as long as I can remember. I could not attribute any issue to it, so I did not care much. Recently I have re-installed Lucee to upgrade tomcat and jvm and was surprised to see it still there, so I became bit more curious. Looks like something is misconfigured in tomcat or java ?

Similarly, I can see in the log after each restart this info:

The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path

So I was wondering: Is this library something which should be installed and could be useful for Lucee ?

Regards

Ivan

[David Eurenius]

Hi

The info is just f.y.i, it has been there for years even on ACF.

The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path

If you really want to remove the entry from the log-files, try following this thread:

http://stackoverflow.com/questions/8716259/what-does-the-apr-based-apache-tomcat-native-library-was-not-found-mean

It seems that you are able to add 1 dll file to the bin-folder, restart and it should be gone.

I have not personally tested it, but please go ahead in a test environment.

--David

[Ivan Rotrekl]

Hi David

 thanks ! I have tried to follow your advice and I have found out  that this library is actually already included in Lucee installer and exists in the tomcat/bin folder.

There are 2 files:  tcnative-1-win32.dll and tcnative-1-win64.dll.

One of these just has to be choosen and renamed back  to  tcnative-1.dll and it gets loaded.

Regards

Ivan