Losing connection to TIBCO JMS Server

I'm having a very strange problem with a Message Driven Bean in WebLogic. We're using a TIBCO JMS Server so I setup a Foreign JMS Server in Weblogic for my MDB. Seems to work fine and receive messages for awhile but then every morning at about the same time, I lose the connection. There are a number of other people connected to that TIBCO server for days/weeks with no problem, just me!
          I thought maybe the problem was with WebLogic so I wrote a main() method for my MDB which manually connects to the server/queue and calls setMessageListener(this). Same behavior: works overnight just fine and then disconnects at about 9:00am. No exception from JMS or anything, it just disconnects. I even set a JMS ExceptionListener but it never gets called.
          Has anyone had this bizarre problem?
          Thanks,
          - Ian

Did you tried running that main program on the same machine where Tibco is running ?

Similar Messages

Setting the JMS client-id on a Tibco JMS server

Dear,
We're running quite a bit of interfaces that connect to a Tibco JMS server.
The Tibco team is suggesting we use client-id's to identify ourselves as the consumer of a particular queue. However I fail to find the parameters I require to send the client-id with my call in the JMS Sender/Receiver Adapter .
Has anyone had any experience with this?
Kr,
Frederik-Jan.

Dear,
I don't see how this is relevant to connecting
- From PI
- To Tibco EMS
I don't need a tool for viewing a queue. When I view the queue, I see that the client-id is left empty. What I need is a parameter/setting for my adapter/communication channel so that I can set the client-id.
Kr,
Frederik-Jan.

How toset JMS_TIBCO_COMPRESS to true ,connecting to tibco jms queue frmBPEl

Hi ,
I m tryingto connect to tibco jms queue from BPEL .How can i set JMS_TIBCO_COMPRESS to true before placing message on the queue.
I am able to send and receive the messages from the queue but I m not able to compress it

Did you figure out a solution for this? I have the same need and I'm investigating using JAAS configuration to accomplish.

Connecting to Tibco JMS through SSL

Hi,
How to we connect to a Tibco JMS Provider using SSL through OAS 10.1.3. Is there a way to configure OAS to use SSL when connecting to Tibco JMS Provider.
Thanks

Did you figure out a solution for this? I have the same need and I'm investigating using JAAS configuration to accomplish.

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

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

Weblogic 10.3 not suporting for MDB to connect remote Weblogic JMS server

Hi,
I have a problem with MDB deployed on Weblogic 10.3.It's simple MDB which is communicating with remote weblogic JMS server. I am getting below exception. could some one help how to resolve this issue.
<Apr 14, 2009 11:28:52 AM PDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: ReceiverFromDocumentum is unable to con
nect to the JMS destination: FMAContractOutboundQueue. The Error was:
[EJB:011013]The Message-Driven EJB attempted to connect to the JMS connection factory with the JNDI name: FMAConnectionFacto
ry. However, the object with the JNDI name: FMAConnectionFactory is not a JMS connection factory. NestedException Message is
:weblogic.jms.client.JMSConnectionFactory cannot be cast to javax.jms.XAConnectionFactory>
-Sreekanth

I recall that this particular warning message is sometimes misleading about the root cause of the problem, an issue that I think has been fixed in a patch. The actual problem can be various:
* The MDB is configured to be transactional, the connection factory exists, but the connection factory isn't configured to be "XA enabled". (I think this is the most likely problem).
* The connection factory doesn't exist.
* The object in JNDI with the specified connection factory name isn't actually a connection factory.
* The dest object in JNDI with the specified name isn't actually a javax.jms.Destination
Note that its unusual to configure the connection factory name for an MDB that consumes from WebLogic JMS. The default name iis usually sufficient unless custom tuning is required on the connection factory. See the MDB section of the EJB developer guide for more information.
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
 >

MDB connecting to Foreign JMS server in WL8.1

Hello,
 I have this problem that I am hoping someone can help me with. There is a
 MDB deployed in a local WL8.1 that is trying to connect to a Foreign JMS
 Server which is also a WL8.1 running in a remote server. This MDB is
 attempting to subscribe to a topic hosted by that foreign server. In the
 local WL8.1 I created a Foreign JMS Server via the adminconsole and mapped
 the connection factory as well as destinations to the Foreign JMS Server.
 The MDB (via its deployment descriptor) only refers to the local JNDI names
 of the ConnectionFactory and Topic. Here are the scenarios concerning
 security:
 1) When security is turned off (user is in group everyone) everything works
 fine. Messages published to the foreign Topic are received by the MDB in
 the local WL8.1 server and processed.
 2) When a security policy is applied to the Topic (via the remote
 adminconsole), the MDB in the local server gets a 'permission denied'. I
 now have to get around this by defining a principle for the MDB to run as
 and to map the credentials of this principle to that of the user in the
 remote environment with access permissions to the Topic.
 3) When I specify the security identity of my MDB, its JNDI lookup of the
 Topic fails with 'not found'.
 4) Even when the security policy in the remote server is reverted back to
 'everyone' (effectively turning security off) but leaving the MDB running as
 the security principle, it still cannot find the Topic.
 I hope this is something that people have seen and dealt with before.
 Thanks for any and all help anyone can provide. I have also included the
 deployment descriptors for this MDB:
 <ejb-jar>
 <enterprise-beans>
 <message-driven>
 <ejb-name>MDB</ejb-name>
 <ejb-class>sample.class.MDB</ejb-class>
 <transaction-type>Container</transaction-type>
 <message-driven-destination>
 <destination-type>javax.jms.Topic</destination-type>
 </message-driven-destination>
 <security-identity>
 <run-as>
 <role-name>OutsideJMSUser</role-name>
 </run-as>
 </security-identity>
 </message-driven>
 </enterprise-beans>
 <assembly-descriptor>
 <security-role>
 <role-name>OutsideJMSUser</role-name>
 </security-role>
 </assembly-descriptor>
 </ejb-jar>
 <weblogic-ejb-jar>
 <weblogic-enterprise-bean>
 <ejb-name>MDB</ejb-name>
 <message-driven-descriptor>
 <pool>
 <initial-beans-in-free-pool>1</initial-beans-in-free-pool>
 </pool>
 <destination-jndi-name>ForeignTopic</destination-jndi-name>
 <connection-factory-jndi-name>ForeignConnectionFactory</connection-factory-j
 ndi-name>
 </message-driven-descriptor>
 <jndi-name>MDB</jndi-name>
 </weblogic-enterprise-bean>
 <security-role-assignment>
 <role-name>OutsideJMSUser</role-name>
 <principal-name>OutsideJMSUser</principal-name>
 </security-role-assignment>
 </weblogic-ejb-jar>


