Issue Type: Bug Bug
Affects Versions: 4.1.0.Final
Assignee: Unassigned
Components: integration
Created: 30/Aug/12 4:49 AM
Description:

JMS messaging is secured by default at jboss-as-7.1.1. So I configured SessionFactory with following props:

<prop key="hibernate.search.default.worker.jndi.java.naming.factory.initial">org.jboss.naming.remote.client.InitialContextFactory</prop>
<prop key="hibernate.search.default.worker.jndi.java.naming.provider.url">remote://master_host:4447</prop>
<prop key="hibernate.search.default.worker.jndi.java.naming.security.principal">guest</prop>
<prop key="hibernate.search.default.worker.jndi.java.naming.security.credentials">123123123</prop>

While jboss start everything went well – connection factory and queue were successfully found, but when I forced index change to check if replication was working I got following :

Failed to create session : HornetQException[errorCode=105 message=Unable to validate user: null]

After digging into some code I found that "JMSBackendQueueTask" class creates a "QueueConnection" without passing username/password to it :

cnn = processor.getJMSFactory().createQueueConnection();

So is there a way to pass there security credentials, if they were configured for that index worker?

So far I disabled JMS security at my standalone-full-ha.xml (added <security-enabled>false</security-enabled> to "messaging" subsystem), what is not good.

Environment: jboss-as-7.1.1.Final
Project: Hibernate Search
Labels: jms
Priority: Major Major
Reporter: Anton Nazaruk
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira