XMLWordPrintable

Details

    • Support Patch
    • Resolution: Done
    • Major
    • 4.3.0.GA, 4.2.0.GA_CP02
    • 4.2.0.GA_CP01
    • None
    • None
    • JBPAPP_4_2_0_GA_CP01_JBPAPP-364
    • Release Notes
    • Hide
      PATCH NAME:
              JBPAPP-387
      PRODUCT NAME:
              JBoss EAP / Application Platform
      VERSION:
             4.2.0 CP01
      DESCRIPTION:
      Corrects failover problem when integrating with TIBCO EMS
      MANUAL INSTALL INSTRUCTIONS:
      For EJB 2.x MDBs, replace your JBOSS_HOME/server/<server-config>/lib with this jboss.jar To configure this capability you will need to add three elements to your jboss.xml descriptor:

      <ForceClearOnShutdown>true | false</ForceClearOnShutdown>

      This will enable the general behavior to move past the issue of outstanding Server Sessions

      <ForceClearInterval>n milliseconds</ForceClearInterval>

      This value, in milliseconds is the amount of wait time between each attempt to clear the ServerSessionPool. This should be set to something reasonable for your environment, I would suggest starting with something like 5ms and incrementing this value if this is too short.

      <ForceClearAttempts>n attempts</ForceClearAttempts>

      This is the number of attempts that JBoss will allow in waiting for the pool to clear. Once this threshhold has been met, the pool will be recycled regardless of whether or not there is outstanding work in the pool.

      For EJB 3.0 MDBs, replace your JBOSS_HOME/server/<server-config>/deploy/jms with the attached jms-ra.rar To configure this capability you will need to add new ActivationConfigProperties forceClearOnShutdown, forceClearInterval, and forceClearAttempts.

      COMPATIBILITY:
              None
      DEPENDENCIES:
             JBoss EAP 4.2.0 CP01
      SUPERSEDES:
              None
      SUPERSEDED BY:
              None
      CREATOR:
              Weston Price, William DeCoste
      DATE:
              Tue Oct 30 13:20:34 PDT 2007
      Show
      PATCH NAME:          JBPAPP-387 PRODUCT NAME:         JBoss EAP / Application Platform VERSION:        4.2.0 CP01 DESCRIPTION: Corrects failover problem when integrating with TIBCO EMS MANUAL INSTALL INSTRUCTIONS: For EJB 2.x MDBs, replace your JBOSS_HOME/server/<server-config>/lib with this jboss.jar To configure this capability you will need to add three elements to your jboss.xml descriptor: <ForceClearOnShutdown>true | false</ForceClearOnShutdown> This will enable the general behavior to move past the issue of outstanding Server Sessions <ForceClearInterval>n milliseconds</ForceClearInterval> This value, in milliseconds is the amount of wait time between each attempt to clear the ServerSessionPool. This should be set to something reasonable for your environment, I would suggest starting with something like 5ms and incrementing this value if this is too short. <ForceClearAttempts>n attempts</ForceClearAttempts> This is the number of attempts that JBoss will allow in waiting for the pool to clear. Once this threshhold has been met, the pool will be recycled regardless of whether or not there is outstanding work in the pool. For EJB 3.0 MDBs, replace your JBOSS_HOME/server/<server-config>/deploy/jms with the attached jms-ra.rar To configure this capability you will need to add new ActivationConfigProperties forceClearOnShutdown, forceClearInterval, and forceClearAttempts. COMPATIBILITY:         None DEPENDENCIES:        JBoss EAP 4.2.0 CP01 SUPERSEDES:         None SUPERSEDED BY:         None CREATOR:         Weston Price, William DeCoste DATE:         Tue Oct 30 13:20:34 PDT 2007

    Attachments

      1. jboss.jar
        2.01 MB
      2. jms-ra.rar
        70 kB

      Issue Links

        Activity

          People

            wdecoste1@redhat.com William Decoste (Inactive)
            wdecoste1@redhat.com William Decoste (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: