[jboss-user] [JBoss Messaging] - Re: Persistence Manager Problem - null-persistence-service.x
I'll let you guys know if there are and adverse effects. The suggested modifications certainly worked in getting around problems during start-up. However, now that I'm using the null-persistence-manager, I see the following errors when deploying MDBs (ejb3) ... (I get this dump for each MDB I have). 10:25:41,120 ERROR [ExceptionUtil] ConnectionFactoryEndpoint[jboss.messaging.connectionfactory:service=ConnectionFactory] createFailoverConnectionDelegate [7b-w0i3pmuf-1-lvt1pmuf-mxc4dw-c2aba] javax.jms.JMSSecurityException: User null is NOT authenticated at org.jboss.jms.server.jbosssx.JBossASSecurityMetadataStore.authenticate(JBossASSecurityMetadataStore.java:223) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:93) at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:27) at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:208) at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:120) at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:262) at javax.management.StandardMBean.invoke(StandardMBean.java:391) at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy89.authenticate(Unknown Source) at org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint.createConnectionDelegateInternal(ServerConnectionFactoryEndpoint.java:233) at org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint.createConnectionDelegate(ServerConnectionFactoryEndpoint.java:171) at org.jboss.jms.server.endpoint.advised.ConnectionFactoryAdvised.org$jboss$jms$server$endpoint$advised$ConnectionFactoryAdvised$createConnectionDelegate$aop(ConnectionFactoryAdvised.java:108) at org.jboss.jms.server.endpoint.advised.ConnectionFactoryAdvised.createConnectionDelegate(ConnectionFactoryAdvised.java) at org.jboss.jms.wireformat.ConnectionFactoryCreateConnectionDelegateRequest.serverInvoke(ConnectionFactoryCreateConnectionDelegateRequest.java:91) at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:143) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:908) at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106) at org.jboss.remoting.Client.invoke(Client.java:1708) at org.jboss.remoting.Client.invoke(Client.java:612) at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.org$jboss$jms$client$delegate$ClientConnectionFactoryDelegate$createConnectionDelegate$aop(ClientConnectionFactoryDelegate.java:171) at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeTarget(ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111) at org.jboss.jms.client.container.StateCreationAspect.handleCreateConnectionDelegate(StateCreationAspect.java:81) at org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect_z_handleCreateConnectionDelegate_9491698.invoke(StateCreationAspect_z_handleCreateConnectionDelegate_9491698.java) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.createConnectionDelegate(ClientConnectionFactoryDelegate.java) at org.jboss.jms.client.JBossConnectionFactory.createConnectionInternal(JBossConnectionFactory.java:205) at org.jboss.jms.client.JBossConnectionFactory.createQueueConnection(JBossConnectionFactory.java:101) at org.jboss.jms.client.JBossConnectionFactory.createQueueConnection(JBossConnectionFactory.java:95) at org.jboss.resource.adapter.jms.inflow.dlq.AbstractDLQHandler.setupDLQConnection(AbstractDLQHandler.java:137) at org.jboss.resource.adapter.jms.inflow.dlq.AbstractDLQHandler.setup(AbstractDLQHandler.java:83) at org.jboss.resource.adapter.jms.inflow.dlq.JBossMQDLQHandler.setup(JBossMQDLQHandler.java:48) at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupDLQ(JmsActivation.java:413) at org.jboss.resource.adapter.jms.inflow.JmsActivation.setup(JmsActivation.java:351) at
[jboss-user] [JBoss Messaging] - Re: Persistence Manager Problem - null-persistence-service.x
I've managed to come up with a resolution, for now. If I copy the portion of the hsqldb-persistence-service.xml file related to the JMS User Manager MBean config into the null-persistence-service.xml, the problem is resolved. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4230538#4230538 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4230538 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Persistence Manager Problem - null-persistence-service.x
It looks like the dependency is missing. try adding depends optional-attribute-name=TransactionManagerjboss:service=TransactionManager/depends View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4207251#4207251 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4207251 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Persistence Manager Problem - null-persistence-service.x
Thanks for the tip. That seemed to fix it.
I added that line to the PostOffice and the JMSUserManager. I also had to
comment out a few things: ChannelFactoryName and GroupName
I'll let you guys know if there are and adverse effects.
| ?xml version=1.0 encoding=UTF-8?
|
| !--
| Null persistence config.
|
| Use this if you don't actually want to persist anything
|
| $Id$
| --
|
| server
|
|!-- Persistence Manager MBean configuration
| --
|
|mbean code=org.jboss.messaging.core.jmx.NullPersistenceManagerService
| name=jboss.messaging:service=PersistenceManager
| xmbean-dd=xmdesc/NullPersistenceManager-xmbean.xml
| !--
| depends
optional-attribute-name=TransactionManagerjboss:service=TransactionManager/depends
| --
|/mbean
|
|!-- Messaging Post Office MBean configuration
| = --
|
|mbean code=org.jboss.messaging.core.jmx.MessagingPostOfficeService
| name=jboss.messaging:service=PostOffice
| xmbean-dd=xmdesc/MessagingPostOffice-xmbean.xml
|
| depends
optional-attribute-name=ServerPeerjboss.messaging:service=ServerPeer/depends
| depends
optional-attribute-name=TransactionManagerjboss:service=TransactionManager/depends
| !-- The name of the post office --
|
| attribute name=PostOfficeNameJMS post office/attribute
|
| !-- This post office is clustered. If you don't want a clustered
post office then set to false --
|
| attribute name=Clusteredfalse/attribute
|
| !-- All the remaining properties only have to be specified if the
post office is clustered.
|You can safely comment them out if your post office is non
clustered --
|
| !-- The JGroups group name that the post office will use --
| !--
| attribute
name=GroupName${jboss.messaging.groupname:MessagingPostOffice}/attribute
| --
| !-- Max time to wait for state to arrive when the post office joins
the cluster --
|
| attribute name=StateTimeout3/attribute
|
| !-- Max time to wait for a synchronous call to node members using
the MessageDispatcher --
|
| attribute name=CastTimeout3/attribute
|
| !-- Set this to true if you want failover of connections to occur
when a node is shut down --
|
| attribute name=FailoverOnNodeLeavefalse/attribute
| !--
| depends
optional-attribute-name=ChannelFactoryNamejboss.jgroups:service=ChannelFactory/depends
| attribute name=ControlChannelNamejbm-control/attribute
| attribute name=DataChannelNamejbm-data/attribute
| attribute
name=ChannelPartitionName${jboss.partition.name:DefaultPartition}-JMS/attribute
| --
|/mbean
|
|!-- Messaging JMS User Manager MBean config
| === --
|
|mbean code=org.jboss.jms.server.plugin.JDBCJMSUserManagerService
| name=jboss.messaging:service=JMSUserManager
| xmbean-dd=xmdesc/JMSUserManager-xmbean.xml
| depends
optional-attribute-name=TransactionManagerjboss:service=TransactionManager/depends
|/mbean
|
| /server
|
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4207516#4207516
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4207516
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Persistence Manager Problem - null-persistence-service.x
droberts18 wrote : | I also had to comment out a few things: ChannelFactoryName and GroupName https://jira.jboss.org/jira/browse/JBMESSAGING-1471 View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4207526#4207526 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4207526 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
