glassfish
  1. glassfish
  2. GLASSFISH-18543

Deployment fails without error message when (JMS) connection pool has steady-pool-size greater than max-pool-size

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: 3.1.2_b23
    • Fix Version/s: None
    • Component/s: jca
    • Labels:
      None
    • Environment:

      java version "1.7.0_03"
      Java(TM) SE Runtime Environment (build 1.7.0_03-b04)
      Java HotSpot(TM) Client VM (build 22.1-b02, mixed mode)

      GlassFish Version: GlassFish Server Open Source Edition 3.1.2 (build 23)

      Description

      When deploying an EAR that has an invalid connector resource definition in glassfish-resources.xml the process fails without a clear error message.

      ==Admin Console==
      An error has occurred
      Error occurred during deployment: null. Please see server.log for more details.

      ==server.log==

      [#|2012-03-21T17:03:55.756+0100|INFO|glassfish3.1.2|org.glassfish.admingui|_ThreadID=48;_ThreadName=Thread-2;|uploadFileName=myAppEE6.ear|#]

      [#|2012-03-21T17:03:56.648+0100|INFO|glassfish3.1.2|javax.enterprise.system.container.web.com.sun.enterprise.web|_ThreadID=71;_ThreadName=Thread-2;|WEB0671: Loading application myAppEE6#myApp-war.war at [myApp-war]|#]

      [#|2012-03-21T17:03:56.723+0100|SEVERE|glassfish3.1.2|javax.enterprise.system.tools.admin.org.glassfish.deployment.admin|_ThreadID=71;_ThreadName=Thread-2;|The log message is empty or null. Please log an issue against the component in the logger field.|#]

      [#|2012-03-21T17:03:56.736+0100|INFO|glassfish3.1.2|org.glassfish.admingui|_ThreadID=48;_ThreadName=Thread-2;|Exception Occurred :Error occurred during deployment: null. Please see server.log for more details. |#]

      [#|2012-03-21T17:03:56.744+0100|SEVERE|glassfish3.1.2|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=48;_ThreadName=Thread-2;|java.lang.RuntimeException: Error occurred during deployment: null. Please see server.log for more details.
      at org.glassfish.admingui.common.util.RestUtil.parseResponse(RestUtil.java:414)
      [...]

      ==reproduce==

      Create an empty EE6 application with a glassfish-resources.xml in the app that has this resource:

      <connector-resource enabled="true" jndi-name="jms/myTopicFactory" object-type="user" pool-name="jms/myTopicFactory">
      <description/>
      </connector-resource>
      <connector-connection-pool associate-with-thread="false" connection-creation-retry-attempts="0" connection-creation-retry-interval-in-seconds="10" connection-definition-name="javax.jms.TopicConnectionFactory" connection-leak-reclaim="false" connection-leak-timeout-in-seconds="0" fail-all-connections="false" idle-timeout-in-seconds="300" is-connection-validation-required="false" lazy-connection-association="false" lazy-connection-enlistment="false" match-connections="true" max-connection-usage-count="0" max-pool-size="4" max-wait-time-in-millis="60000" name="jms/myTopicFactory" ping="false" pool-resize-quantity="2" pooling="true" resource-adapter-name="jmsra" steady-pool-size="5" validate-atmost-once-period-in-seconds="0"/>

      Notice:
      *max-pool-size=4
      *steady-pool-size=5

      You have to restart GF after this because it thinks the application name you tried to deploy the application with is occupied when you try to deploy again:
      Error occurred during deployment: Application name myAppEE6 is already in use. Please pick a different name.. Please see server.log for more details.

      The app was deployed to GF 2.1.1 before without problems.

        Activity

        Hide
        Hong Zhang added a comment -

        assgin to jagadish to take a look

        Show
        Hong Zhang added a comment - assgin to jagadish to take a look
        Hide
        mdo added a comment -

        I withdraw that this definitely worked with the 2.1 branch, can't warrant that we ever deployed app scoped resources as we either used NetBeans to deploy the descriptor resources in our development environment or manually created resources in production.

        Show
        mdo added a comment - I withdraw that this definitely worked with the 2.1 branch, can't warrant that we ever deployed app scoped resources as we either used NetBeans to deploy the descriptor resources in our development environment or manually created resources in production.

          People

          • Assignee:
            Jagadish
            Reporter:
            mdo
          • Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated: