I am trying to go with approach (4) - put my MDB in deploy-hasingleton, but it 
doesnot seem to work. (Note- when I put my MDBs in deploy or farm folder, it 
works just fine).

Here is the exception I get on startup:

15:13:46,546 WARN  [EjbModule] Could not load the org.jboss.resource.connectionm
anager.CachedConnectionInterceptor interceptor for this container
javax.management.InstanceNotFoundException: 
jboss.jca:service=CachedConnectionManager is not registered....
...
MBeans waiting for other MBeans:
ObjectName: jboss.j2ee:binding=message-driven-bean,jndiName=local/DefaultProvide
rMDB,plugin=invoker,service=EJB
 state: FAILED
 I Depend On:
 Depends On Me: javax.naming.NameNotFoundException: DefaultJMSProvider not bound


MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM:
ObjectName: jboss.j2ee:binding=message-driven-bean,jndiName=local/DefaultProvide
rMDB,plugin=invoker,service=EJB
 state: FAILED
 I Depend On:
 Depends On Me: javax.naming.NameNotFoundException: DefaultJMSProvider not bound


I am running in 'all' mode and  have ensured that jmsjca-service.xml is in the 
deploy folder. Also, since I am using SonicMQ, and not JBossMQ, I have removed 
JBossMQ related configurations.

My sonic-service.xml looks something like this:

  | <?xml version="1.0" encoding="UTF-8"?>
  | <server>
  |     <mbean code="com.integral.jmsx.jndi.jboss.JBossLoader" 
name="sonic.mq:service=JNDILoader">
  |         <attribute 
name="JNDIInitClassName">com.integral.jmsx.jndi.JmsJndiInit</attribute>
  |         <depends>jboss:service=Naming</depends>
  |     </mbean>
  |     
  | 
  |   <!-- The JMS provider loader -->
  |   <mbean code="org.jboss.jms.jndi.JMSProviderLoader"
  |      name="jboss.mq:service=JMSProviderLoader,name=JBossMQProvider">
  |     <attribute name="ProviderName">DefaultJMSProvider</attribute>
  |     <attribute name="ProviderAdapterClass">
  |     org.jboss.jms.jndi.JNDIProviderAdapter
  |     </attribute>
  |     <attribute 
name="QueueFactoryRef">java:/QueueConnectionFactory</attribute>
  |     <attribute 
name="TopicFactoryRef">java:/TopicConnectionFactory</attribute>
  |   </mbean>
  | 
  |   <!-- org.jboss.jms.jndi.JNDIProviderAdapter -->
  |   <!-- The server session pool for Message Driven Beans -->
  |   <mbean code="org.jboss.jms.asf.ServerSessionPoolLoader"
  |      name="jboss.mq:service=ServerSessionPoolMBean,name=StdJMSPool">
  |     <depends 
optional-attribute-name="XidFactory">jboss:service=XidFactory</depends>
  |     <attribute name="PoolName">StdJMSPool</attribute>
  |     <attribute name="PoolFactoryClass">
  |       org.jboss.jms.asf.StdServerSessionPoolFactory
  |     </attribute>
  |   </mbean>
  | 
  |   <!-- JMS XA Resource adapter, use this to get transacted JMS in beans -->
  |   <tx-connection-factory>
  |     <jndi-name>JmsXA</jndi-name>
  |     <xa-transaction/>
  |     <rar-name>jms-ra.rar</rar-name>
  |     
<connection-definition>org.jboss.resource.adapter.jms.JmsConnectionFactory</connection-definition>
  |     <config-property name="SessionDefaultType" 
type="java.lang.String">javax.jms.Topic</config-property>
  |     <config-property name="JmsProviderAdapterJNDI" 
type="java.lang.String">java:/DefaultJMSProvider</config-property>
  |     <max-pool-size>20</max-pool-size>
  |     
<security-domain-and-application>JmsXARealm</security-domain-and-application>
  |   </tx-connection-factory>     
  | </server>
  | 


-Thanks.
-Inder.

View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3868729#3868729

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3868729


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to