"jj_ht" wrote : Since the server.log is pretty big, I preprocessed it and give 
the difference I noticed for  the started RA instance and un-started RA 
instance. It seems definitely not working for you, sorry about that.
  | 
  | Since there is not enough space I can post the whole server log here, here 
is the logging related to the started RA instance:
  | 
  | 2005-02-10 09:24:47,515 DEBUG 
[org.jboss.ejb.plugins.inflow.JBossMessageEndpointFactory] Starting 
jboss.j2ee:binding=message-inflow-driven-bean,jndiName=local/FileMessageListenerMDB1,plugin=invoker,service=EJB
  | \2005-02-10 09:24:47,566 DEBUG 
[org.jboss.ejb.plugins.inflow.JBossMessageEndpointFactory] Started 
jboss.j2ee:binding=message-inflow-driven-bean,jndiName=local/FileMessageListenerMDB1,plugin=invoker,service=EJB
  | 2005-02-10 09:24:47,566 DEBUG [org.jboss.system.ServiceController] Starting 
dependent components for: 
jboss.j2ee:binding=message-inflow-driven-bean,jndiName=local/FileMessageListenerMDB1,plugin=invoker,service=EJB
 dependent components: []
  | 2005-02-10 09:24:47,566 DEBUG [org.jboss.ejb.MessageDrivenContainer] 
Started jboss.j2ee:jndiName=local/FileMessageListenerMDB1,service=EJB
  | 2005-02-10 09:24:47,566 DEBUG [org.jboss.system.ServiceController] Starting 
dependent components for: 
jboss.j2ee:jndiName=local/FileMessageListenerMDB1,service=EJB dependent 
components: []
  | 2005-02-10 09:24:47,566 DEBUG [org.jboss.ejb.EjbModule] Started 
jboss.j2ee:module=FileConnectorWSHF_MDB1.jar,service=EjbModule
  | 2005-02-10 09:24:47,566 DEBUG [org.jboss.system.ServiceController] Starting 
dependent components for: 
jboss.j2ee:module=FileConnectorWSHF_MDB1.jar,service=EjbModule dependent 
components: []
  | 2005-02-10 09:24:47,566 INFO  [org.jboss.ejb.EJBDeployer] Deployed: 
file:/D:/jboss-4.0.0/server/default/tmp/deploy/tmp48141FileConnector.ear-contents/FileConnectorWSHF_MDB1.jar
  | 2005-02-10 09:24:47,696 DEBUG [org.jboss.deployment.MainDeployer] End 
deployment start on package: FileConnectorWSHF_MDB1.jar
  | 
  | 
  | And here is the logging related to the un-started RA instance:
  | 
  | 2005-02-10 09:24:47,706 DEBUG [org.jboss.system.ServiceController] starting 
service 
jboss.j2ee:binding=message-inflow-driven-bean,jndiName=local/FileMessageListenerMDB2,plugin=invoker,service=EJB
  | 2005-02-10 09:24:47,706 DEBUG 
[org.jboss.ejb.plugins.inflow.JBossMessageEndpointFactory] Starting 
jboss.j2ee:binding=message-inflow-driven-bean,jndiName=local/FileMessageListenerMDB2,plugin=invoker,service=EJB
  | 2005-02-10 09:24:47,726 DEBUG 
[org.jboss.ejb.plugins.inflow.JBossMessageEndpointFactory] Started 
jboss.j2ee:binding=message-inflow-driven-bean,jndiName=local/FileMessageListenerMDB2,plugin=invoker,service=EJB
  | 2005-02-10 09:24:47,726 DEBUG [org.jboss.system.ServiceController] Starting 
dependent components for: 
jboss.j2ee:binding=message-inflow-driven-bean,jndiName=local/FileMessageListenerMDB2,plugin=invoker,service=EJB
 dependent components: []
  | 2005-02-10 09:24:47,726 DEBUG [org.jboss.ejb.MessageDrivenContainer] 
Started jboss.j2ee:jndiName=local/FileMessageListenerMDB2,service=EJB
  | 2005-02-10 09:24:47,726 DEBUG [org.jboss.system.ServiceController] Starting 
dependent components for: 
jboss.j2ee:jndiName=local/FileMessageListenerMDB2,service=EJB dependent 
components: []
  | 2005-02-10 09:24:47,726 DEBUG [org.jboss.ejb.EjbModule] Started 
jboss.j2ee:module=FileConnectorWSHF_MDB2.jar,service=EjbModule
  | 2005-02-10 09:24:47,726 DEBUG [org.jboss.system.ServiceController] Starting 
dependent components for: 
jboss.j2ee:module=FileConnectorWSHF_MDB2.jar,service=EjbModule dependent 
components: []
  | 2005-02-10 09:24:47,726 INFO  [org.jboss.ejb.EJBDeployer] Deployed: 
file:/D:/jboss-4.0.0/server/default/tmp/deploy/tmp48141FileConnector.ear-contents/FileConnectorWSHF_MDB2.jar
  | 2005-02-10 09:24:47,766 DEBUG [org.jboss.deployment.MainDeployer] End 
deployment start on package: FileConnectorWSHF_MDB2.jar
  | 
  | 

Your log shows both have started ok.

I would guess your rar is not responding to the endpointActivation request
correctly on the second request?

One thing your post does highlight is that JBoss JCA's RARDeployment
needs some TRACE logging so you can see what requests are passed to the RAR
http://jira.jboss.com/jira/browse/JBAS-1446

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

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


-------------------------------------------------------
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