Hi 
     Am new to this messaging, recetly i have upgraded to Jboss messaging.
I read somedid necessary changes in config files and ... when deploying it 
complains abt the jndi is null. can any one tell me wher am going wrong..


My *-service.xml file is

<server>
  | 
  | <!--
  |             code="org.jboss.mq.server.jmx.Topic" 
  | 
  |     <mbean
  |             code="org.jboss.mq.server.jmx.Topic" 
  |             name="com.barco.event:service=Topic,name=events"> 
  |             <attribute name="JNDIName">topic/events</attribute>
  |             <attribute name="InMemory">true</attribute>
  |             <depends optional-attribute-name="DestinationManager">
  |                     jboss.mq:service=DestinationManager
  |             </depends>
  |             <depends optional-attribute-name="SecurityManager">
  |                     jboss.mq:service=SecurityManager
  |             </depends>
  |     </mbean> -->
  |     
  |             <mbean code="org.jboss.jms.server.destination.TopicService"     
name="com.barco.event:service=Topic,name=events" 
xmbean-dd="xmdesc/Topic-xmbean.xml"> 
  |         
  |             <depends 
optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
  |             <depends>jboss.messaging:service=PostOffice</depends>
  |               <!--  <attribute name="SecurityConfig">
  |            <security>
  |             <role name="guest" read="true" write="true"/>
  |             <role name="publisher" read="true" write="true" create="false"/>
  |             <role name="durpublisher" read="true" write="true" 
create="true"/>
  |          </security>
  |       </attribute> -->
  |               
  |             </mbean>
  | </server>

MDB code goes like this..

@MessageDriven(activationConfig = {...@activationconfigproperty(propertyName = 
"destinationType", propertyValue = "javax.jms.Topic"),
  |         @ActivationConfigProperty(propertyName = "destination", 
propertyValue = "topic/events")})
  | @Depends({"com.barco.event.emitters:service=BarcoBroadcastService", 
"jboss:service=Naming"})
  | public class BarcoBroadcastMDB
  |     implements MessageListener
  | {
  |     
  |     private static Logger mLogger = 
Logger.getLogger(BarcoBroadcastMDB.class);
  |     
  |     @Depends({"com.barco.event.emitters:service=BarcoBroadcastService"})
  |     static BarcoBroadcastServiceMBean mBroadcastService;



Jboss Console  shows..

11:47:54,179 INFO  [JBossASKernel] Added 
bean(jboss.j2ee:jar=PerspectiveManagement.jar,name=PerspectiveMgtAPIImpl,service=EJB3)
 to KernelDeployment of: PerspectiveManagement.jar
  | 11:47:54,179 INFO  [JBossASKernel] installing bean: 
jboss.j2ee:jar=PerspectiveManagement.jar,name=BarcoBroadcastMDB,service=EJB3
  | 11:47:54,179 INFO  [JBossASKernel]   with dependencies:
  | 11:47:54,179 INFO  [JBossASKernel]   and demands:
  | 11:47:54,179 INFO  [JBossASKernel]      jboss.ejb:service=EJBTimerService
  | 11:47:54,179 INFO  [JBossASKernel]   and supplies:
  | 11:47:54,179 INFO  [JBossASKernel]      jndi:null
  | 11:47:54,179 INFO  [JBossASKernel]      Class:javax.jms.MessageListener
  | 11:47:54,179 INFO  [JBossASKernel] Added 
bean(jboss.j2ee:jar=PerspectiveManagement.jar,name=BarcoBroadcastMDB,service=EJB3)
 to KernelDeployment of: PerspectiveManagement.jar


Often this exception floats....



  | 11:47:59,633 WARN  [JmsActivation] Failure in jms activation 
org.jboss.resource.adapter.jms.inflow.jmsactivations...@874c04(ra=org.jboss.resource.adapter.jms.jmsresourceadap...@68d0ca
 destination=topic/events destinationType=javax.jms.Topic tx=true durable=false 
reconnect=10 provider=java:/DefaultJMSProvider user=null maxMessages=1 
minSession=1 maxSession=15 keepAlive=60000 useDLQ=true 
DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler 
DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=5)
  | javax.naming.NameNotFoundException: events not bound
  |         at org.jnp.server.NamingServer.getBinding(NamingServer.java:771)
  |         at org.jnp.server.NamingServer.getBinding(NamingServer.java:779)
  |         at org.jnp.server.NamingServer.getObject(NamingServer.java:785)
  |         at org.jnp.server.NamingServer.lookup(NamingServer.java:443)
  |         at org.jnp.server.NamingServer.lookup(NamingServer.java:399)
  |         at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:722)
  |         at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:682)
  |         at javax.naming.InitialContext.lookup(InitialContext.java:392)
  |         at org.jboss.util.naming.Util.lookup(Util.java:222)
  |         at 
org.jboss.resource.adapter.jms.inflow.JmsActivation.setupDestination(JmsActivation.java:464)
  |         at 
org.jboss.resource.adapter.jms.inflow.JmsActivation.setup(JmsActivation.java:352)
  |         at 
org.jboss.resource.adapter.jms.inflow.JmsActivation$SetupActivation.run(JmsActivation.java:729)
  |         at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:213)
  |         at 
org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:260)
  |         at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
  |         at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
  |         at java.lang.Thread.run(Thread.java:619)
  | 11:47:59,711 WARN  [Ejb3Configuration] Persistence provider caller does not 
implement the EJB3 spec correctly. PersistenceUnitInfo.getNewTempClassLoader() 
is null.
  | 11:47:59,993 INFO  [AnnotationConfiguration] Mapping package 
com.barco.cms.openapi.sessionmgt
  | 11:48:00,852 INFO  [AnnotationConfiguration] Mapping package 
com.barco.cms.openapi.exception


am not able to get any info on this..
please help me in solving this.

Thanks In Advance
Subramanyam

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

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214074
_______________________________________________
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user

Reply via email to