János Löbb wrote:

On Mar 29, 2009, at 8:58 PM, Caldarale, Charles R wrote:

From: János Löbb [mailto:janos.l...@yale.edu]
Subject: Replicated context is failing...or not ?

Mar 29, 2009 11:59:47 AM org.apache.catalina.startup.HostConfig
deployDescriptor
WARNING: A docBase /usr/local/apache-tomcat-6.0.18/webapps/ROOT inside
the host appBase has been specified, and will be ignored

The above likely doesn't have anything to do with the replication problem, but on the off chance it does, you really should fix it. Looks like you have an illegal <Context> element somewhere.

- Chuck



Hi Chuck,

I am looking into it, but for the first glance I see no other contexts hanging around. I found, that on one of the machines, pathsrv1, it has the Apple packaged Tomcat, I also have the following stack trace in the log when tomcat starts up:

Mar 29, 2009 11:41:46 AM org.apache.catalina.core.AprLifecycleListener init INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: .:/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java
Mar 29, 2009 11:41:46 AM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
Mar 29, 2009 11:41:46 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 1890 ms
Mar 29, 2009 11:41:46 AM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Mar 29, 2009 11:41:46 AM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.18
Mar 29, 2009 11:41:46 AM org.apache.catalina.ha.tcp.SimpleTcpCluster start
INFO: Cluster is about to start
Mar 29, 2009 11:41:46 AM org.apache.catalina.tribes.transport.ReceiverBase bind
INFO: Receiver Server Socket bound to:/10.48.106.107:4000
Mar 29, 2009 11:41:46 AM org.apache.catalina.tribes.membership.McastServiceImpl setupSocket
INFO: Setting cluster mcast soTimeout to 500
Mar 29, 2009 11:41:46 AM org.apache.catalina.tribes.membership.McastServiceImpl waitForMembers INFO: Sleeping for 1000 milliseconds to establish cluster membership, start level:4 Mar 29, 2009 11:41:46 AM org.apache.catalina.ha.tcp.SimpleTcpCluster memberAdded INFO: Replication member added:org.apache.catalina.tribes.membership.MemberImpl[tcp://{10, 48, 106, 44}:4000,{10, 48, 106, 44},4000, alive=4214446187,id={123 32 103 -62 110 51 77 58 -113 -57 43 -80 4 -20 -26 -108 }, payload={}, command={}, domain={}, ] Mar 29, 2009 11:41:46 AM org.apache.catalina.ha.tcp.SimpleTcpCluster memberAdded INFO: Replication member added:org.apache.catalina.tribes.membership.MemberImpl[tcp://{10, 48, 106, 101}:4000,{10, 48, 106, 101},4000, alive=16204423,id={124 -97 -40 -51 -99 -126 69 -73 -80 74 110 -9 80 -74 64 86 }, payload={}, command={}, domain={}, ] Mar 29, 2009 11:41:47 AM org.apache.catalina.tribes.transport.nio.NioReceiver listen
SEVERE: Unable to process request in NioReceiver
java.net.SocketException: Invalid argument
    at sun.nio.ch.Net.setIntOption0(Native Method)
    at sun.nio.ch.Net.setIntOption(Net.java:152)
    at sun.nio.ch.SocketChannelImpl$1.setInt(SocketChannelImpl.java:372)
    at sun.nio.ch.SocketOptsImpl.setInt(SocketOptsImpl.java:46)
at sun.nio.ch.SocketOptsImpl$IP.typeOfService(SocketOptsImpl.java:249)
    at sun.nio.ch.OptionAdaptor.setTrafficClass(OptionAdaptor.java:158)
    at sun.nio.ch.SocketAdaptor.setTrafficClass(SocketAdaptor.java:330)
at org.apache.catalina.tribes.transport.nio.NioReceiver.listen(NioReceiver.java:273) at org.apache.catalina.tribes.transport.nio.NioReceiver.run(NioReceiver.java:353)
    at java.lang.Thread.run(Thread.java:613)
Mar 29, 2009 11:41:47 AM org.apache.catalina.tribes.membership.McastServiceImpl waitForMembers
INFO: Done sleeping, membership established, start level:4

this is fixed by adding
|-Djava.net.preferIPv4Stack=true

to your command line
|

I realized that I had a mispell for jvmRoute in the server.xml of reptile, where jvmRoute=reptile1 instead of jvmRoute=reptile. This will be remedied tonight. Reptile is the machine to whom pathsrv1 should fail over, so it is possible that it was also the problem with the replicated context stack trace. The real workers in the workers.properties file are pathsrv1, raid2b and reptile.

Thanks ahead,

János



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




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

Reply via email to