0 Replies Latest reply on Oct 21, 2010 11:00 PM by Jing Shi

    jboss problem on MSCS

    Jing Shi Newbie

      Hi, All,

       

      We have a vendor application which is built in JBOSS 4.0.1. Data source is SQL Server 2000 and IBM MQ. It was running very well in one single server, but recently we built active - passive cluster server containing Node A and Node B, using MSCS. Then the application becomes unstable. JBoss reports the next error. The strange thing is the error occured not at the beginning, instead it is after the application ran well for sometime, ex 1hr.

       

      Appreciate sharing your advice if anybody has the same experience.

       

      javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out]
      at org.jnp.interfaces.NamingContext.discoverServer(NamingContext.java:1159)
      at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1239)
      at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:527)
      at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:520)
      at javax.naming.InitialContext.lookup(InitialContext.java:351)
      at jp.co.scs.davao.inf.fw.interfaces.EJBDavaoUtil.lookupHome(EJBDavaoUtil.java:25)
      at jp.co.scs.davao.inf.fw.interfaces.EJBDavaoUtil.getHome(EJBDavaoUtil.java:59)
      at jp.co.scs.davao.eai.util.DavaoInvoker.invokeEjbDavao(DavaoInvoker.java:139)
      at jp.co.scs.davao.eai.util.DavaoInvoker.invoke(DavaoInvoker.java:101)
      at jp.co.scs.davao.eai.util.DavaoThreadInvoker.run(DavaoThreadInvoker.java:198)
      Caused by: java.net.SocketTimeoutException: Receive timed out
      at java.net.PlainDatagramSocketImpl.receive0(Native Method)
      at java.net.PlainDatagramSocketImpl.receive(PlainDatagramSocketImpl.java:136)
      at java.net.DatagramSocket.receive(DatagramSocket.java:712)
      at org.jnp.interfaces.NamingContext.discoverServer(NamingContext.java:1129)
      ... 9 more

       

      best regards,

      jing