User development, A new message was posted in the thread "ConnectionFactory JNDI no found in JNDI view": http://community.jboss.org/message/530738#530738 Author : jaikiran pai Profile : http://community.jboss.org/people/jaikiran Message: -------------------------------------------------------------- Actually that's a bad idea for 2 reasons:1) By "attaching" the log file, you have made sure that not many will look into your issue. Believe me, not many have time to download that zip file, extract it and then look at its contents. If you had "posted" the contents of the logs, someone would have glanced over it and probably might have pointed you to a solution2) As i said in my earlier post, we don't need the "server.log" yet, since that file is too verbose. All we needed was the logs that you saw on the console from the time you started the server.Now coming back to your issue. Here's some portion of that log file: 2010-03-09 16:01:13,825 DEBUG [org.jboss.deployment.scanner.URLDeploymentScanner] Watch URL for: file:/A:/sri/esbtowas/jbossesb-server-4.3.GA/jbossesb-server-4.3.GA/server/default/deploy/bridge-destinations-service-node1.xml -> file:/A:/sri/esbtowas/jbossesb-server-4.3.GA/jbossesb-server-4.3.GA/server/default/deploy/bridge-destinations-service-node1.xml2010-03-09 16:01:13,825 ERROR [org.jboss.deployment.scanner.URLDeploymentScanner] Incomplete Deployment listing:--- Packages waiting for a deployer ---org.jboss.deployment.DeploymentInfo@db2a0100 { url=file:/A:/sri/esbtowas/jbossesb-server-4.3.GA/jbossesb-server-4.3.GA/server/default/deploy/bridge-destinations-service-node1.xml }  deployer: null  status: null  state: INIT_WAITING_DEPLOYER  watch: file:/A:/sri/esbtowas/jbossesb-server-4.3.GA/jbossesb-server-4.3.GA/server/default/deploy/bridge-destinations-service-node1.xml  altDD: null  lastDeployed: 1268130673824  lastModified: 1268130673819  mbeans:--- Incompletely deployed packages ---org.jboss.deployment.DeploymentInfo@db2a0100 { url=file:/A:/sri/esbtowas/jbossesb-server-4.3.GA/jbossesb-server-4.3.GA/server/default/deploy/bridge-destinations-service-node1.xml }  deployer: null  status: null  state: INIT_WAITING_DEPLOYER  watch: file:/A:/sri/esbtowas/jbossesb-server-4.3.GA/jbossesb-server-4.3.GA/server/default/deploy/bridge-destinations-service-node1.xml  altDD: null  lastDeployed: 1268130673824  lastModified: 1268130673819  mbeans:--- MBeans waiting for other MBeans ---ObjectName: jboss.messaging.connectionfactory:service=ConnectionFactory  State: FAILED  Reason: java.lang.IllegalArgumentException: Failed to deploy connection factory since remoting configuration seems incorrect.  I Depend On:    jboss.messaging:service=ServerPeer    jboss.messaging:service=Connector,transport=bisocket    jboss.messaging:service=PostOfficeObjectName: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory  State: FAILED  Reason: java.lang.IllegalArgumentException: Failed to deploy connection factory since remoting configuration seems incorrect.  I Depend On:    jboss.messaging:service=ServerPeer    jboss.messaging:service=Connector,transport=bisocket    jboss.messaging:service=PostOfficeObjectName: jboss.messaging.connectionfactory:service=ClusterPullConnectionFactory  State: FAILED  Reason: java.lang.IllegalArgumentException: Failed to deploy connection factory since remoting configuration seems incorrect.  I Depend On:    jboss.messaging:service=ServerPeer    jboss.messaging:service=Connector,transport=bisocket    jboss.messaging:service=PostOfficeObjectName: jboss.esb:deployment=Quickstart_helloworld.esb  State: FAILED  Reason: org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleException: Unexpected configuration exception from prepareMessageReceiver  I Depend On:    jboss.esb:deployment=jbossesb.esb    jboss.esb.quickstart.destination:service=Queue,name=quickstart_helloworld_Request_esb    jboss.esb.quickstart.destination:service=Queue,name=quickstart_helloworld_Request_gw--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---ObjectName: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory  State: FAILED  Reason: java.lang.IllegalArgumentException: Failed to deploy connection factory since remoting configuration seems incorrect.  I Depend On:    jboss.messaging:service=ServerPeer    jboss.messaging:service=Connector,transport=bisocket    jboss.messaging:service=PostOfficeObjectName: jboss.esb:deployment=Quickstart_helloworld.esb  State: FAILED  Reason: org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleException: Unexpected configuration exception from prepareMessageReceiver  I Depend On:    jboss.esb:deployment=jbossesb.esb    jboss.esb.quickstart.destination:service=Queue,name=quickstart_helloworld_Request_esb    jboss.esb.quickstart.destination:service=Queue,name=quickstart_helloworld_Request_gwObjectName: jboss.messaging.connectionfactory:service=ConnectionFactory  State: FAILED  Reason: java.lang.IllegalArgumentException: Failed to deploy connection factory since remoting configuration seems incorrect.  I Depend On:    jboss.messaging:service=ServerPeer    jboss.messaging:service=Connector,transport=bisocket    jboss.messaging:service=PostOfficeObjectName: jboss.messaging.connectionfactory:service=ClusterPullConnectionFactory  State: FAILED  Reason: java.lang.IllegalArgumentException: Failed to deploy connection factory since remoting configuration seems incorrect.  I Depend On:    jboss.messaging:service=ServerPeer    jboss.messaging:service=Connector,transport=bisocket    jboss.messaging:service=PostOffice....2010-03-09 16:01:13,985 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139)] Started in 27s:142ms     1) You are using JBossESB - which you never mentioned in your post. I personally have no experience with JBossESB2) You seem have to renamed a file in deploy folder to bridge-destinations-service-node1.xml. That won't work because JBoss cannot find a deployer for that file. It has to end with -service.xml3) The error logs show that the connection factories failed deployment because of: Reason: java.lang.IllegalArgumentException: Failed to deploy connection factory since remoting configuration seems incorrect. 4) Half of the logs show the version as 4.2.3 and the last line shows the version as 4.2.2. And you mentioned in your earlier post that you are using 4.2.1 At this point, i would suggest that you start from a clean installation. If you are using JBossESB, then let us know, maybe this thread needs to be moved to JBossESB user forum   -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/530738#530738