SJSAS 2005Q1 JMS ConnectionFactory error

Hi all,
I am finally very close to getting a test JMS Topic connection working, but I am running into the issue with Root exceptions when trying to provide it with a INITIAL_CONTEXT_FACTORY. The SJSAS server is located on a different computer.
My question is, what values should I provide to
INITIAL_CONTEXT_FACTORY, and
PROVIDER_URL
I have tried all suggestions that were on this board, but none were specific to SJSAS and didn't work... I either got crazy messages ending with "Maybe" or a Root exception with the class.
Thanks for your help.

The solution can be found in this post:
http://forum.java.sun.com/thread.jspa?threadID=494092&tstart=0

Similar Messages

Unable to resolve 'mslv.oms.oms1.internal.jms.ConnectionFactory'

Hello,
I hope I am posting this in the right place, if not please forgiv and point me to the right place.
Yesterday we did a live upgrade on a system that is running WebLogic 9.2, OSM 6.3.1 and Oracle DB 10.2.0.2, those applications are on a seperate system slice, we did a complete upgrade from Solaris 10/9 (update 6) to the latest Solaris 8/11 (update 10), on SPARC. After the upgrade everything was working and applications are able to start, but weblogic server is spewing the following error message:
<Aug 1, 2012 12:03:58 PM CEST> <Error> <oms.core> <600022> <EJB Create exception thrown while creating object=EventDispatcherEJB.>
<01-Aug-2012 12:03:58,982 CEST PM> <ERROR> <poller.a> <Timer-4> <Failed to process events>
java.rmi.RemoteException: Error in ejbCreate:; nested exception is:
javax.ejb.CreateException: Unable to resolve 'mslv.oms.oms1.internal.jms.ConnectionFactory'. Resolved 'mslv.oms.oms1.internal.jms'
at weblogic.ejb.container.internal.EJBRuntimeUtils.throwRemoteException(EJBRuntimeUtils.java:95)
at weblogic.ejb.container.internal.BaseEJBObject.handleSystemException(BaseEJBObject.java:724)
at weblogic.ejb.container.internal.BaseEJBObject.handleSystemException(BaseEJBObject.java:681)
at weblogic.ejb.container.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:220)
at weblogic.ejb.container.internal.StatelessEJBObject.preInvoke(StatelessEJBObject.java:64)
at com.mslv.oms.eventengine.EventDispatcher_86q3j1_EOImpl.processTimeout(EventDispatcher_86q3j1_EOImpl.java:485)
at com.mslv.oms.poller.a.handleNotification(Unknown Source)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor$ListenerWrapper.handleNotification(DefaultMBeanServerInterceptor.java:1652)
at javax.management.NotificationBroadcasterSupport.handleNotification(NotificationBroadcasterSupport.java:221)
at javax.management.NotificationBroadcasterSupport.sendNotification(NotificationBroadcasterSupport.java:184)
at javax.management.timer.Timer.sendNotification(Timer.java:1295)
at javax.management.timer.Timer.notifyAlarmClock(Timer.java:1264)
at javax.management.timer.TimerAlarmClock.run(Timer.java:1347)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
we went back and activated Solaris update 8, and we still got that problem. The requests that the clients that connect via OSM frontend application that communicates with WebLogic arent being processed.
The oracle db is working and listening to port 1521, I can connect to it and can connect with the user defined in the WebLogic connection pool.
This is the first time working on this system, the application and integration was done by someone else who are not available to help us out, I hope someone here on the forum will be able to help us out with this problem.
Regards,
Omar

