Trying out XA, part 6: jndi.properties rabbit trail

In part 5, we were thinking the problem might be having the wrong class specified in the resource adapter configuration file.

So, based on the ActiveMQ JNDI Support page, looks like we need to put a jndi.properties file with our project…

Tried that and my new queue connection factory doesn’t show up in JNDIView in the JBoss JMX console.  Hmm.  Moved jndi.properties into the same package as my java classes to see if JBoss would see it there… same result.

Hey, jndi.properties exists in JBoss’s conf directory (in my case, server/default/conf/jndi.properties).  How ’bout I first try adding the settings there and bouncing JBoss, and see if the entries show up in the JMX console.  Then I can do it a better way once it’s working, huh?

I’m adding these settings to jndi.properties:

java.naming.provider.url = tcp://localhost:61616

connectionFactoryNames = DapperQueueConnectionFactory

queue.DapperQueue = XATry.DapperQueue

JBoss doesn’t seem to immediately notice the change (no output on the console anyway) so let’s bounce JBoss…

Boom!

javax.naming.CommunicationException: Could not obtain connection to any of these urls: tcp://localhost:61616 and discovery failed with error: javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out] [Root exception is javax.naming.CommunicationException: Failed to connect to server tcp:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server tcp:1099 [Root exception is java.net.UnknownHostException: tcp: tcp]]]

Maybe I should have ActiveMQ running at the time I start JBoss…

Hmm, same error even with ActiveMQ running.

You know, at the top of JBoss’s jndi.properties file there is this comment:

# DO NOT EDIT THIS FILE UNLESS YOU KNOW WHAT YOU ARE DOING

I guess they were right!  :)

I removed the things I had added to the jndi.properties file, and JBoss starts clean again.

Properties in the Spring beans?

I seem to remember <properties> entries you can put within your Spring bean definitions.  Perhaps I should put the settings there instead of in jndi.properties.  Let’s see…ah yes, it was in the Spring manual Appendix A, the part about the jee:jndi-lookup tag.

So instead of

<jee:jndi-lookup id="connectionFactory" jndi-name="java:activemq/ConnectionFactory" />

let’s try this:

<jee:jndi-lookup id="connectionFactory" jndi-name="DapperQueueConnectionFactory">
    <jee:environment>
        java.naming.provider.url=tcp://localhost:61616
        connectionFactoryNames=DapperQueueConnectionFactory
        queue.DapperQueue=XATry.DapperQueue
    </jee:environment>
</jee:jndi-lookup>

Deploying this blows up because again I don’t have ActiveMQ running at port 61616.  Let’s start up ActiveMQ and try again…

Hmm, no new messages in the console, but I think I read somewhere that ActiveMQ doesn’t read the jndi.properties file until the queue (or whatever) is actually going to be used.  So let’s try enabling the DefaultMessageListenerContainer, pointing to the beans which have been revised this way:

    <bean id="messageListener" class="com.example.service.QueueConsumer" />

    <bean id="transactionManager" class="org.springframework.transaction.jta.JtaTransactionManager" />

    <jee:jndi-lookup id="connectionFactory" jndi-name="DapperQueueConnectionFactory">
        <jee:environment>
            java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory
            java.naming.provider.url=tcp://localhost:61616
            connectionFactoryNames=DapperQueueConnectionFactory
            queue.DapperQueue=XATry.DapperQueue
        </jee:environment>
    </jee:jndi-lookup>

    <jee:jndi-lookup id="dapperQueue" jndi-name="DapperQueue">
        <jee:environment>
            java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory
            java.naming.provider.url=tcp://localhost:61616
            connectionFactoryNames=DapperQueueConnectionFactory
            queue.DapperQueue=XATry.DapperQueue
        </jee:environment>
    </jee:jndi-lookup>

    <bean id="jmsContainer" class="org.springframework.jms.listener.DefaultMessageListenerContainer">
        <property name="messageListener" ref="messageListener" />
        <property name="transactionManager" ref="transactionManager" />
        <property name="connectionFactory" ref="connectionFactory" />
        <property name="destination" ref="dapperQueue" />
    </bean>

Result:

13:59:51,947 ERROR [ContextLoader] Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘connectionFactory’: Invocation of init method failed; nested exception is javax.naming.NamingException: Invalid broker URL

Guess we still don’t have it!

Update: See the Something Works! post for the stunning near-conclusion of the example…

About these ads