Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-364

Logger in HTTPClientInvoker should be static

XMLWordPrintable

    • Icon: Support Patch Support Patch
    • Resolution: Done
    • Icon: Major Major
    • None
    • 4.2.0.GA_CP01
    • None
    • None
    • Public
    • Hide
      PATCH NAME:
              JBPAPP-364
      PRODUCT NAME:
              JBoss EAP / Application Platform
      VERSION:
             4.2.0 CP01
      DESCRIPTION:
      For JBPAPP-364
      Corrects NPE coming from uninitialized (non static) Logger

      For JBPAPP-415
      Corrects WSDL URL

      For JBPAPP-387
      Corrects failover problem when integrating with TIBCO EMS

      JBPAPP-363
      Supports configurable JSESSIONID

      MANUAL INSTALL INSTRUCTIONS:
      For JBPAPP-364
      Copy the attached jboss-remoting.jar file over the version in %JBOSS_HOME%/client, %JBOSS_HOME%/server/default/lib, %JBOSS_HOME%/server/all/lib, and %JBOSS_HOME%/server/production/lib of a JBoss EAP 4.2.0 installation.

      For JBPAPP-415
      Copy the attached jbossws-client.jar file over the version in %JBOSS_HOME%/client and the attached jbossws-core.jar file over the version in %JBOSS_HOME%/server/%SERVER_CONFIG%/deploy/jbossws.sar of a JBoss EAP 4.2.0 CP01 installation.

      For JBPAPP-387
      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.

      JBPAPP-363
      Copy the attached jbossweb.jar file over the version in %JBOSS_HOME%/server/%SERVER_CONFIG%/deploy/jboss-web.deployer of a JBoss EAP 4.2.0 CP01 installation.

      COMPATIBILITY:
              None
      DEPENDENCIES:
             JBoss EAP 4.2.0 CP01
      SUPERSEDES:
              None
      SUPERSEDED BY:
              None
      CREATOR:
              Ron Sigal, William DeCoste
      DATE:
              Tue 10/23/2007 15:34:47
      Show
      PATCH NAME:          JBPAPP-364 PRODUCT NAME:         JBoss EAP / Application Platform VERSION:        4.2.0 CP01 DESCRIPTION: For JBPAPP-364 Corrects NPE coming from uninitialized (non static) Logger For JBPAPP-415 Corrects WSDL URL For JBPAPP-387 Corrects failover problem when integrating with TIBCO EMS JBPAPP-363 Supports configurable JSESSIONID MANUAL INSTALL INSTRUCTIONS: For JBPAPP-364 Copy the attached jboss-remoting.jar file over the version in %JBOSS_HOME%/client, %JBOSS_HOME%/server/default/lib, %JBOSS_HOME%/server/all/lib, and %JBOSS_HOME%/server/production/lib of a JBoss EAP 4.2.0 installation. For JBPAPP-415 Copy the attached jbossws-client.jar file over the version in %JBOSS_HOME%/client and the attached jbossws-core.jar file over the version in %JBOSS_HOME%/server/%SERVER_CONFIG%/deploy/jbossws.sar of a JBoss EAP 4.2.0 CP01 installation. For JBPAPP-387 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. JBPAPP-363 Copy the attached jbossweb.jar file over the version in %JBOSS_HOME%/server/%SERVER_CONFIG%/deploy/jboss-web.deployer of a JBoss EAP 4.2.0 CP01 installation. COMPATIBILITY:         None DEPENDENCIES:        JBoss EAP 4.2.0 CP01 SUPERSEDES:         None SUPERSEDED BY:         None CREATOR:         Ron Sigal, William DeCoste DATE:         Tue 10/23/2007 15:34:47

      Fix for http://jira.jboss.com/jira/browse/JBREM-750

      This JIRA has become the roll-up for the following:

      JBPAPP-364 (Logger in HTTPClientInvoker should be static)
      JBPAPP-415 (Address in WSDL - Port value is -1 when server is requested with default port 80)
      JBPAPP-387 (jms server failover with tibco ems)
      JBPAPP-363 (Configurable JSESSIONID Cookie Name)

        1. TESTS-TestSuites.txt
          2 kB
        2. jms-ra.rar
          70 kB
        3. jbossws-core.jar
          1.36 MB
        4. jbossws-client.jar
          1.36 MB
        5. jbossweb.jar
          2.31 MB
        6. jboss-remoting.jar
          835 kB
        7. jboss.jar
          2.01 MB

              alex.pinkin Alex Pinkin (Inactive)
              alex.pinkin Alex Pinkin (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 1 day
                  1d