Often ConnectionFactory errors are caused by an inability to connect with the database hosting the OSM schema and user.
Check the database and make sure that both it and its listener are accepting connections. If that is ok you can also check the oms_pool configuration in WebLogic. Make sure the JNDI connection is valid. In my environments I see that DHCP often screws things up. If I install OSM on a host that has a DHCP assigned address (I'm guilty of being lazy when working in VMs and not statically assigning IP addresses) I often break the JNDI when I reboot the VM and get a new IP.
In WebLogic Admin Console:
Domain > Services > JDBC >Connection Pool > URL
and make sure the JDBC connection string is correct.

Need suggestion on implementing JMS message error recovery

Hi,
Our application has a JMS topic where we publish application events. Now, there can be scenarios where the consumers cannot process the message due to some infrastructure issues and would error out. We need a way so that those messages can be reprocessed again later. we are thinking of the following design for JMS message error recovery
1. Use a persistent TOPIC (this would ensure guaranteed delivery)
2. Configure a error destination on JMS topic e.g a jms queue
3. Have an error handling MDB listening to the Error destination. An error handling MDB would dequeue the errored messages from error destination and persist it to a Data base "error" table..
4. Provide a mechanism to republish those messages to topic (e.g a scheduler or admin ui or a command line utility) .. The messages would deleted from database "error" table and published to topic again....
A. Are there any issues with the above design which we need to handle?
B. Are there any additional steps required in a Cluster environment with a distributed topic and distribute error destination? (our error mdb will have one-copy-per-application setting)
B. From a performance angle, Is it OK to use persistent TOPIC ? Or will it better to persist the message to the db table and then publish it as a non persistent message ... ? (But i guess the performance should be more or less the same in both of these approaches)
C. Are there any other recommended design patterns for error recovery of JMS messages
Please advise.
Regards,
Arif

Thanks Tom !
We may not be able to go with the approach of delaying/pausing redelivery of the messsage because
1. Pausing entire MDB approach: Our MDB application consumes messages generated by different producers and our MDB needs to continue processing the messages even if messages corresponding to one producer is erroring out
2. Redelivery delay : This would only delay the retry of an errored message. But there would still be a problem if the message fails during all retries (i.e redelivery limit count). We don't want to lose this message. In our case, It is possible that a particular message cannot be processed due to unavailability of a third party system for hours or may be a day.
Basically, i am looking on approaches for a robust and performant error recovery/retry framework for our application (refer details in my first post on this thread) while fully making use of all features provided by middleware (WLS). Please advise.
Regards,
Arif

Oracle.jms.AQjmsException: Error creating the db_connection( OSB PS2.)

hi All,
I am beginner in OSB 11g. Please excuse me if I am asking any dumb question.
I am trying to post messages to Oracle AQ by configuring JMS Destination in OSB Alert destination
I have configured AQ JMS in weblogic 10.3.3 ( OSB PS2) following the blog (http://jianmingli.com/wp/?p=2950)
When i invoked my proxy OSB proxy service i am getting following exception. Can you please help if i am missing any kind of setup while configuring the JMS Module.
Caused By: oracle.jms.AQjmsException: Error creating the db_connection
     at oracle.jms.AQjmsDBConnMgr.getConnection(AQjmsDBConnMgr.java:625)
     at oracle.jms.AQjmsDBConnMgr.<init>(AQjmsDBConnMgr.java:399)
     at oracle.jms.AQjmsXAConnection.<init>(AQjmsXAConnection.java:112)
     at oracle.jms.AQjmsXAQueueConnectionFactory.createAllXAConnection(AQjmsXAQueueConnectionFactory.java:320)
     at oracle.jms.AQjmsXAQueueConnectionFactory.createXAQueueConnection(AQjmsXAQueueConnectionFactory.java:198)
     at weblogic.deployment.jms.JMSConnectionHelper.openConnection(JMSConnectionHelper.java:282)
     at weblogic.deployment.jms.JMSConnectionHelper.<init>(JMSConnectionHelper.java:144)
     at weblogic.deployment.jms.JMSSessionPool.getConnectionHelper(JMSSessionPool.java:517)
     at weblogic.deployment.jms.PooledConnectionFactory.createConnectionInternal(PooledConnectionFactory.java:355)
     at weblogic.deployment.jms.PooledConnectionFactory.createQueueConnection(PooledConnectionFactory.java:188)
     at com.bea.wli.sb.transports.jms.JmsOutboundMessageContext.getSession(JmsOutboundMessageContext.java:399)
     at com.bea.wli.sb.transports.jms.JmsOutboundMessageContext.newMessage(JmsOutboundMessageContext.java:621)
     at com.bea.wli.sb.transports.jms.JmsOutboundMessageContext.setRequestMetaData(JmsOutboundMessageContext.java:229)
     at com.bea.wli.sb.transports.jms.JmsOutboundMessageContext.access$100(JmsOutboundMessageContext.java:72)
     at com.bea.wli.sb.transports.jms.JmsOutboundMessageContext$SendAction.run(JmsOutboundMessageContext.java:788)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
     at weblogic.security.Security.runAs(Security.java:61)
     at com.bea.wli.sb.transports.jms.JmsOutboundMessageContext.send(JmsOutboundMessageContext.java:551)
     at com.bea.wli.sb.transports.jms.JmsTransportProvider.sendMessageAsync(JmsTransportProvider.java:680)
     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:597)
     at com.bea.wli.sb.transports.Util$1.invoke(Util.java:83)
     at $Proxy111.sendMessageAsync(Unknown Source)
     at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageWithoutService(TransportManagerImpl.java:489)
     at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:417)
     at com.bea.wli.sb.init.FrameworkStarter$TransportServiceImpl.sendMessageAsync(FrameworkStarter.java:391)
     at com.bea.alsb.alert.action.jms.JmsActionProvider.executeAction(JmsActionProvider.java:345)
     at com.bea.alsb.alert.AlertDestinationHandlerImpl.sendAlertToDestination(AlertDestinationHandlerImpl.java:105)
     at com.bea.alsb.alert.pipeline.PipelineAlertManager.processAlert(PipelineAlertManager.java:59)
     at stages.logging.runtime.AlertRuntimeStep.processMessage(AlertRuntimeStep.java:125)
     at com.bea.wli.sb.pipeline.debug.DebuggerRuntimeStep.processMessage(DebuggerRuntimeStep.java:74)
     at com.bea.wli.sb.stages.StageMetadataImpl$WrapperRuntimeStep.processMessage(StageMetadataImpl.java:346)
     at com.bea.wli.sb.stages.impl.SequenceRuntimeStep.processMessage(SequenceRuntimeStep.java:33)
     at stages.routing.runtime.RouteRuntimeStep.processMessage(RouteRuntimeStep.java:102)
     at com.bea.wli.sb.pipeline.debug.DebuggerRuntimeStep.processMessage(DebuggerRuntimeStep.java:74)
     at com.bea.wli.sb.stages.StageMetadataImpl$WrapperRuntimeStep.processMessage(StageMetadataImpl.java:346)
     at com.bea.wli.sb.pipeline.RouteNode.doRequest(RouteNode.java:106)
     at com.bea.wli.sb.pipeline.Node.processMessage(Node.java:67)
     at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:922)
     at com.bea.wli.sb.pipeline.Router.processMessage(Router.java:214)
     at com.bea.wli.sb.pipeline.MessageProcessor.processRequest(MessageProcessor.java:99)
     at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:593)
     at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:591)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
     at com.bea.wli.sb.security.WLSSecurityContextService.runAs(WLSSecurityContextService.java:55)
     at com.bea.wli.sb.pipeline.RouterManager.processMessage(RouterManager.java:590)
     at com.bea.wli.sb.test.service.ServiceMessageSender.send0(ServiceMessageSender.java:329)
     at com.bea.wli.sb.test.service.ServiceMessageSender.access$000(ServiceMessageSender.java:76)
     at com.bea.wli.sb.test.service.ServiceMessageSender$1.run(ServiceMessageSender.java:134)
     at com.bea.wli.sb.test.service.ServiceMessageSender$1.run(ServiceMessageSender.java:132)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
     at com.bea.wli.sb.security.WLSSecurityContextService.runAs(WLSSecurityContextService.java:55)
     at com.bea.wli.sb.test.service.ServiceMessageSender.send(ServiceMessageSender.java:137)
     at com.bea.wli.sb.test.service.ServiceProcessor.invoke(ServiceProcessor.java:454)
     at com.bea.wli.sb.test.TestServiceImpl.invoke(TestServiceImpl.java:172)
     at com.bea.wli.sb.test.client.ejb.TestServiceEJBBean.invoke(TestServiceEJBBean.java:167)
     at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl.invoke(TestService_sqr59p_EOImpl.java:353)
     at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
     at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
     at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused By: java.lang.ClassCastException: weblogic.jdbc.rmi.SerialConnection_weblogic_jdbc_rmi_internal_ConnectionImpl_weblogic_jdbc_wrapper_JTAConnection_weblogic_jdbc_wrapper_XAConnection_oracle_jdbc_driver_LogicalConnection_1033_WLStub cannot be cast to oracle.jdbc.internal.OracleConnection
     at oracle.jms.AQjmsGeneralDBConnection.getProviderKey(AQjmsGeneralDBConnection.java:96)
     at oracle.jms.AQjmsGeneralDBConnection.<init>(AQjmsGeneralDBConnection.java:65)
     at oracle.jms.AQjmsDBConnMgr.getConnection(AQjmsDBConnMgr.java:566)
     at oracle.jms.AQjmsDBConnMgr.<init>(AQjmsDBConnMgr.java:399)
     at oracle.jms.AQjmsXAConnection.<init>(AQjmsXAConnection.java:112)
     at oracle.jms.AQjmsXAQueueConnectionFactory.createAllXAConnection(AQjmsXAQueueConnectionFactory.java:320)
     at oracle.jms.AQjmsXAQueueConnectionFactory.createXAQueueConnection(AQjmsXAQueueConnectionFactory.java:198)
     at weblogic.deployment.jms.JMSConnectionHelper.openConnection(JMSConnectionHelper.java:282)
     at weblogic.deployment.jms.JMSConnectionHelper.<init>(JMSConnectionHelper.java:144)
     at weblogic.deployment.jms.JMSSessionPool.getConnectionHelper(JMSSessionPool.java:517)
     at weblogic.deployment.jms.PooledConnectionFactory.createConnectionInternal(PooledConnectionFactory.java:355)
     at weblogic.deployment.jms.PooledConnectionFactory.createQueueConnection(PooledConnectionFactory.java:188)