Thanks for the suggestion Greg. I have enabled trust between the two
 domains and that has certainly cut down the variations of SecurityExceptions
 that I get. Now I am consistently only getting a JMSSecurityException with
 a access denied to the topic. I believe I have the credential mapped
 correctly between the run-as local user and the remote authorized user.
 Unfortunately the exception does not specify what username was rejected, it
 would have been useful in determining the next debugging step to take.
 I think you're right, I should engage the security forum for this. Thanks
 again for the help.
 "Greg Brail" <[email protected]> wrote in message
 news:[email protected]...
 > Hmm. The security people (on weblogic.developer.interest.security) might
 > have to help you here, too. When you set the "runAs" identity for the MDB,
 > it's doing everything, including the JNDI lookup, under that identity. So
 if
 > that identity is one that's recognized by the remote domain, then you
 should
 > be OK. One way to make your local identity recognized by the remote domain
 > is to make your domains trusted, but you may wish not to do that.
 >
 > greg
 >
 > "Steve Chan" <[email protected]> wrote in message
 > news:[email protected]...
 > > Hello,
 > >
 > > I have this problem that I am hoping someone can help me with. There is
 a
 > > MDB deployed in a local WL8.1 that is trying to connect to a Foreign JMS
 > > Server which is also a WL8.1 running in a remote server. This MDB is
 > > attempting to subscribe to a topic hosted by that foreign server. In
 the
 > > local WL8.1 I created a Foreign JMS Server via the adminconsole and
 mapped
 > > the connection factory as well as destinations to the Foreign JMS
 Server.
 > > The MDB (via its deployment descriptor) only refers to the local JNDI
 > names
 > > of the ConnectionFactory and Topic. Here are the scenarios concerning
 > > security:
 > >
 > > 1) When security is turned off (user is in group everyone) everything
 > works
 > > fine. Messages published to the foreign Topic are received by the MDB
 in
 > > the local WL8.1 server and processed.
 > >
 > > 2) When a security policy is applied to the Topic (via the remote
 > > adminconsole), the MDB in the local server gets a 'permission denied'.
 I
 > > now have to get around this by defining a principle for the MDB to run
 as
 > > and to map the credentials of this principle to that of the user in the
 > > remote environment with access permissions to the Topic.
 > >
 > > 3) When I specify the security identity of my MDB, its JNDI lookup of
 the
 > > Topic fails with 'not found'.
 > >
 > > 4) Even when the security policy in the remote server is reverted back
 to
 > > 'everyone' (effectively turning security off) but leaving the MDB
 running
 > as
 > > the security principle, it still cannot find the Topic.
 > >
 > > I hope this is something that people have seen and dealt with before.
 > > Thanks for any and all help anyone can provide. I have also included
 the
 > > deployment descriptors for this MDB:
 > >
 > > <ejb-jar>
 > > <enterprise-beans>
 > > <message-driven>
 > > <ejb-name>MDB</ejb-name>
 > > <ejb-class>sample.class.MDB</ejb-class>
 > > <transaction-type>Container</transaction-type>
 > > <message-driven-destination>
 > > <destination-type>javax.jms.Topic</destination-type>
 > > </message-driven-destination>
 > > <security-identity>
 > > <run-as>
 > > <role-name>OutsideJMSUser</role-name>
 > > </run-as>
 > > </security-identity>
 > > </message-driven>
 > > </enterprise-beans>
 > >
 > > <assembly-descriptor>
 > > <security-role>
 > > <role-name>OutsideJMSUser</role-name>
 > > </security-role>
 > > </assembly-descriptor>
 > >
 > > </ejb-jar>
 > >
 > > <weblogic-ejb-jar>
 > > <weblogic-enterprise-bean>
 > > <ejb-name>MDB</ejb-name>
 > > <message-driven-descriptor>
 > > <pool>
 > > <initial-beans-in-free-pool>1</initial-beans-in-free-pool>
 > > </pool>
 > > <destination-jndi-name>ForeignTopic</destination-jndi-name>
 > >
 > >
 >
 <connection-factory-jndi-name>ForeignConnectionFactory</connection-factory-j
 > > ndi-name>
 > > </message-driven-descriptor>
 > > <jndi-name>MDB</jndi-name>
 > > </weblogic-enterprise-bean>
 > >
 > > <security-role-assignment>
 > > <role-name>OutsideJMSUser</role-name>
 > > <principal-name>OutsideJMSUser</principal-name>
 > > </security-role-assignment>
 > >
 > > </weblogic-ejb-jar>
 > >
 > >
 >
 >

Flash Players Crash Due Losing Connection To The Internet Server , Why is that Happening ?

I have been trying to install these Flash Players ,but at the end of the downloading mode it loses connection to the Internet Server and crashes the install . It is very frustrating and I am giving up . Adobe Reader does the same thing , what is there to do ? I have Windows 8 , the Internet Explorer and Chrome . Still nothing works at all . If nothing gets straighten out here with this Flash Player and Adobe Reader by the end of the Holidays then I am going to take my computer and have it cleaned out . Because I've had it with Flash Players and I am tired of it all .

Download the Adobe Flash Player FULL offline installer directly by clicking one of the following links.
Flash Player for ActiveX (Internet Explorer)
Flash Player Plug-in (All other browsers)
Download the Adobe Reader FULL offline installer here: http://get.adobe.com/reader/enterprise/
Those require NO internet connection to install once you've downloaded them.

How to connect to Tibco JMS

Hi
I am looking for sample appliction, where a JSP tries to post a request to remote TIBCO JMS destination.
An application tier MDB consumes the message and prints the payload information.
We will we be configuring the remote destination name. Note the application is to be deployed in OC4J.
Pointers in this regard will be great.
Thanks
sunder

Don't have a sample application, but I can point you at the documentation for the Generic JMS Resource Adapter, which is our JCA1.5 adapter for interoperating with 3rd party JMS providers.
http://download.oracle.com/docs/cd/B32110_01/web.1013/b28958/jms.htm#CHDJDHCA
-steve-

