SEVERE: Failed to initialize end point associated with ProtocolHandler [http-bio-443]

2013-04-24 Thread James H. H. Lampert
We're trying to bring up SSL in Tomcat on a customer AS/400 (an E4C at 
V7R1, using the /QOpenSys/QIBM/ProdData/JavaVM/jdk60/64bit JVM), and 
every time we launch CATALINA, we get



SEVERE: Failed to initialize end point associated with ProtocolHandler 
[http-bio-443]
Throwable occurred: java.net.BindException: The socket name is already in use. 
null:443


Earlier today, I found something (I couldn't tell WHAT, because there 
were no jobs associated with the port) listening (and idle for 16 hours) 
on 443, on one of the IP addresses, but now, nothing on that port. I 
also looked for restrictions on that port, and there aren't any.


Any ideas of where to look next?

--
JHHL

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org



Re: SEVERE: Failed to initialize end point associated with ProtocolHandler [http-bio-443]

2013-04-24 Thread Neven Cvetkovic
James,

Something else is listening on port 443 (SSL port). I am no AS/400 expert,
but you should be able to see listening processes, e.g.

Linux:  netstat -vatpn | grep 443
Windows: netstat -aon | findstr 443

Did you try connecting to the port 443?

Btw in your log null is actual real IP address, you just removed it for
the mailing list, correct?




On Wed, Apr 24, 2013 at 4:50 PM, James H. H. Lampert 
jam...@touchtonecorp.com wrote:

 We're trying to bring up SSL in Tomcat on a customer AS/400 (an E4C at
 V7R1, using the /QOpenSys/QIBM/ProdData/**JavaVM/jdk60/64bit JVM), and
 every time we launch CATALINA, we get

  SEVERE: Failed to initialize end point associated with ProtocolHandler
 [http-bio-443]
 Throwable occurred: java.net.BindException: The socket name is already in
 use. null:443


 Earlier today, I found something (I couldn't tell WHAT, because there were
 no jobs associated with the port) listening (and idle for 16 hours) on 443,
 on one of the IP addresses, but now, nothing on that port. I also looked
 for restrictions on that port, and there aren't any.

 Any ideas of where to look next?

 --
 JHHL

 --**--**-
 To unsubscribe, e-mail: 
 users-unsubscribe@tomcat.**apache.orgusers-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org




Re: SEVERE: Failed to initialize end point associated with ProtocolHandler [http-bio-443]

2013-04-24 Thread James H. H. Lampert

Neven Cvetkovic wrote:


Btw in your log null is actual real IP address, you just removed it for
the mailing list, correct?


That's the actual message from CATALINA.OUT, verbatim. Perhaps we're not 
specifying an IP address in the configuration files (how would one do 
that?), and (with several IP addresses assigned to the box) it's having 
trouble deciding which one we want?


And as I said, earlier today, I did find *something* else listening on 
443 (incidentally, on an AS/400, NETSTAT has a synonym, more 
idiomatically native to the OS, of WRKTCPSTS), but now there's no trace 
of that something else, and even when it was there, it was kind of elusive.


--
JHHL

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org



Re: SEVERE: Failed to initialize end point associated with ProtocolHandler [http-bio-443]

2013-04-24 Thread Jakub 1983
James,

try to set tomcat port to 1443 and check, and write us if it starts than,

try to start knock knock server with default  port, than change it to
443 port -
http://docs.oracle.com/javase/tutorial/networking/sockets/examples/KnockKnockServer.java
(link and explanation is here
http://docs.oracle.com/javase/tutorial/networking/sockets/clientServer.html)

write about the results

regards
Jakub





On Wed, Apr 24, 2013 at 11:23 PM, James H. H. Lampert 
jam...@touchtonecorp.com wrote:

 Neven Cvetkovic wrote:

  Btw in your log null is actual real IP address, you just removed it
 for
 the mailing list, correct?


 That's the actual message from CATALINA.OUT, verbatim. Perhaps we're not
 specifying an IP address in the configuration files (how would one do
 that?), and (with several IP addresses assigned to the box) it's having
 trouble deciding which one we want?

 And as I said, earlier today, I did find *something* else listening on 443
 (incidentally, on an AS/400, NETSTAT has a synonym, more idiomatically
 native to the OS, of WRKTCPSTS), but now there's no trace of that something
 else, and even when it was there, it was kind of elusive.

 --
 JHHL

 --**--**-
 To unsubscribe, e-mail: 
 users-unsubscribe@tomcat.**apache.orgusers-unsubscr...@tomcat.apache.org

 For additional commands, e-mail: users-h...@tomcat.apache.org