hi All,
Here is the actual exception while posting message into AQ ( AQ JMS) from OSB.
Caused By: java.lang.ClassCastException: weblogic.jdbc.rmi.SerialConnection_weblogic_jdbc_rmi_internal_ConnectionImpl_weblogic_jdbc_wrapper_JTAConnection_weblogic_jdbc_wrapper_XAConnection_oracle_jdbc_driver_LogicalConnection_1033_WLStub cannot be cast to oracle.jdbc.internal.OracleConnection
at oracle.jms.AQjmsGeneralDBConnection.getProviderKey(AQjmsGeneralDBConnection.java:96)
at oracle.jms.AQjmsGeneralDBConnection.<init>(AQjmsGeneralDBConnection.java:65)
Not sure what is missing in my AQ JMS configuration. Please help.
Regards,
Nagi

JMS adapter error in MQSeries connection

Dear All,
i am getting the below error in Communicatin Channel Monitoring for my sender JMS adapter:
Error during channel initialization; exception trace: javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for '<IP_ADRESS>:<MQ_QUEUE_MANAGER>'
     at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:546)
     at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1137)
     at com.ibm.mq.jms.MQConnection.createQMNonXA(MQConnection.java:799)
com.ibm.mq.MQException: Message catalog not found
     at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:171)
     at com.ibm.mq.MQClientManagedConnectionFactoryJ11._createManagedConnection(MQClientManagedConnectionFactoryJ11.java:228)
