Oracle JMS Client Acknowledgement?
Hi Guy,
How can we implement Client Ack mode using BPEL and JMS adapter?
There is no activity to acknowledge a message.
I tried configuring a outbound connection factory for JMSAdapter with acknowledgment mode as CLIENT_ACKNOWLEDGMENT, but didn't work as expected.
Please advise.
--Chari
In your JMS client, you can set the system properties "oracle.jms.minSleepTime" and "oracle.jms.maxSleepTime"
For example,
System.setProperty("oracle.jms.minSleepTime", "100");
System.setProperty("oracle.jms.maxSleepTime", "4000");
In this case, the listener will wait for 100ms to start with and the sleep time will be doubled if there is no new message - 200, 400, 800, 1600, 3200, and 4000 ms. The sleep time won't go beyond 4000ms and will be reset to 0 whenever there is a new message.
Similar Messages
-
JMS Client disconnects often randomly in Weblogic10.3 cluster setup
Hi,
It would be very helpful for us if someone can suggest the way to overcome the below jms issue.
Our application recently migrated to Weblogic 10.3 from Weblogic8.1, It is a clustered set up with two managed servers each on different solaris machine.
Client connects to jms using wljmsclient.jar and wlclient.jar with t3 protocol.
When client starts jms connection, it is getting connected to server with no errors, however we often see that client jms connection disconnects in between,
It sometimes calls onException() and some times we do not even see any error message in console log when it disconnects,
When onException() is called, we can see below exception stack trace:
==========================
JMS exception class = weblogic.messaging.dispatcher.DispatcherException: java.rmi.MarshalException: CORBA COMM_FAILURE 1398079697 No; nested exception is:
org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 209 completed: No
weblogic.jms.common.JMSException: weblogic.messaging.dispatcher.DispatcherException: java.rmi.MarshalException: CORBA COMM_FAILURE 1398079697 No; nested exception is:
org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 209 completed: No
at weblogic.jms.dispatcher.DispatcherAdapter.convertToJMSExceptionAndThrow(DispatcherAdapter.java:116)
at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSyncNoTran(DispatcherAdapter.java:61)
at weblogic.jms.client.JMSSession.acknowledge(JMSSession.java:2191)
at weblogic.jms.client.JMSSession.acknowledge(JMSSession.java:2120)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4588)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:4233)
at weblogic.jms.client.JMSSession.executeMessage(JMSSession.java:3709)
JMS exception class = java.rmi.MarshalException: CORBA COMM_FAILURE 1398079697 No; nested exception is:
org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 209 completed: No
weblogic.jms.common.LostServerException: java.rmi.MarshalException: CORBA COMM_FAILURE 1398079697 No; nested exception is:
org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 209 completed: No
at weblogic.jms.client.JMSConnection.dispatcherPeerGone(JMSConnection.java:1436)
at weblogic.messaging.dispatcher.DispatcherWrapperState.run(DispatcherWrapperState.java:692)
at weblogic.messaging.dispatcher.DispatcherWrapperState.timerExpired(DispatcherWrapperState.java:617)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
=======================
When onException() is triggered, TopicConnection and TopicSession gets recreated in program, however jms is not getting reconnected once onException() is called. Some times jms session is lost in between with out any errors in log. We did not see this issue when our app used Weblogic8.1.
We greatly appreciate if someone can help to resolve this issue.Hi,
This is a common issue if you use wljmsclient.jar and wlclient.jar at client side. Many times we get "org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 209 completed: No" Please try using weblogic.jar at client end or even there is a better option to create the "*wlfullclient.jar*" using the jarBuilder utility provided as part of WebLogic.
To create the "wlfullclient.jar" please refer to the following link:
[http://download-llnw.oracle.com/docs/cd/E11035_01/wls100/client/jarbuilder.html#wp1077742|http://download-llnw.oracle.com/docs/cd/E11035_01/wls100/client/jarbuilder.html#wp1077742]
Thanks
Jay SenSharma
http://jaysensharma.woardpress.com -
Create EJB 3.0 Message Driven Bean on a Oracle JMS (AQ)
Hi, I need to develop a EJB 3.0 Message Driven Bean. The MDB has to work on a Oracle AQ using Oracle JMS. Is there any how-to document giving an example about this issue. Can you give an example how to create the JMS destination in OC4J (how to configure the Oracle JMS AQ in OC4j), issue the JMS destination via annotions (resource injection) in the MDB. Please give me a working example of the MDB and a test client to produce a message. Regards, Arjan Jorritsma
Check your ejb-jar.xml and see if it has the version of "2.1" there...
If the application was depending upon EJB 3.0 annotations but it had a ejb-jar.xml that had version set to "2.1" and there was no oracle specific descriptor (orion-ejb-jar.xml) to designate it use the resource adapter; It would expect JMS destination and connection factory that is required for a JMS-MDB set in the ejb-jar.xml. So try to change the ejb-jar.xml to update the version to "3.0", OC4J would have parsed the annotation and combined the metadata with ejb-jar.xml and it would work.
-Frances -
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 -
Weblogic Connection with Oracle JMS AQ errors
Hi All,
I am a newbie with SOA 11g and I am trying to do a simple test case for a use case of connecting Oracle AQ JMS with Weblogic and using it in my SOA 11g process. I am trying to publish something to my queue that I created but I am getting this error in the weblogic / soa log files pasted below :
The steps I followed exactly are this :
1) Created a Database Queue called DemoInqueue using the following scripts :
exec dbms_aqadm.create_queue_table ( queue_table=> 'DemoInQueue', queue_payload_type=> 'SYS.AQ$_JMS_TEXT_MESSAGE', multiple_consumers=> FALSE, compatible=> '8.1');
COMMIT;
exec dbms_aqadm.create_queue(queue_name=> 'DemoInQueue', queue_table=> 'DemoInQueue');
COMMIT;
exec dbms_aqadm.start_queue('DemoInQueue');
COMMIT;
2) Created a Data Source in weblogic server : Called it using the JNDI name : jdbc/oracle/jms Driver Class Name : oracle.jdbc.xa.client.OracleXADataSource (I tested the connection it works fine)
3) Created a JMS Module (JMSTestModule) and then Created a New Summary of Resource for it ( AQServer) and chose option Foregin Server.
Under General Tab, I gave "oracle.jms.AQjmsInitialContextFactory" as the JNDI Initial Context Factory and Under JNDI Properties I put in "datasource=jdbc/oracle/jms" as I created the above datasource.
Under Connection Factores I created a new "ForeignConnectionFactory-0". Under Configuration I gave Local JNDI name as "jms/DemoCF" and remote JNDI Name as "XAQueueConnectionFactory" (I have also tried with
QAConnectionFactory but no difference )
Under Destinations I created a new "ForeignDestination-0" with local JNDI name as "jms/DemoInQ" and Remote JNDI Name as "Queues/DemoInQueue" (Because my Queue name is that)....
4) I restarted the Weblogic Server then went to SOA suite and tried a very simple process Hello world added a JMS adpater....Inside the adpater I selected OEMS (Advanced Queueing), App server my weblogic server,
operation as ProduceMessage and when I hit Browse I was able to see my AQServer ForeignDestination-0 Queue. I selected it and under destination name it populated "jms/DemoInQ" but under JNDI name it also
populated "eis/aqjms/Queue" I left that as is and deployed my process and tried invoking it. It failed with the error message below.....I also tried modifying the JNDI name to something else...in Jdev..but the results
are the same....
Are these steps correct ? Am I missing something here.?
I followed all the blogs and forums in this site and I think I did all the steps...but if anyone can help me I would really appreciate it...
Here is the error stack below :
<BEA1-57B9592B4D0D4FFD1A5C> <3f3d2d8955322f32:-5d57c961:12ca300b9a3:-7fd3-00000000000002d7> <1291230437281> <BEA-190032> << eis/aqjms/Queue > ResourceAllocationException thrown by resource adapter on call to ManagedConnectionFactory.createManagedConnection(): "BINDING.JCA-12141
ERRJMS_CONN_FAC_NOT_FOUND.
ERRJMS_CONN_FAC_NOT_FOUND.
Unable to instantiate connection factory. JMS adapter was unable to look up the connection factory aqjms/XAQueueConnectionFactory neither through JNDI nor instantiate it as a Java class.
Please examine the log file to determine the problem.
">
####<Dec 1, 2010 2:07:17 PM EST> <Warning> <Connector> <OLRMSPLAP103> <AdminServer> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-57B9592B4D0D4FFD1A5C> <3f3d2d8955322f32:-5d57c961:12ca300b9a3:-7fd3-00000000000002d7> <1291230437296> <BEA-190032> << eis/aqjms/Queue > ResourceAllocationException thrown by resource adapter on call to ManagedConnectionFactory.createManagedConnection(): "BINDING.JCA-12141
ERRJMS_CONN_FAC_NOT_FOUND.
ERRJMS_CONN_FAC_NOT_FOUND.
Unable to instantiate connection factory. JMS adapter was unable to look up the connection factory aqjms/XAQueueConnectionFactory neither through JNDI nor instantiate it as a Java class.
Please examine the log file to determine the problem.
">
SOA LOG.....
####<Dec 1, 2010 2:07:17 PM EST> <Error> <oracle.soa.adapter> <OLRMSPLAP103> <AdminServer> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-57B9592B4D0D4FFD1A5C> <3f3d2d8955322f32:-5d57c961:12ca300b9a3:-7fd3-00000000000002d7> <1291230437359> <BEA-000000> <JCABinding=> [default/HelloWorldComposite!1.0*soa_25f514de-3db3-4bed-9144-44d83dacbe10.Publishmessage]:Produce_Message One-way operation Produce_Message() failed>
####<Dec 1, 2010 2:07:17 PM EST> <Error> <oracle.soa.bpel.engine.ws> <OLRMSPLAP103> <AdminServer> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-57B9592B4D0D4FFD1A5C> <3f3d2d8955322f32:-5d57c961:12ca300b9a3:-7fd3-00000000000002d7> <1291230437359> <BEA-000000> <<WSInvocationManager::invoke> got FabricInvocationException
oracle.fabric.common.FabricInvocationException: BINDING.JCA-12563
Exception occured when binding was invoked.
Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'Produce_Message' failed due to: JCA Binding Component connection issue.
JCA Binding Component is unable to create an outbound JCA (CCI) connection.
HelloWorldComposite:Publishmessage [ Produce_Message_ptt::Produce_Message(body) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12141
ERRJMS_CONN_FAC_NOT_FOUND.
ERRJMS_CONN_FAC_NOT_FOUND.
Unable to instantiate connection factory. JMS adapter was unable to look up the connection factory aqjms/XAQueueConnectionFactory neither through JNDI nor instantiate it as a Java class.
Please examine the log file to determine the problem.Thanks for passing along the link.
The part about Oracle's documentation not mentioning the JmsAdapter configuration was a real sticking point for me - I was having the same problem as the original poster until I updated that deployment as the link outlined.
Also, towards the end of that link the author mentions running in to problems getting their composite to successfully bind to the queue definitions that were created in WebLogic.
I attempted post my solution to this on the original site, but I'm not sure if it got through - so I'll add the details of what worked for me here:
Connection Factory:
Local JNDI: aqjms/JMSTest_Connection_Factory
Remote JNDI: XAQueueConnectionFactory
Destination:
Local JNDI: aqjms/JMSTest_Queue
Remote JNDI: Queues/JMSTest_Queue
Outbound Connection Pool:
Name: eis/aqjms/JMSTest_Queue
Connection Factory: aqjms/JMSTest_Connection_Factory
JDeveloper Composite:
Destination Name: aqjms/JMSTest_Queue
JNDI Name: eis/aqjms/JMSTest_Queue
Cheers,
- Nathan -
Stomp: client acknowledge error message
Using OpenMQ 4.4 b04, I try to use client acknowledge.
I have found that the broker expects not only the message Id but also the subscription id.
If I use the subscription id which is in the message header and add it to the ACK Stomp frame, the broker displays these lines in the log file:
javax.jms.JMSException: Ack a message[ID:297-192.168.178.21(c1:a1:82:3f:f4:72)-1
731-1239293602031] that is not found in subscriber[{F90F7D8E-843A-4EBB-BA15-23B2
0F732060}]
at com.sun.messaging.bridge.service.stomp.StompSubscriberSession.ack(Sto
mpSubscriberSession.java:175)
at com.sun.messaging.bridge.service.stomp.StompProtocolHandler.onACK(Sto
mpProtocolHandler.java:643)
at com.sun.messaging.bridge.service.stomp.StompProtocolFilter.execute(St
ompProtocolFilter.java:123)
at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultPro
tocolChain.java:136)
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.jav
a:103)
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.jav
a:89)
at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextT
ask.java:67)
at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.
java:57)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)Which special headers are expected by the broker in a ACK frame? If the Stomp frame does not contain a subscription header, the error log gives some hints which mention a "/subscription-to/" header:
WARNUNG: No subscription header specified, ACK all non-transacted subscription i
ds with prefix /subscription-to/ for message ID:409-192.168.178.21(b3:dd:75:42:f
:91)-1781-1239294021718
09.04.2009 18:20:30
SCHWERWIEGEND: ACK failed: Can't determine subscriber to ack message ID:409-192.
168.178.21(b3:dd:75:42:f:91)-1781-1239294021718. Please specify subscription hea
derIt's the STOMP ACK 'subscription' header. STOMP client should always specify a subscription header on ACK besides message-id header.
The exception you saw is a bug in ACK message for client ack mode. The client mode ACK problem has been fixed in build5.
MESSAGE
index:0
content-length:10
destination:/queue/q0
subscription:sub2
timestamp:1239309779559
redelivered:false
priority:4
expires:0
message-id:ID:7-10.5.81.239(80:17:42:1e:c5:e7)-55202-1239309779559
Message #0
ACK
message-id:ID:7-10.5.81.239(80:17:42:1e:c5:e7)-55202-1239309779559
subscription:sub2 -
Oracle JMS using AQ throwing InvalidDestinationException
While creating Queue(AQJMS) using Application-Client.xml as shown below iam getting the below shown error. I have configured the Oracle JMS Provider and datasource on Server . Can you Please suggest me what has to be done. Iam using Oracle 10g AS(10.1.2).
Error
javax.jms.InvalidDestinationException: Destination "JMSUSER.demoQueue" has inval id type "class oracle.jms.AQjmsDestination" and cannot be used with OC4J JMS.
at com.evermind.server.jms.EvermindDestination.checkDestination EvermindDestination.java:262)
at com.evermind.server.jms.EvermindMessageProducer.<init>(EvermindMessageProducer.java:61)
at com.evermind.server.jms.EvermindQueueSender.<init>(EvermindQueueSender.java:50)
at com.evermind.server.jms.EvermindQueueSession.createSender(EvermindQueueSession.java:91)
at mypackage.Test.enqueue(Test.java:107)
at mypackage.Test.<init>(Test.java:37)
at mypackage.Test.main(Test.java:48)
[application-client.xml]
<resource-ref>
<res-ref-name>jms/YourQueueConnectionFactory</res-ref-name>
<res-type>javax.jms.QueueConnectionFactory</res-type>
<res-auth>Application</res-auth>
<res-sharing-scope>Shareable</res-sharing-scope>
</resource-ref>
<resource-env-ref>
<resource-env-ref-name>jms/demoQueue</resource-env-ref-name>
<resource-env-ref-type>javax.jms.Queue</resource-env-ref-type>
</resource-env-ref>
[orion-application-client.xml]
<resource-ref-mapping
name="jms/YourQueueConnectionFactory"
location="java:comp/resource/OJMSReference/QueueConnectionFactories/someQcf" />
<resource-env-ref-mapping name="jms/demoQueue" location="java:comp/resource/OJMSReference/Queues/jmsuser.demoQueue"/>
Thanks in Advance for the help.no not required. Foreign JMS for Weblogic is independent of OSB. It will work with out installation of OSB.
Manoj -
Publish/Subscribe Client Acknowledgements!?
Hi all.
Im experimenting with the simplePublishSubscribe example from sun's JMS tutorial, trying to understand how the acknowledgements work when in CLIENT_ACKNOWLEDGEMENT mode.
So I set the above mode for the session and run the example without any message.acknowledgment() 's. So now after the the publish message have been delivered to the subscriber, without being acknowledged from the client, running topicSession.recover() should result in all the previous messages being redelivered to the client as they have not been acknowledged and therefore not deleted from the topic.
However after trying this it would seem that not messages are redelivered to the client!? Any advice on this scenario. It is important since the application we are designing relies on client acknowledgements in an asyncronous mode.
Thanks
(PS...i have search the forum and nnot found a definitive answer to this problem)Hi,
The following code should work as you expect:
session = connection.createTopicSession(false,Session.CLIENT_ACKNOWLEDGE);
subscriber = session.createSubscriber( topic );
message = subscriber.receive();
mID = message.getJMSMessageID();
session.recover();
message = subscriber.receive();
newMID = message.getJMSMessageID();
if( ! mID.equals( newMID ) )
//fail!!!
Arnaud
http://www.arjuna.com -
Oracle JMS AQ connection using Weblogic 10.3.3
Hi All,
I am a newbie with SOA 11g and I am trying to do a simple test case for a use case of connecting Oracle AQ JMS with Weblogic and using it in my SOA 11g process. I am trying to publish something to my queue that I created but I am getting this error in the weblogic / soa log files pasted below :
The steps I followed exactly are this :
1) Created a Database Queue called DemoInqueue using the following scripts :
exec dbms_aqadm.create_queue_table ( queue_table=> 'DemoInQueue', queue_payload_type=> 'SYS.AQ$_JMS_TEXT_MESSAGE', multiple_consumers=> FALSE, compatible=> '8.1');
COMMIT;
exec dbms_aqadm.create_queue(queue_name=> 'DemoInQueue', queue_table=> 'DemoInQueue');
COMMIT;
exec dbms_aqadm.start_queue('DemoInQueue');
COMMIT;
2) Created a Data Source in weblogic server : Called it using the JNDI name : jdbc/oracle/jms Driver Class Name : oracle.jdbc.xa.client.OracleXADataSource (I tested the connection it works fine)
3) Created a JMS Module (JMSTestModule) and then Created a New Summary of Resource for it ( AQServer) and chose option Foregin Server.
Under General Tab, I gave "oracle.jms.AQjmsInitialContextFactory" as the JNDI Initial Context Factory and Under JNDI Properties I put in "datasource=jdbc/oracle/jms" as I created the above datasource.
Under Connection Factores I created a new "ForeignConnectionFactory-0". Under Configuration I gave Local JNDI name as "jms/DemoCF" and remote JNDI Name as "XAQueueConnectionFactory" (I have also tried with
QAConnectionFactory but no difference )
Under Destinations I created a new "ForeignDestination-0" with local JNDI name as "jms/DemoInQ" and Remote JNDI Name as "Queues/DemoInQueue" (Because my Queue name is that)....
4) I restarted the Weblogic Server then went to SOA suite and tried a very simple process Hello world added a JMS adpater....Inside the adpater I selected OEMS (Advanced Queueing), App server my weblogic server,
operation as ProduceMessage and when I hit Browse I was able to see my AQServer ForeignDestination-0 Queue. I selected it and under destination name it populated "jms/DemoInQ" but under JNDI name it also
populated "eis/aqjms/Queue" I left that as is and deployed my process and tried invoking it. It failed with the error message below.....I also tried modifying the JNDI name to something else...in Jdev..but the results
are the same....
Are these steps correct ? Am I missing something here.?
I followed all the blogs and forums in this site and I think I did all the steps...but if anyone can help me I would really appreciate it...
Here is the error stack below :
<BEA1-57B9592B4D0D4FFD1A5C> <3f3d2d8955322f32:-5d57c961:12ca300b9a3:-7fd3-00000000000002d7> <1291230437281> <BEA-190032> << eis/aqjms/Queue > ResourceAllocationException thrown by resource adapter on call to ManagedConnectionFactory.createManagedConnection(): "BINDING.JCA-12141
ERRJMS_CONN_FAC_NOT_FOUND.
ERRJMS_CONN_FAC_NOT_FOUND.
Unable to instantiate connection factory. JMS adapter was unable to look up the connection factory aqjms/XAQueueConnectionFactory neither through JNDI nor instantiate it as a Java class.
Please examine the log file to determine the problem.
">
####<Dec 1, 2010 2:07:17 PM EST> <Warning> <Connector> <OLRMSPLAP103> <AdminServer> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-57B9592B4D0D4FFD1A5C> <3f3d2d8955322f32:-5d57c961:12ca300b9a3:-7fd3-00000000000002d7> <1291230437296> <BEA-190032> << eis/aqjms/Queue > ResourceAllocationException thrown by resource adapter on call to ManagedConnectionFactory.createManagedConnection(): "BINDING.JCA-12141
ERRJMS_CONN_FAC_NOT_FOUND.
ERRJMS_CONN_FAC_NOT_FOUND.
Unable to instantiate connection factory. JMS adapter was unable to look up the connection factory aqjms/XAQueueConnectionFactory neither through JNDI nor instantiate it as a Java class.
Please examine the log file to determine the problem.
">
SOA LOG.....
####<Dec 1, 2010 2:07:17 PM EST> <Error> <oracle.soa.adapter> <OLRMSPLAP103> <AdminServer> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-57B9592B4D0D4FFD1A5C> <3f3d2d8955322f32:-5d57c961:12ca300b9a3:-7fd3-00000000000002d7> <1291230437359> <BEA-000000> <JCABinding=> [default/HelloWorldComposite!1.0*soa_25f514de-3db3-4bed-9144-44d83dacbe10.Publishmessage]:Produce_Message One-way operation Produce_Message() failed>
####<Dec 1, 2010 2:07:17 PM EST> <Error> <oracle.soa.bpel.engine.ws> <OLRMSPLAP103> <AdminServer> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-57B9592B4D0D4FFD1A5C> <3f3d2d8955322f32:-5d57c961:12ca300b9a3:-7fd3-00000000000002d7> <1291230437359> <BEA-000000> <<WSInvocationManager::invoke> got FabricInvocationException
oracle.fabric.common.FabricInvocationException: BINDING.JCA-12563
Exception occured when binding was invoked.
Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'Produce_Message' failed due to: JCA Binding Component connection issue.
JCA Binding Component is unable to create an outbound JCA (CCI) connection.
HelloWorldComposite:Publishmessage [ Produce_Message_ptt::Produce_Message(body) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12141
ERRJMS_CONN_FAC_NOT_FOUND.
ERRJMS_CONN_FAC_NOT_FOUND.
Unable to instantiate connection factory. JMS adapter was unable to look up the connection factory aqjms/XAQueueConnectionFactory neither through JNDI nor instantiate it as a Java class.
Please examine the log file to determine the problem.I executed your scripts one by one and then tried again. Same Error Message. I think the problem is not in the AQ queue. The issue is with the BPEL / SOA process as the error message below clearly says it's not able to find aqjms/XAQueueConnectionFactory. That's the JNDI name in my Jdeveloper ? Is that JNDI what I should be using or should be match something else ? Please help................
Latest Error LOG...
<<anonymous>> <BEA1-0B06BE09987B4FFD1A5C> <3f3d2d8955322f32:-73cb8b9a:12ca58d835d:-7fd3-0000000000000123> <1291268540004> <BEA-000000> <<CubeEngine::handleWorkItem> This exception occurred because the fault thrown in the BPEL flow was not handled by any fault handlers and reached the top-level scope. Root cause : com.oracle.bpel.client.BPELFault: faultName: {{http://schemas.oracle.com/bpel/extension}bindingFault}
parts: {{
summary=<summary>Exception occured when binding was invoked.
Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'Produce_Message' failed due to: JCA Binding Component connection issue.
JCA Binding Component is unable to create an outbound JCA (CCI) connection.
HelloWorldComposite:Publishmessage [ Produce_Message_ptt::Produce_Message(body) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12141
ERRJMS_CONN_FAC_NOT_FOUND.
ERRJMS_CONN_FAC_NOT_FOUND.
Unable to instantiate connection factory. JMS adapter was unable to look up the connection factory aqjms/XAQueueConnectionFactory neither through JNDI nor instantiate it as a Java class.
Please examine the log file to determine the problem.
The invoked JCA adapter raised a resource exception.
Please examine the above error message carefully to determine a resolution.
</summary>
,detail=<detail>aqjms/XAQueueConnectionFactory</detail>
,code=<code>null</code>}
> -
What is the impact of upgrading JMS client from 3 to 5?
Hi,
I'm new to JMS client. Recently, I was tasked to look into re-writing
one of our old applications that was using JMS client 3.0.
The company is going to upgrade all the existing JMS client from
3.0 to 5.0 and Sonic MQ from 4.0 to 6.1
Please advise how should I go about doing it? Will there be any
major changes in my JMS client when it upgrades from 3 to 5?
It will be great if you can pinpoint me to any resources on the web that
I can read and research on.
thanks
KennyJDBC 10g works just fine against 9.2 database. See the interopeability matrix on the JDBC portal http://www.oracle.com/technology/tech/java/sqlj_jdbc/index.html
Kuassi - blog http://db360.blogspot.com/ -
Oracle.jms.AQjmsException when inserting large MessageMap message via JMS
Is there a limit on the number of items/size of message that can be placed on the AQ using the MessageMap message format?
Ive attempted to place 100 elements, each a small string of approximately 20 characters, into the AQ but I get the following error.
---> nested oracle.jms.AQjmsException: JMS-204: An error occurred in the AQ JNI layer
If I reduce the number of elements to about 70 the message is successfully queued.As long as the byte array obtained by serializing the JMSMapMessage
java object instance fits in a BLOB (max size 4 Gig) you should be able to
enqueue your message (providing the OS and/or the JVM can handle it).
Smaller map messages are stored inline in the table itself. Larger messages
are stored in a BLOB. It is likely that you do not have permissions to
write to the BLOB field of the OJMS MapMessage ADT.
To figure out the exact SQL exception turn tracing on by putting the following
lines of code in your OJMS client and recompiling.
AQjmsOracleDebug.setDebug(true);
AQjmsOracleDebug.setTraceLevel(5);
This will give you the exact SQL exception that is thrown.
-Vivek -
Jms client failure + reconnect
Hello,
I try to achieve the following setup - I have two (or more) queue readers on a Weblogic queue that share the load in the queue
for processing. They are unaware of each other presence.
They all read the message , do some subsequent processing that can take a couple of seconds
and finally do an explicit client acknowledgement.
This works fine in a uninterrupted situation where one sees that they both take part in processing a fair share of the load and all messages are processed.
However killing one of the participants (@work) seems to put the records in progress in some state @the server so that they are not available to the other still
working instance. Even restarting the original instance not always resolves the problem and still another restart is needed.
Could someone please explain the internal logic/rationale behind this (what happens exactly) and in what way the relevant settings (many) need
to be configured to remedy this?.
Currently we experience problems because these "stuck "records" are not delivered in a timely fashion.
Thanks in advance
Peter GeertsYour question is weblogic specific, but you are asking it in a general JMS forum. it's possible that someone here may have a lot of weblogic experience and know the answer to your question, but you'd probably be better off posting in a weblogic specific forum.
-
Oracle Lite and Oracle 8i Client on Win98
I've had Olite v8i running on my Win98 machine for a while now. I just installed Oracle 8i Client on my machine. Now, my JDBC driver for Oracle Lite does NOT work. What could have happened here??
Thanks.
-Jeremy
nullHI Jeremy,
I think, Your PATH was cranked up.
The JDBC driver for OLite normally does not use any OCI DLLs, so that should not be the problem. As I said, the OLite dlls may be missing now from the PATH.
Any error messages? "Does not work" is a bit... fuzzy. -
Unable to install Oracle XE Client on Ubuntu 8.04 - "no such user"
Hi,
I've just installed Oracle XE client on my desktop machine (64bit Ubuntu 8.04), and I had to manually create some users and groups:
sudo groupadd nobody
sudo groupadd oinstall
sudo useradd -s /bin/bash -g oinstall -G dba oracle
sudo passwd oracle
before the install would complete, due to what appears to be incorrect arguments to useradd by the installer.
It took quite a lot of hunting to find the above, and I'm a little concerned since no one else seems to have had the same problems.
I installed using:
$ sudo dpkg -i --force-architecture oracle-xe-client_10.2.0.1-1.0_i386.deb
(the force-architecture was required for the server install on my server, so I did the same here)
I read the install instructions on the oracle pages
(http://www.oracle.com/technology/software/products/database/xe/files/install.102/b25144/toc.htm#BABFEDEI) and didn't see anything about having to manually create these accounts, and I seem to have followed the rest of the instructions correctly.
What did I do wrong? I'm probably going to have to do it again sometime, and I'm a little concerned that I might have just been causing trouble for myself by doing those extra manual steps.
Note that I had to provide a password for the oracle user; how does oracle manage to log in using this account, since I didn't have to provide it anywhere?
Any help/advice would be appreciated,
many thanks,
William
BTW I'm really not happy with the preview/post message thing in this forum; I'm using Firefox 3.0.1 and if you use preview then the back button clears the entire text (yay, thanks!); I tried to be more cunning next time, and use the back button instead, but then none of the "preview", "post message" and "cancel" buttons work... so this was my third attempt at writing this message, and it's somewhat shorter than the original, like my patience :pBTW I'm really not happy with the preview/post
message thing in this forum; I'm using Firefox 3.0.1
and if you use preview then the back button clears
the entire text (yay, thanks!); I tried to be more
cunning next time, and use the back button instead,
but then none of the "preview", "post message" and
"cancel" buttons work...It's not Firefox related - same issue with other browsers.
Please put your entry regarding this into this thread:
Preview not working correctly - works now
That's the right place for this issue...
Cheers! -
I am trying to use the relatively new Code First from Database with the newest EF (6.x) and on an Oracle database (11g, but I have installed the newest ODTwithODAC). First of all, it works fine as long as the connection string is inside the App.Config file. But when I try to build it dynamically in the C# code (or rather, statically at the moment) it fails. I have it working with a dynamically built connection string when doing Model from Database though, so I'm at a loss right now.
First, I have created a second constructor for the context class that takes a string and does base(connectionString). Then I build the connection string via
OracleConnectionStringBuilder oracleBuilder = new OracleConnectionStringBuilder();
oracleBuilder.DataSource = "TEST.BLA.COM";
oracleBuilder.UserID = "ABC";
oracleBuilder.Password = "abc";
oracleBuilder.PersistSecurityInfo = true;
string connection = oracleBuilder.ToStrin();
Now trying to open an EntityConnection by giving to it this provider-specific connection string (or even the static one from the App.Config) doesn't work; I get "keyword not supported: user id"). Trying it by creating a context and giving this connection string doesn't work either. I'm pretty sure that this is because I didn't specify the provider to use; after all, it should use the Oracle.ManagedDataAccess.Client provider and not an SQL Server based one.
I then tried to get around this by using an EntityConnectionStringBuilder on top and specifying the provider keyword there, but then I get "keyword not supported: provider" when using it in the context constructor, and "the 'metadata' keyword is always required" when using it with the EntityConnection constructor.
As I said above: I bet it's the provider that I have to specify somehow, but I don't know how. The code that does work is the following:
using (var context = new Model())
context.Database.Connection.Open();
context.Database.Connection.Close();
When I read context.Database.Connection.ConnectionString, it is exactly the provider-specific connection string I created above, but I don't know where to specify the provider again. Do you know of any way to do this? Certainly there must be one.
PS: I have also posted this question on http://stackoverflow.com/questions/27979454/ef-code-first-from-database-with-managed-oracle-data-access-dynamic-connection because it is quite urgent and I'd like to use Code First from Database. Otherwise I'd have to go "back" to using Model from Database again, which is not ideal because we have updatable views where the .edmx-file has to be edited after every reload of the model, while with Code First from DB inserting into the view automatically works.I am trying to use the relatively new Code First from Database with the newest EF (6.x) and on an Oracle database (11g, but I have installed the newest ODTwithODAC). First of all, it works fine as long as the connection string is inside the App.Config file. But when I try to build it dynamically in the C# code (or rather, statically at the moment) it fails. I have it working with a dynamically built connection string when doing Model from Database though, so I'm at a loss right now.
First, I have created a second constructor for the context class that takes a string and does base(connectionString). Then I build the connection string via
OracleConnectionStringBuilder oracleBuilder = new OracleConnectionStringBuilder();
oracleBuilder.DataSource = "TEST.BLA.COM";
oracleBuilder.UserID = "ABC";
oracleBuilder.Password = "abc";
oracleBuilder.PersistSecurityInfo = true;
string connection = oracleBuilder.ToStrin();
Now trying to open an EntityConnection by giving to it this provider-specific connection string (or even the static one from the App.Config) doesn't work; I get "keyword not supported: user id"). Trying it by creating a context and giving this connection string doesn't work either. I'm pretty sure that this is because I didn't specify the provider to use; after all, it should use the Oracle.ManagedDataAccess.Client provider and not an SQL Server based one.
I then tried to get around this by using an EntityConnectionStringBuilder on top and specifying the provider keyword there, but then I get "keyword not supported: provider" when using it in the context constructor, and "the 'metadata' keyword is always required" when using it with the EntityConnection constructor.
As I said above: I bet it's the provider that I have to specify somehow, but I don't know how. The code that does work is the following:
using (var context = new Model())
context.Database.Connection.Open();
context.Database.Connection.Close();
When I read context.Database.Connection.ConnectionString, it is exactly the provider-specific connection string I created above, but I don't know where to specify the provider again. Do you know of any way to do this? Certainly there must be one.
PS: I have also posted this question on http://stackoverflow.com/questions/27979454/ef-code-first-from-database-with-managed-oracle-data-access-dynamic-connection because it is quite urgent and I'd like to use Code First from Database. Otherwise I'd have to go "back" to using Model from Database again, which is not ideal because we have updatable views where the .edmx-file has to be edited after every reload of the model, while with Code First from DB inserting into the view automatically works.
Maybe you are looking for
-
Can't view Cellular Data network on legally unlocked iPhone 3GS
I bought an iphone from Singapore and those phones come as unlock. Now that I am in the States, I was hoping to use my corporate AT&T sim card for data surfing and all. While I am able to make calls, it says that I am not registered for cellular data
-
Process: Pages [400] Path: /Applications/iWork '09/Pages.app/Contents/MacOS/Pages Identifier: com.apple.iWork.Pages Version: 4.3 (1048) Build Info: Pages-10480000~1 App Item ID: 409201541 App External ID: 9465
-
SUS - Purchase Order and Change Order Response
Hi, We have a requirement to display the Original PO and Changed PO in the list of PO's if the change PO is generated before the original PO has been confirmed. In other words, if there is a PO that was sent to Supplier and a change was made to th
-
Once I select the oject I want to extend and switch the button from move to extend it will not let me extend the object. It stays on move no matter what. Can you please help me resolve this issue?
-
Solaris 9 404 Upgrade to Solaris 10 on Ultra 10
I tried to do a Solaris 9 404 Upgrade to Solaris 10 on my Ultra 10 with SVM mirrored system drives and it wouldn't get past the Upgrade Profile Initialisation section. It stayed there for a long time, maybe 20 minutes and finally came up with a Faile