Connecting to remote JMS server

I am running Flex2/FDS using Tomcat, and want to create a
Producer/Consumer to message via a JMS application (Sonic ESB) on a
different host. We have successfully done this with Flex 1.5 using
a java servlet, but I cannot get it to work via Flex2/FDS
messaging.
Here are (I think) the essentials:
We have the sonic jars on the server available to FDS, I also
put them in tomcat's common/lib directory
in mxml, I have:
<Producer id="p" destination="sonicDestination" />
in messaging-config.xml I have (relevant part):
<destination id="sonicDestination" >
<adapter ref="jms"/>
<channels>
<channel ref="my-rtmp">
</channel>
<properties>
<jms>
<destination-type>Queue</destination-type>
<message-type>javax.jms.TextMessage</message-type>
<connection-factory>java:comp/env/jms/connectionFactory</connection-factory>
<destination-jndi-name>java:comp/env/sonicDestination</destination-jndi-name>
<destination-name>targetSonicQueue</destination-name>
<delivery-mode>NON-PERSISTENT</delivery-mode>
<acknowledge-mode>AUTO_ACKNOWLEDGE</acknowledge-mode>
<transacted-sessions>false</transacted-sessions>
</jms>
</properties>
</destination>
in web-xml I have:
<resource-ref>
<res-ref-name>jms/connectionFactory</res-ref-name>
<res-type>javax.jms.ConnectionFactory</res-type>
<res-auth>Container</res-auth>
<res-sharing-scope>Shareable</res-sharing-scope>
</resource-ref>
<resource-ref>
<res-ref-name>sonicDestination</res-ref-name>
<res-type>javax.jms.Destination</res-type>
<res-auth>Container</res-auth>
<res-sharing-scope>Shareable</res-sharing-scope>
</resource-ref>
AND in context.xml I have:
<Resource name="jms/connectionFactory" auth="container"
type="progress.message.jclient.ConnectionFactory"
brokerURL="tcp:_ipaddress_:2506"
username="_username_" password="_password_"
defaultUser="_username_" defaultPassword="_password_"
/>
<Resource name="sonicDestination" auth="container"
type="progress.message.jclient.Queue"
queueName="targetSonicQueue" />
... this all seems to deploy OK... in the mxml... when I
create a message and try to have the producer send it...
I get an error on the server (which is passed back as an
exception to the client)... the relevant part of all that is:
javax.naming.NamingException: Cannot create resource instance
at
org.apache.naming.factory.ResourceFactory.getObjectInstance()
at javax.naming.spi.NamingManager.getObjectInstance()
at org.apache.naming.NamingContext.lookup()
_several layers of calling NamingContext_
at javax.naming.InitialContext.lookup()
at
flex.messaging.services.messaging.adapters.JMSProxy.getDestination()
at
flex.messaging.services.messaging.adapters.JMSQueueProducer.start()
..._more
It looks to me like it is finding Tomcat's JNDI service and
getting to the point where its trying to instantiate the
connectionFactory or the sonicDestination...
and that's failing...
do you have or know of someone who knows how to connect to
from Flex 2.0.1 / FDS via Tomcat to a Sonic MQ (7.0) server on
another host ?
Thanx much

My current code is:
env.setProperty(Context.PROVIDER_URL, "iiop://localhost:2809");
env.setProperty(Context.INITIAL_CONTEXT_FACTORY, "com.ibm.websphere.naming.WsnInitialContextFactory");
InitialContext initCtx = new InitialContext(env);
System.out.println("Getting connection factory....");
// Finding the WAS QueueConnectionFactory
javax.jms.ConnectionFactory qcf = (javax.jms.ConnectionFactory) initCtx.lookup(JMSCF_JNDI_NAME);
System.out.println("qcf="+qcf);
// Finding the Queue Destination
Destination q = (Destination) initCtx.lookup(JMSQ_JNDI_NAME);
I am getting exception as:
Oct 26, 2005 4:10:11 PM com.ibm.ws.naming.java.javaURLContextFactory
SEVERE: javaAccessorNotSet
javax.naming.ConfigurationException: Name space accessor for the java: name space has not been set. Possible cause is that the user is specifying a java: URL name in a JNDI Context method call but is not running in a J2EE client or server environment.
at com.ibm.ws.naming.java.javaURLContextFactory.isNameSpaceAccessable(javaURLContextFactory.java:98)
at com.ibm.ws.naming.urlbase.UrlContextFactory.getObjectInstance(UrlContextFactory.java:73)
at javax.naming.spi.NamingManager.getURLObject(NamingManager.java:579)
at javax.naming.spi.NamingManager.getURLContext(NamingManager.java:528)
at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:275)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at sender.Main.main(Main.java:29)

