I'm having a problem that on the surface looks to be very simple but that has had me stumped for a couple days.
I'm trying to deploy a JMS Connection factory and Queue on the server with the following jndi names on Wildfly 8.1.0 :
java:jboss/exported/jms/UnicsRetry for the connection factory and java:jboss/exported/queue/Create for the queue.
This is my configuration xml bit for these two components, and from what I've been able to gather from the documentation, it looks correct:
Wildfly itself accepts these and starts up without a hitch, however when I try to access the connection factory via JNDI (with this provider url: http-remoting://localhost:8080 using the jbss naming remote client context factory) I always get a name not found exception. I went and printed out the jndi bindings for both java:global and java:jboss like so:
And I on both cases I get this output
jboss/exported/jms/UnicsRetry -- service jboss.naming.context.java.jboss.exported.jboss.exported.jms.UnicsRetry
It looks like the connection factory is actually up and bound, so why is it that the lookup fails? Needless to say, I haven´t been able to try out the queue itself or the MDB I actually want to test. I thought it may have been that I had to remove the java: part of the jndi when doing the lookup like the listing showed, but it didn't work either.
If it has anything to do with my problem, I had to put up these dependencies in my pom.xml to build my testing client:
Any help any kind reader could provide would be greatly appreciated, this has me pulling my hair out.