Howdy All
Im trying to deploy an MDB to a JBoss 3.0 instance and am getting the
following Security issue. I think I have everything wide open on the
Queue and the exception seems to indicate that its something with the
creation of the DLQ.
Ive tried various roles in the method permissions for the MDB but
honestly I dont think I should even need that by default.
As I understand it the DLQHander gets created on the MDB deployment. Is
this an issue in configuration (DLQ does not seem to have an explicit
deployment section)
Any help would be appreciated
Thanks
-=Brian
------------ Exception im getting
11:59:27,988 INFO [EjbModule] Deploying DomainEventListner
11:59:28,498 WARN [JMSContainerInvoker] JMS provider failure detected:
javax.jms.JMSSecurityException: User: null is NOT authenticated
at
org.jboss.mq.security.SecurityManager.authenticate(SecurityManager.java:181)
at
org.jboss.mq.security.ServerSecurityInterceptor.authenticate(ServerSecurityInterceptor.java:40)
at
org.jboss.mq.server.TracingInterceptor.authenticate(TracingInterceptor.java:575)
at
org.jboss.mq.server.JMSServerInvoker.authenticate(JMSServerInvoker.java:288)
at org.jboss.mq.il.jvm.JVMServerIL.authenticate(JVMServerIL.java:302)
at org.jboss.mq.Connection.authenticate(Connection.java:759)
at org.jboss.mq.Connection.<init>(Connection.java:233)
at org.jboss.mq.Connection.<init>(Connection.java:264)
at org.jboss.mq.SpyConnection.<init>(SpyConnection.java:59)
at
org.jboss.mq.SpyConnectionFactory.createQueueConnection(SpyConnectionFactory.java:96)
at org.jboss.ejb.plugins.jms.DLQHandler.create(DLQHandler.java:131)
( rest of big huge honking exception goes here )
------------My Beans ejb-jar.xml is defined as
<message-driven >
<description><![CDATA[Message processor for the
domainRegistration requests.]]></description>
<ejb-name>DomainEventListner</ejb-name>
<ejb-class>com.flytechnology.server.ejb.listeners.domain.DomainEventListner</ejb-class>
<transaction-type>Container</transaction-type>
<acknowledge-mode>Auto-acknowledge</acknowledge-mode>
<message-driven-destination>
<destination-type>javax.jms.Queue</destination-type>
<subscription-durability>NonDurable</subscription-durability>
</message-driven-destination>
</message-driven>
-----------and i have even added a permissions role to ejb-jar.xml
<method-permission >
<description>description not supported yet by
ejbdoclet</description>
<role-name>subscriber</role-name>
<method >
<description>description not supported yet by
ejbdoclet</description>
<ejb-name>DomainEventListner</ejb-name>
<method-name>*</method-name>
</method>
</method-permission>
----------- my jboss.xml entry looks like
<message-driven>
<ejb-name>DomainEventListner</ejb-name>
<destination-jndi-name>
queue/DomainEventQueue
</destination-jndi-name>
</message-driven>
-----------The Queue is defined in the jbossmq-destinations.xml file as
<mbean code="org.jboss.mq.server.jmx.Queue"
name="jboss.mq.destination:service=Queue,name=DomainEventQueue">
<depends
optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
<depends
optional-attribute-name="SecurityManager">jboss.mq:service=SecurityManager</depends>
<attribute name="SecurityConf">
<security>
<role name="guest" read="true" write="true"/>
<role name="publisher" read="true" write="true" create="false"/>
<role name="subscriber" read="true" write="true"
create="false"/>
<role name="noacc" read="true" write="true" create="false"/>
</security>
</attribute>
</mbean>
--------- The jbossmq-state.xml is default that comes with the
distribution
-------------------------------------------------------
This sf.net email is sponsored by: Jabber - The world's fastest growing
real-time communications platform! Don't just IM. Build it in!
http://www.jabber.com/osdn/xim
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