Trying to connect client to JMS server

Hello,
I'm trying to do a client program that reads messages from a queue placed in another machine.
The queue is running in a machine using SunONE MQ 3.0, and broker is running in port 7979. I'm using a File System Object Store on this machine.
Is it possible to create a client program (on a different machine) that listens to this queue? I know it's possible if the JMS uses LDAP Object Store, but I don't know if that's possible when we use File System Object Store.
In case it's possible, which properties should I use to initialize InitialContext() and do the context.lookup()?
Thanks

You can connect to a remote broker using either the
LDAP Object Store or the File System Object Store.
You will find information in both the Develper's Guide:
http://docs.sun.com/source/817-0355-10/adminobj.html#34151
and Administrator Guide about the attributes you can use
with the File system Object store:
http://docs.sun.com/source/817-0354-10/adminobj.html#16293

Deploying MDB on WebLogic server 8.1 (SP2) with Tibco JMS

Hi,
 I am currently facing problems to deploy and run my MDB on weblogic connecting it to Tibco JMS as the foreign jms server.
 
 My ejb-jar.xml:
 
 <message-driven>
 <ejb-name>DeAMMsgFactors</ejb-name>
 <ejb-class>com.db.deam.mdb.DeAMMsgFactors</ejb-class>
 <transaction-type>Container</transaction-type>
 <message-driven-destination>
 <destination-type>javax.jms.Topic</destination-type>
 </message-driven-destination>
 </message-driven>
 </enterprise-beans>
 <assembly-descriptor>
 <security-role>
 <role-name>soiadmin</role-name>
 </security-role>
 </assembly-descriptor>
 
 weblogic-ejb-jar.xml:
 
 <weblogic-enterprise-bean>
 <ejb-name>DeAMMsgFactors</ejb-name>
 <message-driven-descriptor>
 <pool>
 <max-beans-in-free-pool>20</max-beans-in-free-pool>
 <initial-beans-in-free-pool>10</initial-beans-in-free-pool>
 </pool>
 <destination-jndi-name>WLFactorsTopic</destination-jndi-name>
 <connection-factory-jndi-name>WLFactorsCF</connection-factory-jndi-name>
 <jms-polling-interval-seconds>10</jms-polling-interval-seconds>
 </message-driven-descriptor>
 <transaction-descriptor>
 <trans-timeout-seconds>100000</trans-timeout-seconds>
 </transaction-descriptor>
 </weblogic-enterprise-bean>
 <security-role-assignment>
 <role-name>soiadmin</role-name>
 <principal-name>jmsusername</principal-name>
 </security-role-assignment>
 
 Error:
 weblogic.ejb20.WLDeploymentException: [EJB:011014]The Message-Driven EJB failed while creating a JMS Connection. The err
 or was:
 javax.jms.JMSSecurityException: invalid name or password.
 javax.jms.JMSSecurityException: invalid name or password
 at com.tibco.tibjms.Tibjmsx.buildException(Tibjmsx.java:395)
 at com.tibco.tibjms.TibjmsConnection._create(TibjmsConnection.java:581)
 at com.tibco.tibjms.TibjmsConnection.<init>(TibjmsConnection.java:1743)
 at com.tibco.tibjms.TibjmsTopicConnection.<init>(TibjmsTopicConnection.java:35)
 at com.tibco.tibjms.TibjmsxCFImpl._createImpl(TibjmsxCFImpl.java:92)
 at com.tibco.tibjms.TibjmsxCFImpl._createConnection(TibjmsxCFImpl.java:121)
 at com.tibco.tibjms.TibjmsTopicConnectionFactory.createTopicConnection(TibjmsTopicConnectionFactory.java:66)
 at weblogic.ejb20.internal.JMSConnectionPoller.getConnection(JMSConnectionPoller.java:607)
 at weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectionPoller.java:1783)
 at weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller.java:1087)
 at weblogic.ejb20.internal.JMSConnectionPoller.trigger(JMSConnectionPoller.java:970)
 at weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:243)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
 at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:229)
 at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:223)
 at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:50)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
 at weblogic.ejb20.internal.JMSConnectionPoller.getConnection(JMSConnectionPoller.java:638)
 at weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectionPoller.java:1783)
 at weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller.java:1087)
 at weblogic.ejb20.internal.JMSConnectionPoller.trigger(JMSConnectionPoller.java:970)
 at weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:243)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
 at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:229)
 at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:223)
 at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:50)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
 [JMSConnectionPoller] : ** Connect attempt for: WLFactorsTopic was: unsuccessful
 
 Any help would be appreciated.
 
 Thanks, 
 Kiran Kumar MV.

