JBoss AS 6.0 Final - Unable to validate user: null for check type

[notify]

I am moving a live JBoss SEAM Application from Jboss 4.2.3 to JBoss AS 6.0 on Windows 7. I used plain vanilla JMS in JBoss 4.2.3.

I have created a queue in the hornet-jms.xml

<queue name="NOTiFYPiNPOiNTMessagesQueue">

<entry name="/queue/NOTiFYPiNPOiNTMessagesQueue"/>

</queue>

When I start Jboss AS 6.0 I get an error: "Unable to validate user: null for check type CONSUME";

20:35:57,813 INFO [HornetQActivation] Attempting to reconnect org.hornetq.ra.inflow.HornetQActivationSpec(ra=org.hornetq.ra.HornetQ

ResourceAdapter@114ea11 destination=queue/NOTiFYPiNPOiNTMessagesQueue destinationType=javax.jms.Queue ack=Auto-acknowledge durable=f

alse clientID=null user=null maxSession=15)

20:35:57,819 ERROR [HornetQActivation] Unable to reconnect org.hornetq.ra.inflow.HornetQActivationSpec(ra=org.hornetq.ra.HornetQReso

urceAdapter@114ea11 destination=queue/NOTiFYPiNPOiNTMessagesQueue destinationType=javax.jms.Queue ack=Auto-acknowledge durable=false

clientID=null user=null maxSession=15): HornetQException[errorCode=105 message=Unable to validate user: null for check type CONSUME

for address jms.queue.NOTiFYPiNPOiNTMessagesQueue]

at org.hornetq.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:287) [:6.0.0.Final]

at org.hornetq.core.client.impl.ClientSessionImpl.internalCreateConsumer(ClientSessionImpl.java:1556) [:6.0.0.Final]

at org.hornetq.core.client.impl.ClientSessionImpl.createConsumer(ClientSessionImpl.java:447) [:6.0.0.Final]

at org.hornetq.core.client.impl.ClientSessionImpl.createConsumer(ClientSessionImpl.java:392) [:6.0.0.Final]

at org.hornetq.core.client.impl.DelegatingSession.createConsumer(DelegatingSession.java:201) [:6.0.0.Final]

at org.hornetq.ra.inflow.HornetQMessageHandler.setup(HornetQMessageHandler.java:165) [:6.0.0.Final]

at org.hornetq.ra.inflow.HornetQActivation.setup(HornetQActivation.java:291) [:6.0.0.Final]

at org.hornetq.ra.inflow.HornetQActivation.handleFailure(HornetQActivation.java:539) [:6.0.0.Final]

at org.hornetq.ra.inflow.HornetQActivation$SetupActivation.run(HornetQActivation.java:577) [:6.0.0.Final]

at org.jboss.resource.work.WorkWrapper.run(WorkWrapper.java:172) [:6.0.0.Final]

at org.jboss.threads.SimpleDirectExecutor.execute(SimpleDirectExecutor.java:33) [:2.0.0.CR7]

at org.jboss.threads.QueueExecutor.runTask(QueueExecutor.java:801) [:2.0.0.CR7]

at org.jboss.threads.QueueExecutor.access$100(QueueExecutor.java:45) [:2.0.0.CR7]

at org.jboss.threads.QueueExecutor$Worker.run(QueueExecutor.java:821) [:2.0.0.CR7]

at java.lang.Thread.run(Unknown Source) [:1.6.0_20]

at org.jboss.threads.JBossThread.run(JBossThread.java:122) [:2.0.0.CR7]

I have Googled this error but no definite answer. Any futher suggestions?

[notify]

Found a solution;

Added;

<security-enabled>false</security-enabled

to my HornetQ configuration file.

[ziggy25]

How is HornetQ disabled on the Jboss.7.1.0 with the embedded HornetQ provider?

[jbertram]

Simply remove the <subsystem xmlns="urn:jboss:domain:messaging:1.1"> tag and all its contents from the server configuration file.  It wouldn't hurt to remove <extension module="org.jboss.as.messaging"/> and <socket-binding name="messaging" port="5445"/> and <socket-binding name="messaging-throughput" port="5455"/> as well.

[jbertram]

One more thing...Try not to comment on old threads that have been resolved.  Since your question isn't directly related to this thread anyway it would have been better to create a new thread for it.

[ziggy25]

Actually i just re-read the question and i think i asked the wrong question

I actually wanted to ask how is the HornetQ security disabled when it is used as the JMS provider with Jboss (Not how to disable HornetQ completely). The answer that was originally provided was related to the hornetQ configuration file for the standalone HorneQ version, i was curious about how to achieve the same for the built-in version within Jboss.

[jbertram]

The method of disabling security for HornetQ within JBoss AS 7.1.0.Final is essentially the same as for standalone HornetQ or HornetQ with a different version of JBoss AS.  You use this tag just as previously specified:

  <security-enabled>false</security-enabled>

However, for AS 7.1.0.Final instead of putting this into hornetq-configuration.xml you will put this in the <hornetq> section of the messaging subsystem in standalone*.xml.

[ziggy25]

I did try that but it didnt quite work. I am not sure if it is the HornetQ authorisation that doesnt work or the Jboss authorisation/authentication that doesnt work. See this link https://community.jboss.org/message/721400#721400