• Bug
  • Status: Closed
  • 2 Major
  • Resolution: Fixed
  • DSO:L2
  • kkannaiy
  • Reporter: tindor
  • October 16, 2007
  • 0
  • Watchers: 0
  • February 12, 2013
  • October 19, 2007

Description

In active-passive mode, then one of the clients is killed, the passive server goes down with this exception :

narabota2:~/terracotta-2.4.4/bin# sh start-tc-server.sh -f ../tc-config.xml 2007-10-16 13:22:42,966 INFO - Terracotta 2.4.4, as of 20071003-131012 (Revision 5783 by [email protected] from 2.4) 2007-10-16 13:22:44,319 INFO - Configuration loaded from the file at ‘/root/terracotta-2.4.4/bin/../tc-config.xml’. 2007-10-16 13:22:44,398 INFO - Log file: ‘/root/terracotta-2.4.4/bin/../logs/server2-logs/terracotta-server.log’. 2007-10-16 13:22:45,370 INFO - JMX Server started. Available at URL[service:jmx:jmxmp://localhost:9520] Oct 16, 2007 1:22:47 PM org.apache.catalina.tribes.transport.ReceiverBase bind INFO: Receiver Server Socket bound to:/192.168.168.71:9530 2007-10-16 13:22:47,524 INFO - NodeID[tcp://192.168.168.70:9530] joined the cluster Oct 16, 2007 1:22:47 PM org.apache.catalina.tribes.io.BufferPool getBufferPool INFO: Created a buffer pool with max size:104857600 bytes of type:org.apache.catalina.tribes.io.BufferPool15Impl 2007-10-16 13:22:47,579 INFO - Moved to State[ PASSIVE-UNINITIALIZED ] 2007-10-16 13:22:47,930 INFO - Moved to State[ PASSIVE-STANDBY ] java.lang.AssertionError: This should never be called. at com.tc.objectserver.tx.PassiveTransactionAccount.clientDead(PassiveTransactionAccount.java:73) at com.tc.objectserver.tx.ServerTransactionManagerImpl.shutdownClient(ServerTransactionManagerImpl.java:126) at com.tc.objectserver.handler.ChannelLifeCycleHandler.channelRemoved(ChannelLifeCycleHandler.java:67) at com.tc.objectserver.handler.ChannelLifeCycleHandler.handleEvent(ChannelLifeCycleHandler.java:52) at com.tc.async.impl.StageImpl$WorkerThread.run(StageImpl.java:142)

The only way to have it back is to start it again.

Steps to reproduce : start 2 servers start 2 tomcat instances with TC_CONFIG_PATH=”192.168.168.71:9510,192.168.168.70:9510” kill one of the tomcats and watch the logs of the passive server

Comments

Fiona OShea 2007-10-16

Can you check this one out?

Fiona OShea 2007-10-16

Ortega only…I am getting confused

Kalai Kannaiyan 2007-11-20

Retested this issue with rev 6252, it is working as expected. Closing this issue.

Steps:

  1. Install the kit rev6252
  2. Create the tc-config.xml to support network-based active passive server mention active server: su10qa0, passive server: su10qa1, gc: on and persistence:on
  3. On su10qa0, Navigate to install-dir/bin and execute ./start-tc-server.sh -f tc-config.xml
  4. Active server started successfully on su10qa0:9520
  5. On su10qa1, Navigate to install-dir/bin and execute ./start-tc-server.sh -f tc-config.xml 6.Passive server started successfully on su10qa1:8520
  6. Before starting the tomcat instances -> set the TC_INSTALL_DIR
  7. set the TC_CONFIG_PATH=”su10qa0:9510,su10qa1:9510”
  8. set the bootjarpath
  9. start the tomcat server instance 1 on su10qa6
  10. start the tomcat server instance 2 on su10qa7
  11. Verify that the two clients are displayed in the admin console
  12. kill the tomcat 1

Actual: Active and passive servers are running without any issues