I was able to use MDB to receive msg from a Tibco JMS queue. This is what you have to do: using WL console,
 - set up a foreign JMS Server. Make sure you specify the following correctly: jndi initial context factory (tibjms class), tibjms server url, username/password
 - create a foreign connection factory (if you are using CMT, make sure you create a XA compliant connection factory in Tibco JMS server). It seems that you have to specify URL again when creating XA connection factory in Tibjms.
 - create a foreign destination (queue/topic)
 In ejb-jar.xml and weblogic-ejb-jar.xml,
 - use resource-ref (wrapper) to specify the foreign connection factory
 - use resource-env-ref to specify the foreign destination.
 - In MDB ejb-jar.xml, specify destination-jndi-name and connection-factory-jndi-name.
 See Message Driven Beans chapter in Programming WebLogic EJB doc.
 Good luck.

ORA-25228 error occurs when Foreign JMS Server connecting to the Oracle AQ

Hi,
I configure of a Foreign JMS Server that uses the Oracle JDBC Driver to connect to the AQ Topic. I use OSB messaging proxy service as a JMS client to connect the Foreign JMS Server. After the launch, I get the following error:
####<Jan 30, 2013 4:51:49 AM MSK> <Error> <EJB> <EPRUSARW0520> <osb_server1> <RequestEJB7826682746890400115XX35047bed.13c85602eea.X7f53> <<anonymous>> <> <0000Jm8w2Es6qI_5xRh8iW1H1sMk0001sD> <1359507109078> <BEA-010079> <An error occurred while attempting to receive a message from JMS for processing by a message-driven bean: oracle.jms.AQjmsException: JMS-120: Dequeue failed
Nested exception: java.sql.SQLException: ORA-00604: error occurred at recursive SQL level 1
ORA-06502: PL/SQL: numeric or value error
ORA-06512: at line 11
ORA-25228: timeout or end-of-fetch during message dequeue from MDM.ALL_NSI
The exception is : oracle.jms.AQjmsException: JMS-120: Dequeue failed
 at oracle.jms.AQjmsError.throwEx(AQjmsError.java:315)
 at oracle.jms.AQjmsConsumer.jdbcDequeue(AQjmsConsumer.java:1620)
 at oracle.jms.AQjmsConsumer.receiveFromAQ(AQjmsConsumer.java:1035)
 at oracle.jms.AQjmsConsumer.receiveFromAQ(AQjmsConsumer.java:960)
 at oracle.jms.AQjmsConsumer.receiveFromAQ(AQjmsConsumer.java:938)
 at oracle.jms.AQjmsConsumer.receive(AQjmsConsumer.java:790)
 at weblogic.deployment.jms.WrappedMessageConsumer.receive(WrappedMessageConsumer.java:201)
 at weblogic.ejb.container.internal.JMSMessagePoller$1.run(JMSMessagePoller.java:262)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
 at weblogic.ejb.container.internal.JMSConnectionPoller.doPrivilegedJMSAction(JMSConnectionPoller.java:2752)
 at weblogic.ejb.container.internal.JMSMessagePoller.processOneMessage(JMSMessagePoller.java:257)
 at weblogic.ejb.container.internal.JMSMessagePoller.pollContinuously(JMSMessagePoller.java:351)
 at weblogic.ejb.container.internal.JMSMessagePoller.pollForParent(JMSMessagePoller.java:483)
 at weblogic.ejb.container.internal.JMSMessagePoller.run(JMSMessagePoller.java:499)
 at java.lang.Thread.run(Thread.java:722)
