Integration

I have a bpel that is putting messges in a queue of weblogic 8.1 (remote server). I have made entry in oc4j-ra.xml as

<connector-factory location="eis/wljms/WLQueue" connector-name="Connection_factory_WL">
<config-property name="connectionFactoryLocation" value="CDR.QueueConnectionFactory"/>
<config-property name="factoryProperties" value="java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory;java.naming.provider.url=t3://xx.xx.xx.xx:7001"/>
<config-property name="acknowledgeMode" value="CLIENT_ACKNOWLEDGE"/>
<config-property name="isTopic" value="false"/>
<config-property name="isTransacted" value="true"/>
<config-property name="username" value=""/>
<config-property name="password" value=""/>
<connection-pooling use="none">
</connection-pooling>
<security-config use="none">
</security-config>
</connector-factory>

I have copied weblogic.jar to j2ee/oc4j_soa/connectors/JmsAdapter/JmsAdapter folder. But when i run my bpel process it throws error,

<2009-05-20 09:19:17,569> <DEBUG> <default.collaxa.cube.ws> <JMSAdapter::Outbound> JMSConnectionFactoryFactory_getConnectionFactory: JNDI Naming exception when looking up CDR.QueueConnectionFactory: null
<2009-05-20 09:19:17,569> <DEBUG> <default.collaxa.cube.ws> <JMSAdapter::Outbound> JMSConnectionFactoryFactory_getConnectionFactory: Will now try to determine if the 'ConnectionFactoryLocation' CDR.QueueConnectionFactory is a loadable Java class. If so, the above exception can be ignored.
<2009-05-20 09:19:17,570> <DEBUG> <default.collaxa.cube.ws> <JMSAdapter::Outbound> Error while creating managed connection:
<2009-05-20 09:19:17,571> <DEBUG> <default.collaxa.cube.ws> <JMSAdapter::Outbound>
ORABPEL-12141
ERRJMS_CONN_FAC_NOT_FOUND.
Unable to instantiate connection factory. JMS adapter was unable to look up the connection factor CDR.QueueConnectionFactory neither through JNDI nor instantiate it as a Java class [Caused by: t3://xx.xx.xx.xx:7001: Bootstrap to: xx.xx.xx.xx/xx.xx.xx.xx:7001' over: 't3' got an error or timed out]
Please examine the log file to determine the problem.

at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getConnectionFactory(JMSConnectionFactoryFactory.java:157)
at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getQueueConnectionFactory(JMSConnectionFactoryFactory.java:98)
at oracle.tip.adapter.jms.JMS.JMSConnection.init(JMSConnection.java:191)
at oracle.tip.adapter.jms.JMS.JMSConnection.<init>(JMSConnection.java:132)
at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createConnection(JmsManagedConnectionFactory.java:426)
at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createDefaultConnection(JmsManagedConnectionFactory.java:417)
at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createConnection(JmsManagedConnectionFactory.java:380)
at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createManagedConnection(JmsManagedConnectionFactory.java:104)
at oracle.tip.adapter.jms.JmsDefaultConnectionManager.allocateConnection(JmsDefaultConnectionManager.java:76)
at oracle.tip.adapter.jms.JmsConnectionFactory.getConnection(JmsConnectionFactory.java:125)
at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.createConsumer(JMSMessageConsumer.java:269)
at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.init(JMSMessageConsumer.java:223)
at oracle.tip.adapter.jms.inbound.JmsConsumer.init(JmsConsumer.java:159)
at oracle.tip.adapter.jms.JmsEndpoint.run(JmsEndpoint.java:151)
at oracle.tip.adapter.fw.jca.work.WorkerJob.go(WorkerJob.java:51)
at oracle.tip.adapter.fw.common.ThreadPool.run(ThreadPool.java:272)
at java.lang.Thread.run(Thread.java:595)
Caused by: javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://xx.xx.xx.xx:7001: Bootstrap to: xx.xx.xx.xx/xx.xx.xx.xx:7001' over: 't3' got an error or timed out]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:47)
at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:651)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:320)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:253)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:135)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at oracle.tip.adapter.jms.JMS.JMSFactory.getInitialContext(JMSFactory.java:189)
at oracle.tip.adapter.jms.JMS.JMSFactory.jndiLookup(JMSFactory.java:237)
at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getConnectionFactory(JMSConnectionFactoryFactory.java:138)
... 16 more
Caused by: java.net.ConnectException: t3://xx.xx.xx.xx:7001: Bootstrap to: xx.xx.xx.xx/xx.xx.xx.xx:7001' over: 't3' got an error or timed out
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:200)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:125)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:310)
... 25 more

I am able to ping remote weblogic server so connectivity is not a problem. Also, to add to the complexity , the same bpel code and configuration is working from other environment. I dont have clue whats preventing a jndi lookup from this environment :(
SoA Suite ver 10.1.3.3.0
Any help in this regard is appreciated. Thanks.