i have written '<IP_ADRESS>:<MQ_QUEUE_MANAGER>' just to hide the data - i am getting <IP_ADRESS> as IP Adress i gave in JMS adapter and <MQ_QUEUE_MANAGER> as Queue Manager i gave in JMS adapter.
i am using the correct IP and 1414 port of MQSeries server. I have used a MQQueueManager defined in MQSeries. i have deployed JMS adapter properly in XI server.
So can anybody suggest what could be the possible reason of this error and how to rectify it. It is slightly urgent.
Thanks and Regards,
Rajeev Gupta
Edited by: RAJEEV GUPTA on Jan 29, 2008 2:32 PM
Edited by: RAJEEV GUPTA on Jan 29, 2008 2:39 PM

Hi,
Check this as well [http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/index.jsp?topic=%2Fcom.ibm.mq.csqzaw.doc%2Fjm35210_.htm]
Regards,
Venkata S Pagolu

JMS Internal Error at Server Client Adapter!JMS Service is not started

Hi
Can any one tell me how to trouble shoot for following errors:
Failed to Create Connection! Reason: Response from the server could not be reached.
JMS Internal Error at Server Client Adapter!JMS Service is not started
The following hosts could not be reached 143:223:221:10:50310
We are trying to send the request from SONICMQ JMS to R/3 and trying to post the response to Sonic Queue. but we are facing some problems for JMS adapter .
but in JMS sender and receiver adapter i gave different IP and port for listen the SONIC queue. why it is showing in different IP here? this message got from logviewer.
regards
Rambarki...

