Hi all
I am using glassfish v3.0.1 b 14.
I have two Topics that are defined as follows im my domain.xml
<connector-resource pool-name="jms/IncomingMessageFactory" jndi-name="jms/IncomingMessageFactory" />
<connector-connection-pool name="jms/IncomingMessageFactory" resource-adapter-name="jmsra" connection-definition-name="javax.jms.TopicConnectionFactory" idle-timeout-in-seconds="600" />
<connector-resource pool-name="jms/OutgoingMessageFactory" jndi-name="jms/OutgoingMessageFactory" />
<connector-connection-pool name="jms/OutgoingMessageFactory" resource-adapter-name="jmsra" connection-definition-name="javax.jms.TopicConnectionFactory" idle-timeout-in-seconds="600" />
</resources>
<servers>
<server name="server" config-ref="server-config">
<resource-ref ref="jms/IncomingMessageTopic" />
<resource-ref ref="jms/OutgoingMessageTopic" />
<resource-ref ref="jms/IncomingMessageFactory" />
<resource-ref ref="jms/OutgoingMessageFactory" />
</server>
</servers>
It seems that the server can't find jms/OutgoingMessageTopic even though it is able to find jms/OutgoingMessageTopic and they have an identical declaration. I have tried
@Resource(name = "jms/OutgoingMessageTopic")
and
Destination destination = (Destination) c.lookup("java:comp/env/jms/OutgoingMessageTopic");
and both fail
I get the following with asadmin:
/opt/glassfishv301b14/bin/asadmin list-jndi-entries --context jms
OutgoingMessageFactory: javax.naming.Reference
IncomingMessageTopic: javax.naming.Reference
IncomingMessageFactory: javax.naming.Reference
OutgoingMessageTopic: org.glassfish.javaee.services.ResourceProxy
Command list-jndi-entries executed successfully.
I have no idea why OutgoingMessageTopic is seen as a org.glassfish.javaee.services.ResourceProxy
instead of javax.naming.Reference like the rest.
Any ideas?
[Message sent by forum member 'waynetg']
http://forums.java.net/jive/thread.jspa?messageID=398513