Re: [Resin-interest] Start up problem
Here is my netstat dump. I am running in a console as root when I try to start resin up. I can start Jetty, but I cannot start Glassfish as well. I get a similiar error. I thought maybe it had to with resolving its domain name as it is behind a firewall which is doing NAT, but I think I have taken care of that with an entry in the hosts file. I do have the ports open in the iptables firewall as well. Any ideas? Thanks, Tony Active Internet connections (w/o servers) Proto Recv-Q Send-Q Local Address Foreign Address Stat e tcp 1 0 mine10.zakula.com:40764 cobe-if-a.mirrorservic:http CLOS E_WAIT tcp 52 0 mine10.zakula.com:ssh 192.168.1.2:sixtrak ESTA BLISHED tcp 0 1 mine10.zakula.com:40074 mine10.zakula.com:pop3 SYN_ SENT tcp 0 1 mine10.zakula.com:40998 mine10.zakula.com:pop3 SYN_ SENT tcp 0 1 mine10.zakula.com:40999 mine10.zakula.com:pop3 SYN_ SENT tcp 0 1 mine10.zakula.com:47892 mine10.zakula.com:smtp SYN_ SENT tcp 0 1 mine10.zakula.com:47893 mine10.zakula.com:smtp SYN_ SENT tcp 0 1 mine10.zakula.com:46359 mine10.zakula.com:smtp SYN_ SENT tcp 1 0 mine10.zakula.com:54406 ie.freshrpms.net:http CLOS E_WAIT Active UNIX domain sockets (w/o servers) Proto RefCnt Flags Type State I-Node Path unix 13 [ ] DGRAM 6222 /dev/log unix 2 [ ] DGRAM 1476 @/org/kernel/udev/udevd unix 2 [ ] DGRAM 7206 @/org/freedesktop/hal/u dev_event unix 2 [ ] DGRAM 88252 unix 2 [ ] DGRAM 9722 unix 2 [ ] DGRAM 8122 unix 2 [ ] DGRAM 8114 unix 3 [ ] STREAM CONNECTED 8011 /var/run/dbus/system_bu s_socket unix 3 [ ] STREAM CONNECTED 8010 unix 3 [ ] STREAM CONNECTED 7953 @/var/run/hald/dbus-C9r PpArtSW unix 3 [ ] STREAM CONNECTED 7948 unix 3 [ ] STREAM CONNECTED 7803 /var/run/acpid.socket unix 3 [ ] STREAM CONNECTED 7802 unix 3 [ ] STREAM CONNECTED 7789 /var/run/dbus/system_bu s_socket unix 3 [ ] STREAM CONNECTED 7788 unix 3 [ ] STREAM CONNECTED 7797 @/var/run/hald/dbus-C9r PpArtSW unix 3 [ ] STREAM CONNECTED 7786 unix 3 [ ] STREAM CONNECTED 7201 @/var/run/hald/dbus-vaH MTYCoih unix 3 [ ] STREAM CONNECTED 7200 unix 2 [ ] DGRAM 7199 unix 2 [ ] DGRAM 6877 unix 2 [ ] DGRAM 6840 unix 2 [ ] DGRAM 6667 unix 3 [ ] STREAM CONNECTED 6594 unix 3 [ ] STREAM CONNECTED 6593 unix 3 [ ] STREAM CONNECTED 6496 unix 3 [ ] STREAM CONNECTED 6495 unix 2 [ ] DGRAM 6368 unix 2 [ ] DGRAM 6357 unix 2 [ ] DGRAM 6230 unix 3 [ ] STREAM CONNECTED 6184 unix 3 [ ] STREAM CONNECTED 6183 Vic Simkus wrote: Tony wrote: Hi, I have been trying to install and run resin on a Centos 5 system. I run it fine on Windows. Everything installs fine on Centos, but when I try to run the resin.jar file with all of the default configuration, I get the following error: Aug 24, 2007 11:26:39 AM com.caucho.boot.ResinWatchdog run INFO: java.net.BindException: Cannot assign requested address java.net.BindException: Cannot assign requested address at java.net.PlainSocketImpl.socketBind(Native Method) at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:359) at java.net.ServerSocket.bind(ServerSocket.java:319) at java.net.ServerSocket.init(ServerSocket.java:185) at com.caucho.boot.ResinWatchdog.run(ResinWatchdog.java:496) at java.lang.Thread.run(Thread.java:619) The server is behind a firewall with an ip address of 192.168.1.3, but I have an entry in the hosts file with the machine name and the ip address. Any help would be appreciated. Thanks! Tony Sounds like something else is bound to a port that Resin is trying to use. Do a netstat and make sure that nothing is using ports 8080 and 6800. ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Start up problem
This is an old bug report, but it sounds like it might be the cause: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6206527 Centos is sort of a redhat derivative, right? anyway, assuming you are using JDK 5, you could try either a) upgrading to JDK 6 or b) disable IPv6. A workaround for RedHat-type users is to disable IPv6, by editing /etc/sysconfig/network and changing NETWORKING_IPV6=no. anyway, I have no idea if this is the actual issue. I just did a quick google search for java.net.BindException: Cannot assign requested address and came across this. It actually says it only happens when binding to the local address, but maybe that's what the watchdog process is doing?? ..mike.. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tony Zakula Sent: Friday, August 24, 2007 9:26 PM To: resin-interest@caucho.com Subject: [Resin-interest] Start up problem Hi, I have been trying to install and run resin on a Centos 5 system. I run it fine on Windows. Everything installs fine on Centos, but when I try to run the resin.jar file with all of the default configuration, I get the following error: Aug 24, 2007 11:26:39 AM com.caucho.boot.ResinWatchdog run INFO: java.net.BindException: Cannot assign requested address java.net.BindException: Cannot assign requested address at java.net.PlainSocketImpl.socketBind(Native Method) at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:359) at java.net.ServerSocket.bind(ServerSocket.java:319) at java.net.ServerSocket.init(ServerSocket.java:185) at com.caucho.boot.ResinWatchdog.run(ResinWatchdog.java:496) at java.lang.Thread.run(Thread.java:619) The server is behind a firewall with an ip address of 192.168.1.3, but I have an entry in the hosts file with the machine name and the ip address. Any help would be appreciated. Thanks! Tony ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Start up problem
Scott Ferguson wrote: On Aug 28, 2007, at 8:49 AM, Mike Wynholds wrote: This is an old bug report, but it sounds like it might be the cause: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6206527 Centos is sort of a redhat derivative, right? anyway, assuming you are using JDK 5, you could try either a) upgrading to JDK 6 or b) disable IPv6. A workaround for RedHat-type users is to disable IPv6, by editing /etc/sysconfig/network and changing NETWORKING_IPV6=no. anyway, I have no idea if this is the actual issue. I just did a quick google search for java.net.BindException: Cannot assign requested address and came across this. It actually says it only happens when binding to the local address, but maybe that's what the watchdog process is doing?? That's interesting. Thanks for finding this. The Watchdog does bind to port localhost:6600. That's how the stop command works and how the Watchdog can manage multiple Resin JVMs with a single watchdog process. -- Scott Is this a bug? or going to be considered a bug? I am wondering how this would work if I started multiple Resin installations on the same machine? ..mike.. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tony Zakula Sent: Friday, August 24, 2007 9:26 PM To: resin-interest@caucho.com Subject: [Resin-interest] Start up problem Hi, I have been trying to install and run resin on a Centos 5 system. I run it fine on Windows. Everything installs fine on Centos, but when I try to run the resin.jar file with all of the default configuration, I get the following error: Aug 24, 2007 11:26:39 AM com.caucho.boot.ResinWatchdog run INFO: java.net.BindException: Cannot assign requested address java.net.BindException: Cannot assign requested address at java.net.PlainSocketImpl.socketBind(Native Method) at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:359) at java.net.ServerSocket.bind(ServerSocket.java:319) at java.net.ServerSocket.init(ServerSocket.java:185) at com.caucho.boot.ResinWatchdog.run(ResinWatchdog.java:496) at java.lang.Thread.run(Thread.java:619) The server is behind a firewall with an ip address of 192.168.1.3, but I have an entry in the hosts file with the machine name and the ip address. Any help would be appreciated. Thanks! Tony ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Start up problem
Scott Ferguson wrote: On Aug 28, 2007, at 9:45 AM, Eric Kreiser wrote: That's interesting. Thanks for finding this. The Watchdog does bind to port localhost:6600. That's how the stop command works and how the Watchdog can manage multiple Resin JVMs with a single watchdog process. -- Scott Is this a bug? or going to be considered a bug? It's not a Resin bug. Binding to a local port is a capability of the JDK. We're certainly not going to work around a JDK bug that fundamental. -- Scott I don't follow. /Resin/ is binding the Watchdog process to 127.0.0.1:6600 right? And all that I am really concerned with is... how would/should I start multiple Resin servers on the same machine? How will this work if each is going to try to bind to 127.0.0.1:6600? I am wondering how this would work if I started multiple Resin installations on the same machine? ..mike.. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tony Zakula Sent: Friday, August 24, 2007 9:26 PM To: resin-interest@caucho.com Subject: [Resin-interest] Start up problem Hi, I have been trying to install and run resin on a Centos 5 system. I run it fine on Windows. Everything installs fine on Centos, but when I try to run the resin.jar file with all of the default configuration, I get the following error: Aug 24, 2007 11:26:39 AM com.caucho.boot.ResinWatchdog run INFO: java.net.BindException: Cannot assign requested address java.net.BindException: Cannot assign requested address at java.net.PlainSocketImpl.socketBind(Native Method) at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:359) at java.net.ServerSocket.bind(ServerSocket.java:319) at java.net.ServerSocket.(ServerSocket.java:185) at com.caucho.boot.ResinWatchdog.run(ResinWatchdog.java:496) at java.lang.Thread.run(Thread.java:619) The server is behind a firewall with an ip address of 192.168.1.3, but I have an entry in the hosts file with the machine name and the ip address. Any help would be appreciated. Thanks! Tony ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com mailto:resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest -- This message has been scanned for viruses and dangerous content by *MailScanner* http://www.mailscanner.info/, and is believed to be clean. ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Start up problem
I don't follow. Resin is binding the Watchdog process to 127.0.0.1:6600 right? And all that I am really concerned with is... how would/should I start multiple Resin servers on the same machine? How will this work if each is going to try to bind to 127.0.0.1:6600? If you are just using a machine with 1 or 2 CPU's then VMware license for the 'Server' product will let you use It free. Otherwise you would have to buy one of their products. -Rob ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Start up problem
I have been googling for several days on this. I agree, it is a probably a problem on the machine itself. I am just trying to find clues as to how to find it. I am using the latest java machine: java -version puts out: java version "1.6.0_02" Java(TM) SE Runtime Environment (build 1.6.0_02-b05) Java HotSpot(TM) Client VM (build 1.6.0_02-b05, mixed mode, sharing) I have ipv6 disabled. I am starting the process from a console logged in as root. Jetty starts fine, but no other app server will. Any clues as to where to look? Tony Scott Ferguson wrote: On Aug 28, 2007, at 9:45 AM, Eric Kreiser wrote: That's interesting. Thanks for finding this. The Watchdog does bind to port localhost:6600. That's how the "stop" command works and how the Watchdog can manage multiple Resin JVMs with a single watchdog process. -- Scott Is this a bug? or going to be considered a bug? It's not a Resin bug. Binding to a local port is a capability of the JDK. We're certainly not going to work around a JDK bug that fundamental. -- Scott I am wondering how this would work if I started multiple Resin installations on the same machine? ..mike.. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Tony Zakula Sent: Friday, August 24, 2007 9:26 PM To: resin-interest@caucho.com Subject: [Resin-interest] Start up problem Hi, I have been trying to install and run resin on a Centos 5 system. I run it fine on Windows. Everything installs fine on Centos, but when I try to run the resin.jar file with all of the default configuration, I get the following error: Aug 24, 2007 11:26:39 AM com.caucho.boot.ResinWatchdog run INFO: java.net.BindException: Cannot assign requested address java.net.BindException: Cannot assign requested address at java.net.PlainSocketImpl.socketBind(Native Method) at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:359) at java.net.ServerSocket.bind(ServerSocket.java:319) at java.net.ServerSocket.(ServerSocket.java:185) at com.caucho.boot.ResinWatchdog.run(ResinWatchdog.java:496) at java.lang.Thread.run(Thread.java:619) The server is behind a firewall with an ip address of 192.168.1.3, but I have an entry in the hosts file with the machine name and the ip address. Any help would be appreciated. Thanks! Tony ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Start up problem
You can set the watchdog-port for each server you start up, whether you use a single resin.conf for a cluster of servers on the same machine, or multiple resin.confs. 6600 is just the default watchdog port. that is how you start up multiple resin instances on the same machine. as for the bug, binding the watchdog process to the configured port (6600 by default) of the localhost seems the right thing to do. it's just RedHat OSes with JDK 5 that have this bug. JDK 6 is fixed I think, and it has been back ported to JDK 1.4. someone in the bug I posted earlier asked about a back-port to JDK 5. maybe 1.5.0_12 has it, I dunno. that bug was from a while ago. so I would try upgrading to the latest JDK that you can, and if that doesn't work, disable IPv6 if you can. if you can't do any of those things, than I don't know what to tell you. ..mike.. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Eric Kreiser Sent: Tuesday, August 28, 2007 10:50 AM To: General Discussion for the Resin application server Subject: Re: [Resin-interest] Start up problem Scott Ferguson wrote: On Aug 28, 2007, at 9:45 AM, Eric Kreiser wrote: That's interesting. Thanks for finding this. The Watchdog does bind to port localhost:6600. That's how the stop command works and how the Watchdog can manage multiple Resin JVMs with a single watchdog process. -- Scott Is this a bug? or going to be considered a bug? It's not a Resin bug. Binding to a local port is a capability of the JDK. We're certainly not going to work around a JDK bug that fundamental. -- Scott I don't follow. Resin is binding the Watchdog process to 127.0.0.1:6600 right? And all that I am really concerned with is... how would/should I start multiple Resin servers on the same machine? How will this work if each is going to try to bind to 127.0.0.1:6600? I am wondering how this would work if I started multiple Resin installations on the same machine? ..mike.. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tony Zakula Sent: Friday, August 24, 2007 9:26 PM To: resin-interest@caucho.com Subject: [Resin-interest] Start up problem Hi, I have been trying to install and run resin on a Centos 5 system. I run it fine on Windows. Everything installs fine on Centos, but when I try to run the resin.jar file with all of the default configuration, I get the following error: Aug 24, 2007 11:26:39 AM com.caucho.boot.ResinWatchdog run INFO: java.net.BindException: Cannot assign requested address java.net.BindException: Cannot assign requested address at java.net.PlainSocketImpl.socketBind(Native Method) at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:359) at java.net.ServerSocket.bind(ServerSocket.java:319) at java.net.ServerSocket.(ServerSocket.java:185) at com.caucho.boot.ResinWatchdog.run(ResinWatchdog.java:496) at java.lang.Thread.run(Thread.java:619) The server is behind a firewall with an ip address of 192.168.1.3, but I have an entry in the hosts file with the machine name and the ip address. Any help would be appreciated. Thanks! Tony ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest -- This message has been scanned for viruses and dangerous content by MailScanner http://www.mailscanner.info
Re: [Resin-interest] Start up problem
On Aug 28, 2007, at 11:01 AM, Leland, Robert wrote: It could be designed so that it becomes a single service, with only one instance of the process running no matter how many instances of resin are running. It does that now. -- Scott ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Start up problem
Tony Zakula wrote: Hi, I have been trying to install and run resin on a Centos 5 system. I run it fine on Windows. Everything installs fine on Centos, but when I try to run the resin.jar file with all of the default configuration, I get the following error: Aug 24, 2007 11:26:39 AM com.caucho.boot.ResinWatchdog run INFO: java.net.BindException: Cannot assign requested address java.net.BindException: Cannot assign requested address at java.net.PlainSocketImpl.socketBind(Native Method) at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:359) at java.net.ServerSocket.bind(ServerSocket.java:319) at java.net.ServerSocket.init(ServerSocket.java:185) at com.caucho.boot.ResinWatchdog.run(ResinWatchdog.java:496) at java.lang.Thread.run(Thread.java:619) The server is behind a firewall with an ip address of 192.168.1.3, but I have an entry in the hosts file with the machine name and the ip address. Any help would be appreciated. Thanks! Tony Sounds like something else is bound to a port that Resin is trying to use. Do a netstat and make sure that nothing is using ports 8080 and 6800. ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Start up problem
On Aug 27, 2007, at 11:56 AM, Vic Simkus wrote: Sounds like something else is bound to a port that Resin is trying to use. Do a netstat and make sure that nothing is using ports 8080 and 6800. that, or he's trying to use a port 1024 (e.g. 80) and he's not running as root. there's certainly something about this in the resin docs, somewhere or other. -- joe ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
