[GLASSFISH-19445] [Regression] Creation of JMS resources fails Created: 14/Dec/12  Updated: 15/Dec/12  Resolved: 15/Dec/12

Status: Resolved
Project: glassfish
Component/s: jms
Affects Version/s: 4.0_b66
Fix Version/s: 4.0_b66

Type: Bug Priority: Critical
Reporter: Alex Pineda Assignee: David Zhao
Resolution: Works as designed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Glassfish 4.0 build 57 and greater, system running OEL 6, Firefox browser 10.6, JDK 1.7_03


Tags: 40-regression

 Description   

The following set of commands are part of the CLI regression test suite. Basically is creating the JMS resource and then checking them all. At this point, this whole scenario is failing. Noticed the issue starting with build 57, but it worked prior to build 53. The sequence of events are:

  • Install GF 4.0
  • Start the domain
  • Execute the following:
    o asadmin --host wolfrun --port 4848 --terse=false create-jms-resource --restype javax.jms.TopicConnectionFactory jms/res1
    o asadmin --host wolfrun --port 4848 get domain.resources.connector-connection-pool.jms/res1.*

The output results with build 53 are:
domain.resources.connector-connection-pool.jms/res1.associate-with-thread=false
domain.resources.connector-connection-pool.jms/res1.connection-creation-retry-attempts=0
domain.resources.connector-connection-pool.jms/res1.connection-creation-retry-interval-in-seconds=10
domain.resources.connector-connection-pool.jms/res1.connection-definition-name=javax.jms.TopicConnectionFactory
domain.resources.connector-connection-pool.jms/res1.connection-leak-reclaim=false
domain.resources.connector-connection-pool.jms/res1.connection-leak-timeout-in-seconds=0
domain.resources.connector-connection-pool.jms/res1.fail-all-connections=false
domain.resources.connector-connection-pool.jms/res1.idle-timeout-in-seconds=300
domain.resources.connector-connection-pool.jms/res1.is-connection-validation-required=false
domain.resources.connector-connection-pool.jms/res1.lazy-connection-association=false
domain.resources.connector-connection-pool.jms/res1.lazy-connection-enlistment=false
domain.resources.connector-connection-pool.jms/res1.match-connections=true
domain.resources.connector-connection-pool.jms/res1.max-connection-usage-count=0
domain.resources.connector-connection-pool.jms/res1.max-pool-size=250
domain.resources.connector-connection-pool.jms/res1.max-wait-time-in-millis=60000
domain.resources.connector-connection-pool.jms/res1.name=jms/res1
domain.resources.connector-connection-pool.jms/res1.object-type=user
domain.resources.connector-connection-pool.jms/res1.ping=false
domain.resources.connector-connection-pool.jms/res1.pool-resize-quantity=2
domain.resources.connector-connection-pool.jms/res1.pooling=true
domain.resources.connector-connection-pool.jms/res1.resource-adapter-name=jmsra
domain.resources.connector-connection-pool.jms/res1.steady-pool-size=1
domain.resources.connector-connection-pool.jms/res1.validate-atmost-once-period-in-seconds=0
Command get executed successfully.

The error and output seen in build 57 and in build 66 are:
remote failure: Dotted name path domain.resources.connector-connection-pool.jms/res1.* not found.
Command get failed.



 Comments   
Comment by David Zhao [ 15/Dec/12 ]

It is desired that the connection pool created by "create-jms-resource" will have "-Connection-pool" suffix appended automatically. Please see GLASSFISH-15104 for more details on why it is required for making resource name identical across domain.

Now you can get the properties by the the CLI command (-Connection-Pool suffix is required for the name of connection pool):

asadmin --host wolfrun --port 4848 get domain.resources.connector-connection-pool.jms/res1-Connection-Pool.*





Generated at Sun Jul 05 01:22:02 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.