This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Unable to create Queue Destination using New JMS Resource Wizard... updates sun-resources.xml file, but does not create 'Destination Resource' on deploy. unable to create Queue Destination using New JMS Resource Wizard... (Looking at the "Queue Destinations" selection under GlassFish V2 in the Services window. looking at the sun-resources.xml file, both connector-resource and connector-connection-pool are given the same jndi-name="jms/simpleQueue" name. Is this correct? Thanks Leonid <connector-resource enabled="true" jndi-name="jms/simpleQueue" object-type="user" pool-name="jms/simpleQueue"/> <connector-connection-pool associate-with-thread="false" connection-creation-retry-attempts="0" connection-creation-retry-interval-in-seconds="10" connection-definition-name="javax.jms.QueueConnectionFactory" 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="32" max-wait-time-in-millis="60000" name="jms/simpleQueue" pool-resize-quantity="2" resource-adapter-name="jmsra" steady-pool-size="8" validate-atmost-once-period-in-seconds="0"/>
the duplicate names do look suspect.
JMS resource of types javax.jms.QueueConnectionFactory, javax.jms.QueueConnectionFactory and javax.jms.ConnectionFactory map to a Connection Factory resource (under under 'JMS Resources-->Connection Factories') and a Connector Resource (see under 'Connectors-->Connector Resources'). The associated pool is a Connector Connection Pool displayed under 'Connectors-->Connector Connection Pools'. The Connector Connection Pool is not part of the JMS Resources listing. The naming of the connection pool defaults to the name of the associated JMS resource. This conforms to the way the admin console behaves while creating JMS Resources. JMS resource of type javax.jms.Queue and javax.jms.Topic map to 'JMS Resources-->Destination Resources' and 'Connectors-->Admin Object Resources' The JMS Resource Wizard does call out the Connector types that the resources resolve to. Closing the issue as Invalid. Please provide comments if we can make the wizard more descriptive.
Sorry, I don't understand anything that you are saying. I ran the wizard, and came up with these results. Are you saying the results are correct? Or am I using the wizard wrong? Thanks Leonid