Problem having a MDB connect to a remote JMS Topic
Hi, I am having problem making an MDB listen to a remote JMS Topic. Here's the
scenario:
Two Weblogic servers (6.1 sp3) running on the same machine (W2K) - they arenot part of a cluster......both are independent servers
One WLS is listening on port 7001 (Domain=WLSDomain1; Target=Server1) and thesecond one on 8001 (Domain=WLSDomain2; Target=Server1 {This is not a typo, the
target is Server1})
In WLSDomain1/Server1, I have a JMS Topic defined as follows (in its config.xmlfile):
<JMSServer Name="EventServicesJMSServer"
Store="ESJMSServerFileStore" Targets="Server1">
<JMSTopic JNDIName="jms/EventServicesTopic7001"
Name="jms/EventServicesTopic7001" StoreEnabled="true"/>
</JMSServer>
In WLSDomain2/Server1, I have a JMS Topic defined as follows (in config.xmlfile):
<JMSServer Name="EventServicesJMSServer"
Store="ESJMSServerFileStore" Targets="Server1">
<JMSTopic JNDIName="jms/EventServicesTopic8001"
Name="jms/EventServicesTopic8001" StoreEnabled="true"/>
</JMSServer>
An MDB is deployed on WLSDomain1/Server1 with the following elements in itsweblogic-jar.xml file (I haven't included the entire weblogic-jar.xml file, only
the relevant info):
<message-driven-descriptor>
<pool>
<max-beans-in-free-pool>1</max-beans-in-free-pool>
<initial-beans-in-free-pool>0</initial-beans-in-free-pool>
</pool>
<!-- This MDB is defined to listen to a Topic in another WLS Server running
on port 8001 -->
<destination-jndi-name>jms/EventServicesTopic8001</destination-jndi-name>
<initial-context-factory>weblogic.jndi.WLInitialContextFactory</initial-context-factory>
<provider-url>t3://localhost:8001</provider-url>
<connection-factory-jndi-name>weblogic/jms/ConnectionFactory</connection-factory-jndi-name>
</message-driven-descriptor>
An MDB is deployed on WLSDomain2/Server1 with the following elements in itsweblogic-jar.xml file (I haven't included the entire weblogic-jar.xml file, only
the relevant info):
<message-driven-descriptor>
<pool>
<max-beans-in-free-pool>1</max-beans-in-free-pool>
<initial-beans-in-free-pool>0</initial-beans-in-free-pool>
</pool>
<!-- This MDB is defined to listen to a Topic in another WLS Server running
on port 7001 -->
<destination-jndi-name>jms/EventServicesTopic7001</destination-jndi-name>
<initial-context-factory>weblogic.jndi.WLInitialContextFactory</initial-context-factory>
<provider-url>t3://localhost:7001</provider-url>
<connection-factory-jndi-name>weblogic/jms/ConnectionFactory</connection-factory-jndi-name>
</message-driven-descriptor>
After starting both the WLS servers, I've verified that they have made connectionsto each other; the Topics are defined in the JNDI tree of the respective servers;
and the MDBs have been deployed in their respective servers. But the MDBs can't
see/connect to their respective JMS destination. Here's the error message and
stack trace from one the WLS server's trace file:
<Apr 17, 2003 4:58:25 PM GMT> <Warning> <EJB> <The Message-Driven EJB: com.manu.
common.server.objectServices.CSMEventListenerMDB_8001 is unable to connect to
the JMS destination: jms/EventServicesTopic8001. The EJB container will automatically
attempt to
re-establish the connection with the JMS server. This warning may occur during
WebLogic Cluster start-up if the JMS destination is located on another server.
When the JMS server connection is re-established, the Message-Driven EJB will
again receive JMS messages.
The Error was:
weblogic.jms.common.JMSException: Connection not found
at weblogic.jms.dispatcher.InvocableManager.invocableFind(InvocableManager.java:121)
at weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:509)
at weblogic.jms.dispatcher.DispatcherImpl.dispatchSync(DispatcherImpl.java:272)
at weblogic.jms.client.JMSConnection.sessionCreate(JMSConnection.java:268)
at weblogic.jms.client.JMSConnection.createTopicSession(JMSConnection.java:245)
at weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectionPoller.java:522)
at weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller.java:418)
at weblogic.ejb20.internal.JMSConnectionPoller.trigger(JMSConnectionPoller.java:348)
at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:238)
at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:229)
at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:6
9)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Have you run into a similar problem? Any suggestion?
Thanks,
Farook
Hi, I am having problem making an MDB listen to a remote JMS Topic. Here's the
scenario:
Two Weblogic servers (6.1 sp3) running on the same machine (W2K) - they arenot part of a cluster......both are independent servers
One WLS is listening on port 7001 (Domain=WLSDomain1; Target=Server1) and thesecond one on 8001 (Domain=WLSDomain2; Target=Server1 {This is not a typo, the
target is Server1})
In WLSDomain1/Server1, I have a JMS Topic defined as follows (in its config.xmlfile):
<JMSServer Name="EventServicesJMSServer"
Store="ESJMSServerFileStore" Targets="Server1">
<JMSTopic JNDIName="jms/EventServicesTopic7001"
Name="jms/EventServicesTopic7001" StoreEnabled="true"/>
</JMSServer>
In WLSDomain2/Server1, I have a JMS Topic defined as follows (in config.xmlfile):
<JMSServer Name="EventServicesJMSServer"
Store="ESJMSServerFileStore" Targets="Server1">
<JMSTopic JNDIName="jms/EventServicesTopic8001"
Name="jms/EventServicesTopic8001" StoreEnabled="true"/>
</JMSServer>
An MDB is deployed on WLSDomain1/Server1 with the following elements in itsweblogic-jar.xml file (I haven't included the entire weblogic-jar.xml file, only
the relevant info):
<message-driven-descriptor>
<pool>
<max-beans-in-free-pool>1</max-beans-in-free-pool>
<initial-beans-in-free-pool>0</initial-beans-in-free-pool>
</pool>
<!-- This MDB is defined to listen to a Topic in another WLS Server running
on port 8001 -->
<destination-jndi-name>jms/EventServicesTopic8001</destination-jndi-name>
<initial-context-factory>weblogic.jndi.WLInitialContextFactory</initial-context-factory>
<provider-url>t3://localhost:8001</provider-url>
<connection-factory-jndi-name>weblogic/jms/ConnectionFactory</connection-factory-jndi-name>
</message-driven-descriptor>
An MDB is deployed on WLSDomain2/Server1 with the following elements in itsweblogic-jar.xml file (I haven't included the entire weblogic-jar.xml file, only
the relevant info):
<message-driven-descriptor>
<pool>
<max-beans-in-free-pool>1</max-beans-in-free-pool>
<initial-beans-in-free-pool>0</initial-beans-in-free-pool>
</pool>
<!-- This MDB is defined to listen to a Topic in another WLS Server running
on port 7001 -->
<destination-jndi-name>jms/EventServicesTopic7001</destination-jndi-name>
<initial-context-factory>weblogic.jndi.WLInitialContextFactory</initial-context-factory>
<provider-url>t3://localhost:7001</provider-url>
<connection-factory-jndi-name>weblogic/jms/ConnectionFactory</connection-factory-jndi-name>
</message-driven-descriptor>
After starting both the WLS servers, I've verified that they have made connectionsto each other; the Topics are defined in the JNDI tree of the respective servers;
and the MDBs have been deployed in their respective servers. But the MDBs can't
see/connect to their respective JMS destination. Here's the error message and
stack trace from one the WLS server's trace file:
<Apr 17, 2003 4:58:25 PM GMT> <Warning> <EJB> <The Message-Driven EJB: com.manu.
common.server.objectServices.CSMEventListenerMDB_8001 is unable to connect to
the JMS destination: jms/EventServicesTopic8001. The EJB container will automatically
attempt to
re-establish the connection with the JMS server. This warning may occur during
WebLogic Cluster start-up if the JMS destination is located on another server.
When the JMS server connection is re-established, the Message-Driven EJB will
again receive JMS messages.
The Error was:
weblogic.jms.common.JMSException: Connection not found
at weblogic.jms.dispatcher.InvocableManager.invocableFind(InvocableManager.java:121)
at weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:509)
at weblogic.jms.dispatcher.DispatcherImpl.dispatchSync(DispatcherImpl.java:272)
at weblogic.jms.client.JMSConnection.sessionCreate(JMSConnection.java:268)
at weblogic.jms.client.JMSConnection.createTopicSession(JMSConnection.java:245)
at weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectionPoller.java:522)
at weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller.java:418)
at weblogic.ejb20.internal.JMSConnectionPoller.trigger(JMSConnectionPoller.java:348)
at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:238)
at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:229)
at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:6
9)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Have you run into a similar problem? Any suggestion?
Thanks,
Farook
Similar Messages
-
Problem having a MDB connect to a remote JMS Topic (WLS 6.1 sp3)
Hi, I am having problem making an MDB listen to a remote JMS Topic. Here's the
scenario:
> Two Weblogic servers (6.1 sp3) running on the same machine (W2K) - they are
not part of a cluster......both are independent servers
> One WLS is listening on port 7001 (Domain=WLSDomain1; Target=Server1) and the
second one on 8001 (Domain=WLSDomain2; Target=Server1 {This is not a typo, the
target is Server1})
> In WLSDomain1/Server1, I have a JMS Topic defined as follows (in its config.xml
file):
<JMSServer Name="EventServicesJMSServer"
Store="ESJMSServerFileStore" Targets="Server1">
<JMSTopic JNDIName="jms/EventServicesTopic7001"
Name="jms/EventServicesTopic7001" StoreEnabled="true"/>
</JMSServer>
> In WLSDomain2/Server1, I have a JMS Topic defined as follows (in config.xml
file):
<JMSServer Name="EventServicesJMSServer"
Store="ESJMSServerFileStore" Targets="Server1">
<JMSTopic JNDIName="jms/EventServicesTopic8001"
Name="jms/EventServicesTopic8001" StoreEnabled="true"/>
</JMSServer>
> An MDB is deployed on WLSDomain1/Server1 with the following elements in its
weblogic-jar.xml file (I haven't included the entire weblogic-jar.xml file, only
the relevant info):
<message-driven-descriptor>
<pool>
<max-beans-in-free-pool>1</max-beans-in-free-pool>
<initial-beans-in-free-pool>0</initial-beans-in-free-pool>
</pool>
<!-- This MDB is defined to listen to a Topic in another WLS Server running
on port 8001 -->
<destination-jndi-name>jms/EventServicesTopic8001</destination-jndi-name>
<initial-context-factory>weblogic.jndi.WLInitialContextFactory</initial-context-factory>
<provider-url>t3://localhost:8001</provider-url>
<connection-factory-jndi-name>weblogic/jms/ConnectionFactory</connection-factory-jndi-name>
</message-driven-descriptor>
> An MDB is deployed on WLSDomain2/Server1 with the following elements in its
weblogic-jar.xml file (I haven't included the entire weblogic-jar.xml file, only
the relevant info):
<message-driven-descriptor>
<pool>
<max-beans-in-free-pool>1</max-beans-in-free-pool>
<initial-beans-in-free-pool>0</initial-beans-in-free-pool>
</pool>
<!-- This MDB is defined to listen to a Topic in another WLS Server running
on port 7001 -->
<destination-jndi-name>jms/EventServicesTopic7001</destination-jndi-name>
<initial-context-factory>weblogic.jndi.WLInitialContextFactory</initial-context-factory>
<provider-url>t3://localhost:7001</provider-url>
<connection-factory-jndi-name>weblogic/jms/ConnectionFactory</connection-factory-jndi-name>
</message-driven-descriptor>
> After starting both the WLS servers, I've verified that they have made connections
to each other; the Topics are defined in the JNDI tree of the respective servers;
and the MDBs have been deployed in their respective servers. But the MDBs can't
see/connect to their respective JMS destination. Here's the error message and
stack trace from one the WLS server's trace file:
<Apr 17, 2003 4:58:25 PM GMT> <Warning> <EJB> <The Message-Driven EJB: com.manu.
common.server.objectServices.CSMEventListenerMDB_8001 is unable to connect to
the JMS destination: jms/EventServicesTopic8001. The EJB container will automatically
attempt to
re-establish the connection with the JMS server. This warning may occur during
WebLogic Cluster start-up if the JMS destination is located on another server.
When the JMS server connection is re-established, the Message-Driven EJB will
again receive JMS messages.
The Error was:
weblogic.jms.common.JMSException: Connection not found
at weblogic.jms.dispatcher.InvocableManager.invocableFind(InvocableManager.java:121)
at weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:509)
at weblogic.jms.dispatcher.DispatcherImpl.dispatchSync(DispatcherImpl.java:272)
at weblogic.jms.client.JMSConnection.sessionCreate(JMSConnection.java:268)
at weblogic.jms.client.JMSConnection.createTopicSession(JMSConnection.java:245)
at weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectionPoller.java:522)
at weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller.java:418)
at weblogic.ejb20.internal.JMSConnectionPoller.trigger(JMSConnectionPoller.java:348)
at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:238)
at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:229)
at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:6
9)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Have you run into a similar problem? Any suggestion?
Thanks,
Farook
FAQ. Naming conflict. To interop between domains make sure:
All WL Servers are named differently.
All JMS Servers are named differently.
All JMS Stores are named differently.
Tom
Farook Wadia wrote:
> Hi, I am having problem making an MDB listen to a remote JMS Topic. Here's the
> scenario:
>
>
>>Two Weblogic servers (6.1 sp3) running on the same machine (W2K) - they are
>
> not part of a cluster......both are independent servers
>
>
>>One WLS is listening on port 7001 (Domain=WLSDomain1; Target=Server1) and the
>
> second one on 8001 (Domain=WLSDomain2; Target=Server1 {This is not a typo, the
> target is Server1})
>
>
>>In WLSDomain1/Server1, I have a JMS Topic defined as follows (in its config.xml
>
> file):
>
> <JMSServer Name="EventServicesJMSServer"
> Store="ESJMSServerFileStore" Targets="Server1">
> <JMSTopic JNDIName="jms/EventServicesTopic7001"
> Name="jms/EventServicesTopic7001" StoreEnabled="true"/>
> </JMSServer>
>
>>In WLSDomain2/Server1, I have a JMS Topic defined as follows (in config.xml
>
> file):
>
> <JMSServer Name="EventServicesJMSServer"
> Store="ESJMSServerFileStore" Targets="Server1">
> <JMSTopic JNDIName="jms/EventServicesTopic8001"
> Name="jms/EventServicesTopic8001" StoreEnabled="true"/>
> </JMSServer>
>
>>An MDB is deployed on WLSDomain1/Server1 with the following elements in its
>
> weblogic-jar.xml file (I haven't included the entire weblogic-jar.xml file, only
> the relevant info):
>
> ..
> <message-driven-descriptor>
> <pool>
> <max-beans-in-free-pool>1</max-beans-in-free-pool>
> <initial-beans-in-free-pool>0</initial-beans-in-free-pool>
> </pool>
> <!-- This MDB is defined to listen to a Topic in another WLS Server running
> on port 8001 -->
> <destination-jndi-name>jms/EventServicesTopic8001</destination-jndi-name>
> <initial-context-factory>weblogic.jndi.WLInitialContextFactory</initial-context-factory>
> <provider-url>t3://localhost:8001</provider-url>
> <connection-factory-jndi-name>weblogic/jms/ConnectionFactory</connection-factory-jndi-name>
> </message-driven-descriptor>
> ...
>
>
>>An MDB is deployed on WLSDomain2/Server1 with the following elements in its
>
> weblogic-jar.xml file (I haven't included the entire weblogic-jar.xml file, only
> the relevant info):
>
> ..
> <message-driven-descriptor>
> <pool>
> <max-beans-in-free-pool>1</max-beans-in-free-pool>
> <initial-beans-in-free-pool>0</initial-beans-in-free-pool>
> </pool>
> <!-- This MDB is defined to listen to a Topic in another WLS Server running
> on port 7001 -->
> <destination-jndi-name>jms/EventServicesTopic7001</destination-jndi-name>
> <initial-context-factory>weblogic.jndi.WLInitialContextFactory</initial-context-factory>
> <provider-url>t3://localhost:7001</provider-url>
> <connection-factory-jndi-name>weblogic/jms/ConnectionFactory</connection-factory-jndi-name>
> </message-driven-descriptor>
> ...
>
>
>>After starting both the WLS servers, I've verified that they have made connections
>
> to each other; the Topics are defined in the JNDI tree of the respective servers;
> and the MDBs have been deployed in their respective servers. But the MDBs can't
> see/connect to their respective JMS destination. Here's the error message and
> stack trace from one the WLS server's trace file:
>
> <Apr 17, 2003 4:58:25 PM GMT> <Warning> <EJB> <The Message-Driven EJB: com.manu.
> common.server.objectServices.CSMEventListenerMDB_8001 is unable to connect to
> the JMS destination: jms/EventServicesTopic8001. The EJB container will automatically
> attempt to
> re-establish the connection with the JMS server. This warning may occur during
> WebLogic Cluster start-up if the JMS destination is located on another server.
> When the JMS server connection is re-established, the Message-Driven EJB will
> again receive JMS messages.
> The Error was:
> weblogic.jms.common.JMSException: Connection not found
> at weblogic.jms.dispatcher.InvocableManager.invocableFind(InvocableManager.java:121)
> at weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:509)
> at weblogic.jms.dispatcher.DispatcherImpl.dispatchSync(DispatcherImpl.java:272)
> at weblogic.jms.client.JMSConnection.sessionCreate(JMSConnection.java:268)
> at weblogic.jms.client.JMSConnection.createTopicSession(JMSConnection.java:245)
> at weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectionPoller.java:522)
> at weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller.java:418)
> at weblogic.ejb20.internal.JMSConnectionPoller.trigger(JMSConnectionPoller.java:348)
> at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:238)
> at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:229)
> at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:6
> 9)
> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
>
>
> Have you run into a similar problem? Any suggestion?
>
> Thanks,
>
> Farook
-
Connecting to a Remote JMS provider from MDB in jboss-4.0
Hi,
I am using Tibco as a remote JMS Provider. When the Tibco server is running on the same machine as JBoss-4.0, the Message Driven Bean deployed in Jboss is able to get the messages from the queue on Tibco server.
I have added the following configuration to jms-ds.xml file
<!-- The JMS provider loader -->
<mbean code="org.jboss.jms.jndi.JMSProviderLoader"
name="jboss.mq:service=JMSProviderLoader,name=JMSProvider">
<attribute name="ProviderName">TIBCOJMSProvider</attribute>
<attribute name="ProviderAdapterClass">
org.jboss.jms.jndi.JNDIProviderAdapter
</attribute>
<!-- The combined connection factory -->
<!--attribute name="FactoryRef">XAConnectionFactory</attribute-->
<!-- The queue connection factory -->
<attribute name="QueueFactoryRef">XAQueueConnectionFactory</attribute>
<!-- The topic factory -->
<attribute name="TopicFactoryRef">XATopicConnectionFactory</attribute>
<attribute name="Properties">
java.naming.factory.initial=com.tibco.tibjms.naming.TibjmsInitialContextFactory
java.naming.factory.url.pkgs=com.tibco.tibjms.naming
java.naming.provider.url=tibjmsnaming://TibcoHost:7222
</attribute>
</mbean>
Also following invoker proxy binding is added to standardjboss.xml & it is used in MDB's jboss.xml
<invoker-proxy-binding>
<name>my-mdb-invoker</name>
<invoker-mbean>does-not-matter</invoker-mbean>
<proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-factory>
<proxy-factory-config>
<JMSProviderAdapterJNDI>TIBCOJMSProvider</JMSProviderAdapterJNDI>
<ServerSessionPoolFactoryJNDI>StdJMSPool</ServerSessionPoolFactoryJNDI>
<MinimumSize>1</MinimumSize>
<KeepAliveMillis>30000</KeepAliveMillis>
<MaximumSize>15</MaximumSize>
<MaxMessages>1</MaxMessages>
<MDBConfig>
<ReconnectIntervalSec>10</ReconnectIntervalSec>
<DLQConfig>
<DestinationQueue>queue/DLQ</DestinationQueue>
<MaxTimesRedelivered>10</MaxTimesRedelivered>
<TimeToLive>0</TimeToLive>
</DLQConfig>
</MDBConfig>
</proxy-factory-config>
</invoker-proxy-binding>
But When I try to use Tibco server on some other machine it throws following exception. It actually tryies to connect to Tibco server on same machine.
javax.jms.JMSException: Failed to connect to the server at tcp://localhost:7222
at com.tibco.tibjms.TibjmsxLinkTcp._createSocket(TibjmsxLinkTcp.java:748)
at com.tibco.tibjms.TibjmsxLinkTcp.connect(TibjmsxLinkTcp.java:857)
at com.tibco.tibjms.TibjmsConnection._create(TibjmsConnection.java:611)
at com.tibco.tibjms.TibjmsConnection.<init>(TibjmsConnection.java:1769)
at com.tibco.tibjms.TibjmsQueueConnection.<init>(TibjmsQueueConnection.java:35)
at com.tibco.tibjms.TibjmsxCFImpl._createImpl(TibjmsxCFImpl.java:90)
at com.tibco.tibjms.TibjmsxCFImpl._createConnection(TibjmsxCFImpl.java:151)
at com.tibco.tibjms.TibjmsXAQueueConnectionFactory.createQueueConnection(TibjmsXAQueueConnectionFactory.java:140
at org.jboss.ejb.plugins.jms.DLQHandler.createService(DLQHandler.java:152)
at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:237)
at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:164)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerCreate(JMSContainerInvoker.java:545)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.startService(JMSContainerInvoker.java:767)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:271)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:221)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891)
at $Proxy45.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:416)
at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:170)
at org.jboss.ejb.MessageDrivenContainer.startService(MessageDrivenContainer.java:262)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:271)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:221)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:416)
at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy43.start(Unknown Source)
at org.jboss.ejb.EjbModule.startService(EjbModule.java:394)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:271)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:221)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:416)
at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy19.start(Unknown Source)
at org.jboss.ejb.EJBDeployer.start(EJBDeployer.java:605)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:935)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:746)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:709)
at sun.reflect.GeneratedMethodAccessor30.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:119)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:131)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy8.deploy(Unknown Source)Hi,
I am using Tibco as a remote JMS Provider. When the Tibco server is running on the same machine as JBoss-4.0, the Message Driven Bean deployed in Jboss is able to get the messages from the queue on Tibco server.
I have added the following configuration to jms-ds.xml file
<!-- The JMS provider loader -->
<mbean code="org.jboss.jms.jndi.JMSProviderLoader"
name="jboss.mq:service=JMSProviderLoader,name=JMSProvider">
<attribute name="ProviderName">TIBCOJMSProvider</attribute>
<attribute name="ProviderAdapterClass">
org.jboss.jms.jndi.JNDIProviderAdapter
</attribute>
<!-- The combined connection factory -->
<!--attribute name="FactoryRef">XAConnectionFactory</attribute-->
<!-- The queue connection factory -->
<attribute name="QueueFactoryRef">XAQueueConnectionFactory</attribute>
<!-- The topic factory -->
<attribute name="TopicFactoryRef">XATopicConnectionFactory</attribute>
<attribute name="Properties">
java.naming.factory.initial=com.tibco.tibjms.naming.TibjmsInitialContextFactory
java.naming.factory.url.pkgs=com.tibco.tibjms.naming
java.naming.provider.url=tibjmsnaming://TibcoHost:7222
</attribute>
</mbean>
Also following invoker proxy binding is added to standardjboss.xml & it is used in MDB's jboss.xml
<invoker-proxy-binding>
<name>my-mdb-invoker</name>
<invoker-mbean>does-not-matter</invoker-mbean>
<proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-factory>
<proxy-factory-config>
<JMSProviderAdapterJNDI>TIBCOJMSProvider</JMSProviderAdapterJNDI>
<ServerSessionPoolFactoryJNDI>StdJMSPool</ServerSessionPoolFactoryJNDI>
<MinimumSize>1</MinimumSize>
<KeepAliveMillis>30000</KeepAliveMillis>
<MaximumSize>15</MaximumSize>
<MaxMessages>1</MaxMessages>
<MDBConfig>
<ReconnectIntervalSec>10</ReconnectIntervalSec>
<DLQConfig>
<DestinationQueue>queue/DLQ</DestinationQueue>
<MaxTimesRedelivered>10</MaxTimesRedelivered>
<TimeToLive>0</TimeToLive>
</DLQConfig>
</MDBConfig>
</proxy-factory-config>
</invoker-proxy-binding>
But When I try to use Tibco server on some other machine it throws following exception. It actually tryies to connect to Tibco server on same machine.
javax.jms.JMSException: Failed to connect to the server at tcp://localhost:7222
at com.tibco.tibjms.TibjmsxLinkTcp._createSocket(TibjmsxLinkTcp.java:748)
at com.tibco.tibjms.TibjmsxLinkTcp.connect(TibjmsxLinkTcp.java:857)
at com.tibco.tibjms.TibjmsConnection._create(TibjmsConnection.java:611)
at com.tibco.tibjms.TibjmsConnection.<init>(TibjmsConnection.java:1769)
at com.tibco.tibjms.TibjmsQueueConnection.<init>(TibjmsQueueConnection.java:35)
at com.tibco.tibjms.TibjmsxCFImpl._createImpl(TibjmsxCFImpl.java:90)
at com.tibco.tibjms.TibjmsxCFImpl._createConnection(TibjmsxCFImpl.java:151)
at com.tibco.tibjms.TibjmsXAQueueConnectionFactory.createQueueConnection(TibjmsXAQueueConnectionFactory.java:140
at org.jboss.ejb.plugins.jms.DLQHandler.createService(DLQHandler.java:152)
at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:237)
at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:164)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerCreate(JMSContainerInvoker.java:545)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.startService(JMSContainerInvoker.java:767)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:271)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:221)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891)
at $Proxy45.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:416)
at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:170)
at org.jboss.ejb.MessageDrivenContainer.startService(MessageDrivenContainer.java:262)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:271)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:221)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:416)
at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy43.start(Unknown Source)
at org.jboss.ejb.EjbModule.startService(EjbModule.java:394)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:271)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:221)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:416)
at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy19.start(Unknown Source)
at org.jboss.ejb.EJBDeployer.start(EJBDeployer.java:605)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:935)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:746)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:709)
at sun.reflect.GeneratedMethodAccessor30.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:119)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:131)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy8.deploy(Unknown Source) -
Win XP : problems for itune to connect the airport remote speakers
Hi there,
My config is iTunes installed on my PC, a Tecom wifi router and two airport express base stations connected to speakers in different rooms of my flat.
At first, iTunes has no problem for seeing the airport stations and the music goes well through the wifi.
After two or three days, the PC doesn't see the stations anymore in iTunes (they actually still show, but in gray) .
If I want them to be seen again, I need to close iTunes, go to "connexions", disconnect my PC from the network, connect again, run iTunes again, and then... it works !
That's a bit boring. As strange as it could be, the act of shuting down my PC every night and running it "fresh" every morning doesn't help.
Has any one any suggestion on how it could work better ?Hello Deb Parks. Welcome to the Apple Discussions!
I'm not sure if, by product key, you mean the encryption password for your 802.11n AirPort Extreme Base Station's (AEBSn) wireless network. Is your AEBSn's wireless network currently running encryption (WEP or WPA)? If so, temporarily disable it, and then, see if the PC can connect. -
MDBs failed to connect to remote JMS server
Hi,
We currently have 2 clusters: one is a regular cluster (cluster1) and the other is JMS cluster (cluster2). Our JMS server and filestore are targeted to a migratable server in JMS cluster.
In our weblogic-ejb-jar.xml, we added element <provider-url> to the <message-driven-descriptor> to allow JMS remote connection as follows:
<weblogic-enterprise-bean>
<ejb-name>MyBean</ejb-name>
<message-driven-descriptor>
<destination-jndi-name>MyTopic</destination-jndi-name>
<provider-url>t3://myhost:19009,myhost:19011</provider-url>
<connection-factory-jndi-name>MyConnectionFactory</connection-factory-jn
di-name>
</message-driven-descriptor>
</weblogic-enterprise-bean>
When we deployed our application, the Connection Status of MyBean showed "disconnected". I have tried different values (t3://myhost:19009;t3://myhost:19011) and
(t3://myhost:19009) but got the same result.
When I re-targeted the JMS server and filestore to a regular server (instead of migratable server), I was able to connect remotely. But because we want to be able to migrate our JMS server (auto and manually), I have to target it to a migratable server.
I could not figure out why my MDBs failed to connect to a remote JMS server when it is targeted to a migratable server? Is there a restriction that we have to target to a regular server in order to connect remotely or I'm doing something wrong?
Any help would be greatly appreciated.
Thanks,
ThaoI'm using WL9.2 and my migratable server is actually up and running (is that what you mean about booted?). I meant checking your log files to make sure that the JMS server itself actually booted, not checking that the host WL server was up. (For example you should see INFO messages indicating that the JMS server has loaded "X" records from its persistent store).
>>> Could you elaborate on the known problem?
9.x MDBs have special code for enhanced handling of remote distributed destinations. I'm guessing that this code is somehow causing problems when the remote JMS server is migratable. I don't have enough information to elaborate further than that.
>>> What else I can try?
Beyond contacting customer support, I'm not sure.
Tom -
Unable to start connection on remote JMS server
HI
I have a setup in which I try to connect to a remote JMS Server (running on a
remote WLS 8.1 SP1). It is able to get the named QueueConnectionFactory, fails
to start the connection. The stack trace is
weblogic.jms.common.JMSException: Connection not found
at weblogic.jms.dispatcher.InvocableManager.invocableFind(InvocableManager.java:136)
at weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:596)
at weblogic.jms.dispatcher.DispatcherImpl.dispatchSync(DispatcherImpl.java:153)
at weblogic.jms.client.JMSConnection.start(JMSConnection.java:567)
at uk.co.concise.payments.event.EventProcessorServiceAsynchBD.(EventProcessorServiceAsynchBD.java:82)
at uk.co.concise.payments.state.ejb.ObjectStateServiceXDBean.ejbCreate(ObjectStateServiceXDBean.java:213)
at uk.co.concise.payments.state.ejb.ObjectStateService_1th3um_Impl.ejbCreate(ObjectStateService_1th3um_Impl.java:135)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at weblogic.ejb20.pool.StatelessSessionPool.createBean(StatelessSessionPool.java:172)
at weblogic.ejb20.pool.StatelessSessionPool.getBean(StatelessSessionPool.java:110)
at weblogic.ejb20.manager.StatelessManager.preInvoke(StatelessManager.java:140)
at weblogic.ejb20.internal.BaseEJBLocalObject.preInvoke(BaseEJBLocalObject.java:229)
at weblogic.ejb20.internal.StatelessEJBLocalObject.preInvoke(StatelessEJBLocalObject.java:54)
at uk.co.concise.payments.state.ejb.ObjectStateService_1th3um_ELOImpl.createAndGetStateForObject(ObjectStateService_1th3um_ELOImpl.java:273)
at uk.co.concise.payments.state.ObjectStateServiceBD.createAndGetStateForObject(ObjectStateServiceBD.java:123)
at uk.co.concise.payments.submission.ejb.SubmissionServiceXDBean.createSubmission(SubmissionServiceXDBean.java:92)
at uk.co.concise.payments.submission.ejb.SubmissionService_o0dxp8_ELOImpl.createSubmission(SubmissionService_o0dxp8_ELOImpl.java:162)
at uk.co.concise.payments.submission.SubmissionServiceBD.createSubmission(SubmissionServiceBD.java:42)
at uk.co.concise.payments.submission.webapp.SubmitPaymentFileAction.execute(SubmitPaymentFileAction.java:216)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:446)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:266)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1292)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:510)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1053)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:387)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at uk.co.concise.payments.logon.filter.LogonFilter.doFilter(LogonFilter.java:38)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6316)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3622)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2569)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
Any ideas on what could be wrong
thanks
jaz
Thanks Tom
It fixed the problem.
Jaz
Tom Barnes <[email protected]> wrote:
>Hi,
>
>I think "Connection not found" may be a symptom of a name
>conflict. Make sure:
> All JMS servers are named differently
> All WL servers are named differently
> All JMS stores are named differently
>All three above are needed for various reasons, although I think
>it is only first that fixes your particular problem.
>
>A google search of this newsgroup would likely have yielded this
>same answer.
>
>Tom
>
>jasmeet wrote:
>
>> HI
>>
>> I have a setup in which I try to connect to a remote JMS Server (running
>on a
>> remote WLS 8.1 SP1). It is able to get the named QueueConnectionFactory,
>fails
>> to start the connection. The stack trace is
>>
>> weblogic.jms.common.JMSException: Connection not found
>> at weblogic.jms.dispatcher.InvocableManager.invocableFind(InvocableManager.java:136)
>> at weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:596)
>> at weblogic.jms.dispatcher.DispatcherImpl.dispatchSync(DispatcherImpl.java:153)
>> at weblogic.jms.client.JMSConnection.start(JMSConnection.java:567)
>> at uk.co.concise.payments.event.EventProcessorServiceAsynchBD.(EventProcessorServiceAsynchBD.java:82)
>> at uk.co.concise.payments.state.ejb.ObjectStateServiceXDBean.ejbCreate(ObjectStateServiceXDBean.java:213)
>> at uk.co.concise.payments.state.ejb.ObjectStateService_1th3um_Impl.ejbCreate(ObjectStateService_1th3um_Impl.java:135)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>> at java.lang.reflect.Method.invoke(Method.java:324)
>> at weblogic.ejb20.pool.StatelessSessionPool.createBean(StatelessSessionPool.java:172)
>> at weblogic.ejb20.pool.StatelessSessionPool.getBean(StatelessSessionPool.java:110)
>> at weblogic.ejb20.manager.StatelessManager.preInvoke(StatelessManager.java:140)
>> at weblogic.ejb20.internal.BaseEJBLocalObject.preInvoke(BaseEJBLocalObject.java:229)
>> at weblogic.ejb20.internal.StatelessEJBLocalObject.preInvoke(StatelessEJBLocalObject.java:54)
>> at uk.co.concise.payments.state.ejb.ObjectStateService_1th3um_ELOImpl.createAndGetStateForObject(ObjectStateService_1th3um_ELOImpl.java:273)
>> at uk.co.concise.payments.state.ObjectStateServiceBD.createAndGetStateForObject(ObjectStateServiceBD.java:123)
>> at uk.co.concise.payments.submission.ejb.SubmissionServiceXDBean.createSubmission(SubmissionServiceXDBean.java:92)
>> at uk.co.concise.payments.submission.ejb.SubmissionService_o0dxp8_ELOImpl.createSubmission(SubmissionService_o0dxp8_ELOImpl.java:162)
>> at uk.co.concise.payments.submission.SubmissionServiceBD.createSubmission(SubmissionServiceBD.java:42)
>> at uk.co.concise.payments.submission.webapp.SubmitPaymentFileAction.execute(SubmitPaymentFileAction.java:216)
>> at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:446)
>> at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:266)
>> at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1292)
>> at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:510)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
>> at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1053)
>> at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:387)
>> at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28)
>> at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
>> at uk.co.concise.payments.logon.filter.LogonFilter.doFilter(LogonFilter.java:38)
>> at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
>> at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6316)
>> at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
>> at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
>> at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3622)
>> at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2569)
>> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
>> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
>>
>>
>> Any ideas on what could be wrong
>> thanks
>> jaz
>
-
I am still having problems with wi fi connectivity after I upgraded my computer to os x 10.9.4.
I updated my laptop to 10.9.4, and now my laptop won't continually stay connected to the internet. I will get it to open a page initially, then when I try another page, the browser acts like it's going to load a page, but then just hangs there. When it does connect, it is fast, but more often then not as I'm trying to connect to different websites the page doesn't load at all. I've restarted the router, I've restarted the modem, I've deleted and re-added my network, I've restarted my computer, and I tried to restart in 'safe-mode'.
I had the same problem after the last update, but figured it was the same issue everyone else was having of the computer not reconnecting after sleep. I found a fix, and it seemed to help (although the problem never completely went away), but I can no longer find that solution.
My internet provider stated that all was good on their end, and indeed, I have no problems using wi-fi on my iphone. But, my computer just doesn't want to stay connected enough to surf various sites on the internet.
HELP!!Troubleshooting Wi-Fi issues in OS X
Wireless Connection Problems - Fix
Wireless Connection Problems - Fix (2)
Wireless Connection Problems - Fix (3)
Wireless Connection Problems - Fix (4)
Wireless Diagnostics - About
Also try turning off Bluetooth -
I am having trouble with the initial connection of the apple tv. I have isolated the problem to the cable/connection. My new hdmi cable has a resolution up to 1080p...does the resolution matter?is this the right hdmi cable for the apple tv?
There are only two types of HDMI cables (standard and high speed - listen to all 1.2, 1.3 etc etc nonsense they will try to tell in the store) both types will work with the Apple TV.
The cable may be faulty though, have you got another to try, what exactly is happening. -
I'm having problems with my internet connection after installing OS X Lion. Is this a known problem or just a local problem?
After +/- 10 to 15min my connection is gone.
Does anyone have a sollution?Lots of people are having the same problem, you're not the only one, belieeeeve me.
Just Googling the problem gets you tons of people complaining about the same thing, SOMETHING is up with Lion what wasn't happening with Snow Leopard. i just bought a new Imac and it CAME with Lion, so i started experiencing this internet dropout immediately.
It's been going on for the most of a year it looks like (at least by the dates from the threads i've been reading)
So your best bet is to fiddle with the System Preferences and read what other people have used to make theirs work. i'm doing that myself right now. I already posted a similar thread last night trying to figure out why my connection kept on dropping, i got a reply which linked me to a site. i followed the instructions there, so far so good, but i'm just being cautiously optimistic.
i'm gonna call Apple today and see if they've found anything, though seeing as this is a problem right out of the box there may not be an immediate solution. Good luck hunting for a solution :3
Site:
http://osxdaily.com/2011/11/06/lion-wi-fi-problems-solution-mac/?utm_source=feed burner&utm_medium=feed&utm_campaign=Feed%3A+osxdaily+%28OS+X+Daily%29&utm_conten t=FaceBook -
Connection problems with DI-SERVER 2007 & B1WS from remote machine
Hi,
Can you please help us better understand what the issue is, and how to solve it?
I am seeking to get B1WS working on remote machines.
I have built a small test application, which works fine on the server which also hosts the SQL Server instance and IIS.
When I move the application to another machine, no connection happens, and it always throws this error:
Message:
"Unable to connect to the remote server"
Inner Exception:
"No connection could be made because the target machine actively refused it 127.0.0.1:80"
Error Code:
10061
This configuration works:
Licensing Server: Server A
Database Server: Server B
IIS Server (B1WS): Server B
Running App: Server B
This configuration does not work:
Licensing Server: Server A
Database Server: Server B
IIS Server (B1WS): Server B
Running App: Workstation C
I have checked permissions on the web services folder, and gave Everyone all permissions. The same connection problems persists.
All help is welcome!
Thank you in advance,
MikeDear Michael Gurevich,
Was resolved?
Thanks.
João Paulo -
Problems connecting to a remote OPC server in write mode using CWDataSocket control
Hi.
I have been struggling with an odd feature when trying to connect to a remote OPC server using CWDataSocket control, though I'm not sure if it's a CWDataSocket related problem. But anyway, the following error occurs: "Active: Can't write data." Error number: "-2147467259". Now, when I connect to a local OPC server
and write some data and then again connect to the remote server, no errors occure and reading and writing work fine. The same error occurs when I try the same in LabVIEW. What could be the problem?
No errors occure when I connect to the server with some other OPC client application.
Thanks in advance.
- Asko -The ConnectTo operation (as are all DataSocket operations) is asynchronous. In order for it to complete, you must process Windows messages after calling it and before calling another operation. Is it possible that you are trying to write data before the connection operation is complete?
One easy way to test this would be to put the ConnectTo and the Write in separate control callbacks, cause ConnectTo to be called, wait a while, then cause the Write to be called. Alternatively, you could do something like the following:
dsWrite.ConnectTo txtUrl.Text, cwdsWrite
While Not ((dsWrite.Status = cwdsConnectionActive) Or (dsWrite.Status = cwdsConnectionIdle))
DoEvents
Wend
If this is the problem, then you'll probably want to go with the
second option. In a production system, you should include a timeout in the While loop so that if the connection actually cannot be made, you are not stuck in an infinite loop. -
Im having inconsistent internet connection with my macbookpro 13 inch. But if I turn off my wifi and turnit on again, it will come back again. Anyone had this problem?
Sig,
Thanks for the advice. I finally tried a solution after doing nothing. LoL. What I did do was change the channel the router was on from 9 to 7. I think I've done something like this in the past when I had slow internet and that worked out well too. I thought that would help and so far so good. Not an interruption so far but we shall see. To the guy or girl who expressed that they had the same problem as me I would try changing the channel of your router like I did. I will monitor the situation and see if it totally solved my problem or not and keep this thread updated. Thanks people -
I'm having problems maintaining a VPN connection on iPad. Any thoughts?
I'm having problems maintaining a VPN connection on iPad. Any thoughts?
Sorry to be vague but just drops out. Often citing insufficient bandwidth. However, I don't have the same problems using a 3g iPhone on the same wifi connection.
-
Just got Mac book pro. I can't connect to office remotely thru the remote window. My office is window based and I have no problem connecting while at the office thru the server but cannot at home. Any help would be appreciated!
This what my IT replied with:
That teh MacBook cannot connect with RWW because it requires Active-X to connect. That MAc browsers (Safari) do not use Active-X but only Windows (IE) uses Active-X control.
It would seem to me that there must be a way around this. Any help?
Thanks, -
I having problem keep ask me connect to itunes......can't restore...keep show there is no sim card installed in the iphone you are attempting to activate.....how?
ITUNES show keep show there is no sim card installed in the iphone you are attempting to activate.....how?rajafromcalifornia wrote:
how can i get rid of this error There is no sim card installed in the phone u are attempting to activate please disconnect and a sim card in the phone please help me and my iphone cannot go to menu display can u help me please
You cannot active a phone if it does not have a SIM card in it. Period. End of discussion.
If you get this error and it has a SIM card in the phone then either the SIM card is defective or the phone is defective. Get a new SIM card and try again. If the problem occurs with the new SIM card the phone needs to be repaired.
Maybe you are looking for
-
Best modem to use with Macbook pro
I have a new Macbook Pro which won't stay connected to the internet. Apple don' t have the answer. I have noticed it is stable in other locations so I suspect it is not compatible issue with my wireless modem. Can anyone suggest a modem which is stab
-
How Do I Backup to Adobe's Online Storage
I purchased the $20 option to backup files online with Adobe (although, strangely, it still says I only have 2 gig instead of the 20 I bought) but am unable to find any option in the Organizer menu that lets me backup files except to CD, DVD, or ext
-
Firefox starts up in different tab with a different website
Occasionally Firefox starts up in a tab and website that are different from the last time I closed it. For example, last night I closed it facing the second tab with a given website, and then today, when I started it up, I was on the fifth tab, with
-
CAn an you please help me? [email address deleted]
-
Reg: Costing details for PP point of view
Dear SAP Gurus I am balaji Now i am in post go live support project For our client, we recommend Repetitive manufacturing process Order : Planned order consumption thro back flush MFBF. Costing : We have parameter, formulaes, primary and secondary co