Caused by: java.sql.SQLException: ORA-00604: error occurred at recursive SQL level 1
ORA-06502: PL/SQL: numeric or value error
ORA-06512: at line 11
ORA-25228: timeout or end-of-fetch during message dequeue from MDM.ALL_NSI
 at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:462)
 at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:397)
 at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389)
 at oracle.jdbc.driver.T4Caqdq.processError(T4Caqdq.java:497)
 at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:481)
 at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:205)
 at oracle.jdbc.driver.T4Caqdq.doOAQDQ(T4Caqdq.java:183)
 at oracle.jdbc.driver.T4CConnection.doDequeue(T4CConnection.java:4704)
 at oracle.jdbc.driver.PhysicalConnection.dequeue(PhysicalConnection.java:17863)
 at oracle.jdbc.driver.PhysicalConnection.dequeue(PhysicalConnection.java:17949)
 at oracle.jdbc.OracleConnectionWrapper.dequeue(OracleConnectionWrapper.java:1624)
 at weblogic.jdbc.wrapper.XAConnection_oracle_jdbc_driver_LogicalConnection.dequeue(Unknown Source)
 at weblogic.jdbc.wrapper.JTAConnection_weblogic_jdbc_wrapper_XAConnection_oracle_jdbc_driver_LogicalConnection.dequeue(Unknown Source)
 at oracle.jms.AQjmsConsumer.jdbcConnectionDequeueCheck25242(AQjmsConsumer.java:1713)
 at oracle.jms.AQjmsConsumer.jdbcDequeue(AQjmsConsumer.java:1295)
 ... 13 moreHowever, when I put message to AQ topic, the OSB proxy receives and processes it. But SQLException occurs every five seconds and pollute logs.
Request help to resolve this.
Thanks in advance.
Regards
Alexander.

Maybe this can help: http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::p11_question_id:4018285967344

Exception when trying to Connect to JMS Server Remotely

