0 Replies Latest reply on Mar 7, 2002 7:58 AM by osman vurgun

    JMS, SocketException (broken pipe), 2.4.4

    osman vurgun Newbie


      referring to my topic posted at the 6th of March I've tried
      out JBoss 2.4.4.

      If i terminate any process (CTRL+X, CTRL+Z) which is currently communicating with the messaging system, an exception is thrown and JMS hangs up. Every client, which is still conneted, hangs up, too. New connections can be set up, but any further activity concerning JMS hangs up.

      If this behaviour is default, JBossMQ is no alternative for any serious production level application.

      Does anyone have informations about this behaviour? I'm currently evaluating alternatives for WebLogic-Server - if there is no workaround or explanation, JBoss isn't the choice.