Rambarki,
What is the error displayed on the Adapter Monitoring pages?
Generally the correct error descriptions for connectivity issues are found on adapter monitoring UI than any other.
Other possible reasons could be :
<i>JMS Service is not started
The following hosts could not be reached 143:223:221:10:50310</i> This might be issue with your network settings i.e. XI server is unable to reach the specified IP on specified port.
Regards,
Amol

Jms Protocol error

Hi ,
I am using Oracle 10g version 10.1.3 and Oracle AS JMS Server
I have a java client that is using the following configuration for JNDI conext.
// set the environment properties
env.put(Context.INITIAL_CONTEXT_FACTORY,"com.evermind.server.rmi.RMIInitialContextFactory");
env.put(Context.PROVIDER_URL,"opmn:ormi://vtun-lap.us.oracle.com:6003:home");
env.put(Context.SECURITY_PRINCIPAL,"oc4jadmin");
env.put(Context.SECURITY_CREDENTIALS,"apps10g");
QueueConnectionFactory queueConnectionFactory =util.getQueueConnectionFactory();
When I execute the following statement
QueueConnection queueConnection = queueConnectionFactory.createQueueConnection();
I am getting the following error:
[PROTOCOL ERROR] JMSRemoteServer[vtun-lap:12601]: "JMS protocol" error, expected "-559,038,735", got
Object Address: 0x529EDEC4
Thank you
Van Sioung

Your client is using old OC4J JMS classes - you need to set up your client's class-path to point to the .jar files that came with 10.1.3. The exact set of .jar files required for looking up and using OC4J JMS connection factories and destinations over RMI is covered in the 10.1.3 version of the Services Guide - in the JMS Chapter.

JMS Deserialization Error

Hi,
I am encountering the JMS Exception 'Error deserializing object'. I do not have
the stack trace. The same code works perfectly fine 99% of the time. It throws
exception at random very rarely.
Can anyone help me with the possible causes of this exception.
Thanks in advance.

Hi Gordon,
I'm getting the EXACT same problem . were you able to resolve this problem . please let me know what the soln is
thanks
mantish

JMS communication error

Hi,
I have deployed JMS application on Oracle 9i Application Server. I have made the necessary configurations in jms.xml(eg., Setting the queue connection factory and the name of the queue). Now when I try to run the client application I get the following error.
JMS communication error = Unable to connect to JMSServer (localhost/127.0.0.1:9127)
The JMS server is running on port 9127....
The rmi server is running on port 23791...
Can anyone help me out as to how this problem could be resolved ?
Sirisha

Hi
Did you try changing jms.xml to point to the real ip instead of host="localhost" ?
sometimes it works.
g'day
nimo

Reciever JMS Adpater Error