Hi,
I get the following error when i am trying to connect to a JMS server over the network. Please help.
Aug 7, 2009 12:58:10 PM com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl <init>
WARNING: "IOP00410201: (COMM_FAILURE) Connection failure: socketType: IIOP_CLEAR_TEXT; hostname: localhost; port: 3700"
org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 201 completed: No
at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2690)
at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2711)
at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:261)
at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:274)
at com.sun.corba.ee.impl.transport.SocketOrChannelContactInfoImpl.createConnection(SocketOrChannelContactInfoImp
l.java:130)
at com.sun.corba.ee.impl.protocol.CorbaClientRequestDispatcherImpl.beginRequest(CorbaClientRequestDispatcherImpl
.java:192)
at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.request(CorbaClientDelegateImpl.java:181)
at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.is_a(CorbaClientDelegateImpl.java:325)
at org.omg.CORBA.portable.ObjectImpl._is_a(ObjectImpl.java:112)
at org.omg.CosNaming.NamingContextHelper.narrow(NamingContextHelper.java:69)
at com.sun.enterprise.naming.SerialContext.narrowProvider(SerialContext.java:127)
at com.sun.enterprise.naming.SerialContext.getProvider(SerialContext.java:182)
at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:339)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at com.splwg.mpl.server.jms.JNDIJMSConnectionFactoryFactory.getConnectionFactory(JNDIJMSConnectionFactoryFactory
.java:56)
at com.splwg.mpl.server.jms.JMSUtilImpl.getConnectionFactory(JMSUtilImpl.java:75)
at com.splwg.mpl.jms.queue.JMSSender.init(JMSSender.java:80)
at com.splwg.mpl.sending.NewSenderManager.init(NewSenderManager.java:108)
at com.splwg.mpl.sending.SameThreadSendingManager.initSenderManager(SameThreadSendingManager.java:353)
at com.splwg.mpl.sending.SameThreadSendingManager.init(SameThreadSendingManager.java:154)
at com.splwg.mpl.server.async.AsyncServer.init(AsyncServer.java:193)
at com.splwg.mpl.server.MPLServer.init(MPLServer.java:386)
at com.splwg.mpl.server.MPLServer.run(MPLServer.java:547)
at com.splwg.mpl.server.MPLServer.runMPL(MPLServer.java:535)
at com.splwg.mpl.server.MPLServer.main(MPLServer.java:524)
Caused by: java.lang.RuntimeException: java.net.ConnectException: Connection refused: connect
at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:347)
at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:244)
... 22 more
Caused by: java.net.ConnectException: Connection refused: connect
at sun.nio.ch.Net.connect(Native Method)
at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:464)
at com.sun.corba.ee.impl.orbutil.ORBUtility.openSocketChannel(ORBUtility.java:105)
at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:332)
... 23 more
Aug 7, 2009 12:58:16 PM com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl <init>
WARNING: "IOP00410201: (COMM_FAILURE) Connection failure: socketType: IIOP_CLEAR_TEXT; hostname: localhost; port: 3700"
org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 201 completed: No
at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2690)
at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2711)
at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:261)
at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:274)
at com.sun.corba.ee.impl.transport.SocketOrChannelContactInfoImpl.createConnection(SocketOrChannelContactInfoImp
l.java:130)
at com.sun.corba.ee.impl.protocol.CorbaClientRequestDispatcherImpl.beginRequest(CorbaClientRequestDispatcherImpl
.java:192)
at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.request(CorbaClientDelegateImpl.java:181)
at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.is_a(CorbaClientDelegateImpl.java:325)
at org.omg.CORBA.portable.ObjectImpl._is_a(ObjectImpl.java:112)
at org.omg.CosNaming.NamingContextHelper.narrow(NamingContextHelper.java:69)
at com.sun.enterprise.naming.SerialContext.narrowProvider(SerialContext.java:127)
at com.sun.enterprise.naming.SerialContext.getProvider(SerialContext.java:182)
at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:339)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at com.splwg.mpl.server.jms.JNDIJMSConnectionFactoryFactory.getConnectionFactory(JNDIJMSConnectionFactoryFactory
.java:56)
at com.splwg.mpl.server.jms.JMSUtilImpl.getConnectionFactory(JMSUtilImpl.java:75)
at com.splwg.mpl.jms.queue.JMSSender.init(JMSSender.java:80)
at com.splwg.mpl.sending.NewSenderManager.init(NewSenderManager.java:108)
at com.splwg.mpl.sending.SameThreadSendingManager.initSenderManager(SameThreadSendingManager.java:353)
at com.splwg.mpl.sending.SameThreadSendingManager.init(SameThreadSendingManager.java:154)
at com.splwg.mpl.server.async.AsyncServer.init(AsyncServer.java:193)
at com.splwg.mpl.server.MPLServer.init(MPLServer.java:386)
at com.splwg.mpl.server.MPLServer.run(MPLServer.java:547)
at com.splwg.mpl.server.MPLServer.runMPL(MPLServer.java:535)
at com.splwg.mpl.server.MPLServer.main(MPLServer.java:524)
Caused by: java.lang.RuntimeException: java.net.ConnectException: Connection refused: connect
at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:347)
at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:244)
... 22 more
Caused by: java.net.ConnectException: Connection refused: connect
at sun.nio.ch.Net.connect(Native Method)
at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:464)
at com.sun.corba.ee.impl.orbutil.ORBUtility.openSocketChannel(ORBUtility.java:105)
at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:332)
... 23 more

The googleapi.jar contains copies of some javamail classes. Here a few I found in my output:
javax.mail.event.MessageCountListener from googleapi.jar
javax.mail.Session from googleapi.jar
javax.mail.MessagingException from googleapi.jar
javax.mail.NoSuchProviderException from googleapi.jar
This particular google api is the old SOAP google service that is no longer allowing new registrations, but still has support for existing API key holders, like me :-). Thought this might be a common jar in most libraries, so worth mentioning.
Don't forget, you can debug your loaded classes with java -verbose MyApp to find those rogue libraries.

Losing connection to TIBCO JMS Server

Similar Messages

Maybe you are looking for