Hi Experts,
I am getting following error in Reciever JMS adapter:
I am using transport protocol is Acces JMS provider with JNDI
Channel error occurred; detailed error description: com.sap.aii.adapter.jms.api.connector.ConnectorException: Error creating initial context with environment: {java.naming.provider.url=http://168.89.59.82:7005/, java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory}for profile: ConnectionProfile of channel: CC_eRespond_ServiceTicketson node: 8273250 having object id: d72754188a053d43b6aa0dd420346941: javax.naming.CommunicationException
at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createInitialContext(JndiConnectorImpl.java:66)
Can anyone please tell me what is the cause of this error.
Kind Regards,
Praveen.

Hi Experts,
We are sending messages from XI to Weblogic server with the help of JMS Adapter. The Queue is available in Weblogic server.
Our configuration of JMS receiver Adapter is
JNDI Lookup Name of Queue Connection Factory----
ConnectionFactory
JNDI Lookup Name of JMS Queue----
queue/IntegrationQueue
Name of JNDi Initial Context Factory: -
weblogic.jndi.WLInitialContextFactory
JNDI Server Address:----
weblogic server ip
JNDI Logon User: -
user
JNDI Password: -
password
Could you please help us.
The Error message as follows
Channel error occurred; detailed error description: com.sap.aii.adapter.jms.api.connector.ConnectorException: Error creating initial context with environment: {java.naming.provider.url=http://IP:port/, java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory}for profile: ConnectionProfile of channel: CC_eRespond_ServiceTicketson node: 8273250 having object id: d72754188a053d43b6aa0dd420346941: java.lang.NoClassDefFoundError
at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createInitialContext(JndiConnectorImpl.java:66)
Regards
Praveen

Storing of JMS ConnectionFactory in JNDI works Intermittently

I am saving my JMX ConnectionFactory (currently using an ActiveMQConnectionFactory) using JNDI. I am doing this so that the JMS server can be changed by simply replacing the stored ConnectionFactory object in JNDI all my applications can be switched to a new JMS server. My JNDI is currently backed by and LDAP Server (OpenDS). This all seems to work just fine, most of the time. I am running multiple applications on multiple oc4j servers on multiple computers and they all can get the correct ConnectionFactory and connect to the messaging system. My problem is that I am exposing properties from this JNDI server using JMX. When I invoke a method from the MBean browser in the OC4J Application Server Control that tries to access the Connection Factory through JNDI, I get an error that the object returned could not be cast to a ConnectionFactory. All of my other code seems to work. In fact, when I run standalone test code I can call the exact same method directly and it works. I just appears to happen when called through I assume and JMX invoke. What am I missing? Thanks for any light you can shed on this problem.

Yes, it is a separate application running under the same instance of the JVM (the OC4J container). I agree that the class is probably not being recognized by the classloader for the "OC4j Application Server Control" application, but can't figure out how to successfully include the relevant jar in the classpath of this classloader. Because of this I am not able to verify this correct nor fix the problem. I am wading through the Oracle documentation now to try and figure out where the jar belongs and if I need to change any configuration files.

Application Server 9.1 JMS connection errors

We are running SJSAS 9.1 on several machines and on one cluster the server logs are getting flooded with errors like this.
Error occurred on connection creation [localhost:37676]. - cause: java.net.ConnectException: Connection refused: connect|#]
After many of these we get messages like: MQJMSRA_RA2001: onException:Reconnect unsuccessfull on loop# 518|#
I was able to trace these back to a point in time where it appears the admin server asked the node agent to shut down the JMS provider. I see the following messages
[#|2008-01-21T07:38:36.334-0500|INFO|sun-appserver9.1|javax.resourceadapter.mqjmsra.lifecycle|_ThreadID=24;_ThreadName=iMQEventHandler-3;|MQJMSRA_RA1101: onEvent:Connection Event:E201:[E201]: Connection closed due to admin requested shutdown: localhost:37676(2243), com.sun.messaging.jms.notification.ConnectionClosedEvent[source=BrokerAddress=localhost:37676(2243), ConnectionID=3785864354043875840, ReconnectEnabled: false, IsConnectedToHABroker: false]|#]
[#|2008-01-21T07:38:36.334-0500|WARNING|sun-appserver9.1|javax.resourceadapter.mqjmsra.lifecycle|_ThreadID=24;_ThreadName=iMQEventHandler-3;_RequestID=7cad7955-d7fc-4448-875f-869f3ccf8a3b;|MQJMSRA_RA2001: onException:Connection Failed:[C4056]: Received goodbye message from broker.|#]
Our application doesn't even use JMS and there are no connection factories or destinations configured. Does anybody know why this is happening, or how to prevent it?

Try this:
edit your /etc/hosts file and ensure that your hostname maps to an absolute IP address and not to 127.0.0.1.
Hope that helps

JMS receiver error

Hello,
I have maintained a JMS receiver adapter to an existing MQ system (IBM WebSphere 6.0)
After deploying the modules to PI (7.11) the adapter goes green but allways says "Sucessfully disconnected from destination".
When sending a message through this adapter I get the error message:
"Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: No transition found from state: STARTING, on event: process_commence for DFA: JMSReceiver_ATLAS_MQ:4b9d8e8dfe883ebeb7ab5af79e59cdf6"
I can not find out where the problem can be....I played arrounf with the several options for QM Manasger, channels.....
I do not use any "Advanced Adapter options"
Anybody who can help me????
best regards
Werner

I still have checked all the notes and blogs....
But nothing helps, I still have the same problem.
The problem can be, that I am not a MQ specialist, but I have access to the MQ and I can see the settings.
Do I have to use adapter specific atributes???
I only use QManager, Chanell, queue....
ANd there is somehting other really strange.
I have create several components for different scenarios.
When I create an Adapter in one component, I get the error I listed before.
But in some components I get the error:
"Channel Has Internal Error" in the RWB overview and in the node
"Adapter had not provided any status infomration about this channel"
I tried with Creating new channel, copy channel between the components....
but allways the same...in some components I get this error
in other components I get the message "Successfully discponnected from destination"
Werner
Edited by: Werner Magerl on Sep 28, 2010 1:59 PM

Messages in JMS Topic Error destination

Hi,
I have a JMS Topic with an error destination queue configured. Now, In our scenario , there are two subscribers of topic for the same message. Suppose for a message published to topic, subscriber1 is able to processes message successfully but subscriber2 throws errors when processing the same message.
1. Once the redelivery limit is reached and subscriber2 continues to throw exception, Will the message get en queued to Error Destination (in spite of the fact that subscriber 1 has processed the same message successfully) ?
2. For a consumer (e.g MDB) listening to Error destination and consuming error messages, Is it possible to determine which topic subscriber was unable to process the message ?
Please let me know
Regards,
Arif

Here it depends on the state of the message, if the message is visible then the message would be available for consumption, else it is not. In case the subscriber 2 failed to consume the message and the message is still visible then a retry would be made, else the message would not be retried.
In case the message is visible then the message would be move to the error queue based on the configured redelivery attempts.
Additionally, an MDB can find the destination using the getJMSDestination() call. But as per my understanding we will only be able to get the name of the last destination which in this case would be error queue:
http://docs.oracle.com/javaee/1.4/api/javax/jms/Message.html#getJMSDestination%28%29

JMS Adapter Error

Hi Experts,
               We are havingone problem in Sender JMS Adapter. From Sender (SeeBeyond) xml files are getting posted into Remote Queue in MQ, then it has been sent to Local Queue of MQ, and then finally from Local MQ Queue PI is picking up the data and sending it to SNC system.
               The problem lies in PI itself. While coming into PI, the value in the incoming payload where special characters(say, swedish character) are coming, are coming into PI as a garbage value. Whereas, in Sender (SeeBeyond), MQ and in PI Character set is ISO 8859_1. We have stopped the Sender JMS channel in PI, and checked the payload in MQ and in SeeBeyond, in both of the cases it's fine, only when coming into PI, data are getting corrupted.
                For this we have done some investigation like below,
1) We had changed the CCSID from 00819 (ISO 8859_1) to 1208 (UTF-8), 1200 (UTF 16), but no luck.
2) We had added th below mentioned modules into Sender JMS in Processing Sequence with the existing modules,
AF_Modules/MessageTransformBean                                              Local Enterprise Bean               ContentType
(ii) AF_Modules/TextCodepageConversionBean                                   Local Enterprise Bean               codepageConversion
But yet we are getting the same error in encoding in the payload while coming into PI.
Can anybody help me out with it, or probably let me know if I am missing something in my investigation.
//BR
Soumya

Hi Stefan,
             Sorry for the late reply. We were testing in different cases in PI, and here what I have found. In Sender JMS adapter we had put the module "AF_Modules/MessageTransformBean" with Module Key "Transform". And the configuration of this Module Key is as follows:-
Transform     Transform.ContentType      text/plain;charset="UTF-8"
And we changed the CCSID to 1208 (UTF-8). Now when we saw the payload in SXI_MONITOR in PI, we have found that the special character is being distorted whereas in View Sourse the payload is fine including special character also. That means there might be some display problem in SXI_MONITOR.
             Now, the Sender sends the data in XML iin ISO 8859-1nto MQ, MQ send the same as a string in PI, from PI it's going to SCM system (R/3, Supply Chain Management), where we could see ABAP.APPLICATION Error. We tested the interface in SCM system by running SPROXY and found that it's not able to recognise ISO 8859-1, since it's a Non-Unicode System, it will only understan UTF-8 and hence the error. Now manually we have changed the XML Header into UTF-8 and tested at SCM side, and this goes fine.
           So, we could see the changing of XML Header from ISO 8859-1 to UTF-8 would be running fine at receiver end (SCM). Since SCM is a Non-Unicode System, the XML header cannot be changed to UTF-8, is there any possibility in PI that we can change the XML Header from ISO 8859-1 to UTF-8.
           For your information, we are using Sender JMS adapter to receive the File from Sender and we are using Receiver XI adapter to post the file into SCM system.
What's your suggestion Stefan, how can we change the XML Header from ISO 8859-1 to UTF-8 in PI?
Many Thanks
Soumya

SJSAS 2005Q1 JMS ConnectionFactory error

Similar Messages

Maybe you are looking for