JMS persistance issue

Hello All,
We are using JDBC persistance for JMS store. We are seeing messages getting corrupted. The only option is to delete / empty tables and re-start. We cann't afford to delete or loose messages which effects our service credibility.
Please note that our servers are clustered and uses Distributed Queues, and no dataStore is shared, and is configured as per BEA recommendation.
My questions to you are:
1. Can we use JDBC multi-Pool datasource (as we are using Oracle RAC), Ofcourse all datasource are non-XA
2. Why the messages are getting corrupted when suddenly DB goes down. Is there any way we can avoid empyting this table before re-starting.
Look forward to your reply.
Thanks

I hope the following helps:
Only multi-data-sources are supported, and they must be in "fail-over" mode. See the [ WebLogic RAC Documentation | http://download.oracle.com/docs/cd/E15523_01/web.1111/e13737/oracle_rac.htm#insertedID6 ] in the JDBC Admin Guide.
RAC itself must be setup to use synchronous replication (the default in recent versions).
Ensure that you don't have two JDBC stores that attempt to use the same backing table (this results in corruption, and normally WL detects this misconfiguration, but perhaps your setup has somehow disabled this protection). See [ the store admin chapter of the wl admin guide | http://download.oracle.com/docs/cd/E15523_01/web.1111/e13701/store.htm#CNFGD221 ].
Corruption is not expected or normal -- I recommend contacting customer support.
Tom

Similar Messages

In WL Cluster JMS Persistent Storefiles on local file system.

Hi Gurus,
We have Weblogic cluster 10.3.4.1 (3 nodes) on Linux 5 which is setup for Oracle Services Bus. Cluster has 3 machines configured. Currently JMS Persistent Storefiles are on shared file system but we are having some issue with the shared file system and wanna move JMS Persistent Storefiles on the local filesystem instead of shared file system. Is it possible in Clustered WL env or not.
Thanks All.

The data will be uploaded to the server and a PHP program will read the data and use it. I've already implemented it using JSON. I had to install a JSON stringifer and a JSON parser in a subfolder of configuration/shared/common/scripts. It's working well.
Thanks
mitzy_kitty

EntityManager.persist and JMS messaging issues?

Hi everyone:
I am seeing a problem that I could not figure out a solution. Can anyone shed me some lights on this?
I have a EJB method which basically does 2 things: 1). persists a record into a database table using EntityManager 2). sends out a message to a JMS topic. So it is th like:
myMethod() {
entityManager.persist(myObj);
notifier.notify(...);
The client will then listen to the JMS topic and read the new record from database. Usually this works pretty well, but sometimes, the client cannot find the new record from database at all and a few seconds later it can. It is as if there is a delay between the JMS messaging and database persistence - somehow the client receives the message first and at this time the record is not really saved into database yet!
Can anyone explain to me what is going on here? What kind of solutions might help to resolve this?
BTW, I am using the Hibernate EntityManager. My app server is Glassfish.
Thanks a lot for your help
jmao

You need to use flush method to persist the value before you calling notifier.notify(...);
below code should works
myMethod() {
entityManager.persist(myObj);
*entityManager.flush();</<br />
notifier.notify(...);
}

JMS Persistance Store "WLStore"

JMS Persistence Store was using WLStore table, to persist the JMS message, but on production server restart the Weblogic is not able to read that WLStore Table anymore and giving below Error.
<WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Error> <Store> <BEA-280072> <JDBC store "JMSJDBCStore" failed to open table "WLStore".
All help is appreciated.
Thanks
Anand.

Hi Anand,
There must be more information about this error in the log like a exception stacktrace. This error may come due to many reasons so complete error info would be required to identify the exact problem.
As it is a production issue so I would suggest you to raise a SR with support. Cross post your question in weblogic forum to get better response -
WebLogic Server - General
Regards,
Anuj

Embedded JMS/OC4J issue while running an application in Jdeveloper 10.1.3.2

Hi,
I am facing an issue while running an application on my laptop.I downloaded Jdeveloper 10.1.3.2.Installed Jheadstart along with that.
Created a new application specified in HR demo.When I run the application I get following messages,After that it does not show my application pages.It does not even open browser window.
[waiting for the server to complete its initialization...]
Aug 29, 2007 6:01:47 PM com.evermind.server.jms.JMSMessages log
INFO: JMSServer[]: OC4J JMS server recovering transactions (commit 0) (rollback 0) (prepared 0).
Aug 29, 2007 6:01:47 PM com.evermind.server.jms.JMSMessages log
INFO: JMSServer[]: OC4J JMS server recovering local transactions Queue[jms/Oc4jJmsExceptionQueue].
07/08/29 18:01:55 Oracle Containers for J2EE 10g (10.1.3.1.1) initialized
When I delete persistnce directory files under embedded oc4j (specifically jms.state), It logs following messages.But it does not run my application pages and not even open browser window to display some error.
[Starting OC4J using the following ports: HTTP=8988, RMI=23891, JMS=9227.]
C:\jdevstudio10132\jdev\system\oracle.j2ee.10.1.3.40.66\embedded-oc4j\config>
C:jdevstudio10132\jdk\bin\javaw.exe -client -classpath C:jdevstudio10132\j2ee\home\oc4j.jar;C:jdevstudio10132\jdev\lib\jdev-oc4j-embedded.jar -Xverify:none -XX:MaxPermSize=256m -DcheckForUpdates=adminClientOnly -Doracle.application.environment=development -Doracle.j2ee.dont.use.memory.archive=true -Doracle.j2ee.http.socket.timeout=500 -Doc4j.jms.usePersistenceLockFiles=false oracle.oc4j.loader.boot.BootStrap -config C:\jdevstudio10132\jdev\system\oracle.j2ee.10.1.3.40.66\embedded-oc4j\config\server.xml
[waiting for the server to complete its initialization...]
07/08/29 18:06:16 Oracle Containers for J2EE 10g (10.1.3.1.1) initialized.
I tried by creating another standalone application with simple html page, it throws same logs and does not show up browser window.I even tried with Jdeveloper 10.1.3.3, but still same issue .
can you please throw some light on this issue and any suggestion for resolutions.
Thanks.

Can someone throw somelight on this issue?
I posted the same issue in Jdeveloper forum but did not receive any reply .appreciate your suggestions.
Thanks
Sekar.

JMS/OC4J issue while running an application in Jdeveloper 10.1.3.2/10.1.3.3

Hi,
I am facing an issue while running an application on my laptop.I downloaded Jdeveloper 10.1.3.2.Installed Jheadstart along with that.
Created a new application specified in HR demo.When I run the application I get following messages,After that it does not show my application pages.It does not even open browser window.
[waiting for the server to complete its initialization...]
Aug 29, 2007 6:01:47 PM com.evermind.server.jms.JMSMessages log
INFO: JMSServer[]: OC4J JMS server recovering transactions (commit 0) (rollback 0) (prepared 0).
Aug 29, 2007 6:01:47 PM com.evermind.server.jms.JMSMessages log
INFO: JMSServer[]: OC4J JMS server recovering local transactions Queue[jms/Oc4jJmsExceptionQueue].
07/08/29 18:01:55 Oracle Containers for J2EE 10g (10.1.3.1.1) initialized
When I delete persistnce directory files under embedded oc4j (specifically jms.state), It logs following messages.But it does not run my application pages and not even open browser window to display some error.
[Starting OC4J using the following ports: HTTP=8988, RMI=23891, JMS=9227.]
C:\jdevstudio10132\jdev\system\oracle.j2ee.10.1.3.40.66\embedded-oc4j\config>
C:jdevstudio10132\jdk\bin\javaw.exe -client -classpath C:jdevstudio10132\j2ee\home\oc4j.jar;C:jdevstudio10132\jdev\lib\jdev-oc4j-embedded.jar -Xverify:none -XX:MaxPermSize=256m -DcheckForUpdates=adminClientOnly -Doracle.application.environment=development -Doracle.j2ee.dont.use.memory.archive=true -Doracle.j2ee.http.socket.timeout=500 -Doc4j.jms.usePersistenceLockFiles=false oracle.oc4j.loader.boot.BootStrap -config C:\jdevstudio10132\jdev\system\oracle.j2ee.10.1.3.40.66\embedded-oc4j\config\server.xml
[waiting for the server to complete its initialization...]
07/08/29 18:06:16 Oracle Containers for J2EE 10g (10.1.3.1.1) initialized.
I tried by creating another standalone application with simple html page, it throws same logs and does not show up browser window.I even tried with Jdeveloper 10.1.3.3, but still same issue .
can you please throw some light on this issue and any suggestion for resolutions.
Thanks.

I am also facing the same issue on my laptop. I searched for forum but no luck.
appreciate if anybody can throw some light on this.

BPEL process failing in many instances due to JMS performance issue...

Hi All,
We are using a JMS adapter as partner link in a BPEL process to produce messages to JMS Queue.
We are getting an error while producing a message to a JMS Queue.
The error comes for 1 or 2 instances among 5 to10 intsances. (all these instances ran with in 1 or 2 seconds).
We are using Oracle 10G SOA suite.
This error is getting in the Production environment.
The error is as follows (took error from server log).
Failed to handle dispatch message ... exception ORABPEL-05002
Message handle error.
An exception occurred while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the exception is: faultName: {{http://schemas.oracle.com/bpel/extension}bindingFault}
messageType: {{http://schemas.oracle.com/bpel/extension}RuntimeFaultMessage}
parts: {{summary=file:/sw/appaia/product/SOA/bpel/domains/default/tmp/.bpel_CurrencyExchangeListEbizJMSProducer_1.0_4ec528ec93a8a6ff0278fab9701dcc71.tmp/CurrencyExchangeListEbizJMSProducerV1.wsdl [ Produce_Message_ptt::Produce_Message(OutputParameters) ] - WSIF JCA Execute of operation 'Produce_Message' failed due to: Adapter Framework unable to create outbound JCA connection.
file:/sw/appaia/product/SOA/bpel/domains/default/tmp/.bpel_CurrencyExchangeListEbizJMSProducer_1.0_4ec528ec93a8a6ff0278fab9701dcc71.tmp/CurrencyExchangeListEbizJMSProducerV1.wsdl [ Produce_Message_ptt::Produce_Message(OutputParameters) ] - : The Adapter Framework was unable to establish an outbound JCA connection due to the following issue: oracle.j2ee.connector.proxy.ProxyInterceptException: javax.resource.ResourceException: RollbackException: Transaction has been marked for rollback: null [Caused by: RollbackException: Transaction has been marked for rollback: null]
; nested exception is:
ORABPEL-12511
Adapter Framework unable to create outbound JCA connection.
I tried the below JMS tunings with differnt combination, but no improvem
Please let me know if any other logs or any other information is required.
Thanks,
Pershad

One of the values in the oc4j-ra.xml has the below values:
<connector-factory location="OracleASjms/MyXAQCF" connector-name="OracleASjms">
          <config-property name="jndiLocation" value="jms/XAQueueConnectionFactory"/>
          <config-property name="autoCloseSession" value="false"/>
          <connection-pooling use="private">
               <property name="waitTimeout" value="300" />
               <property name="scheme" value="fixed_wait" />
               <property name="maxConnections" value="50" />
               <property name="minConnections" value="0" />
          </connection-pooling>
          <security-config use="principal-mapping-entries">
               <principal-mapping-entries>
                    <principal-mapping-entry>
                         <initiating-user>servletuser</initiating-user>
                         <res-user>jmsuser</res-user>
                         <res-password>->jmsuser</res-password>
                    </principal-mapping-entry>
               </principal-mapping-entries>
          </security-config>
          <connectionfactory-interface>javax.jms.XAQueueConnectionFactory</connectionfactory-interface>
     </connector-factory>
Where do we need to change ?
Please suggest .
Thanks

Receiver JMS adapter issue in PI 7.1

Hi All,
We are using JMS receiver adapter for one of our scenarios. I'm facing different type of issue in production system
Issues:
If the channel is functioning the messages are successfully delivering to end system. If there are NO messages for long time the channel is not sending any message to end system and messages are getting failed in PI.
If i STOP and START the channel after few minutes channel able to deliver the messages.
I'm not not able to figure out where the issue is causing.
Please assist me to get ride of this issue.
Thanks in advance
- VR

Hello Rajesh and all,
Below is the error message i'm receiving. This issue is happens when there is no message flow for few hours and when a new message comes adapter channel in RWB through below error message.
Please assist with inputs
Message processing failed. Cause:com.sap.engine.interfaces.messaging.api.exception.MessagingException:Connector for ConnectionProfile of Channel:IN_JMS_xxxx
node:xxxx havingobject id:xxxxxxx encountered error:MQJMSxxx:an internal error has occured. Please contact your system administrator. Detail: com.ibm.mqservices.MQInternalException:MQJE001:
An MQException occurred:Completion Code 2,Reason 2195 MQJE046:Unsupported codeset:0 in sending to destination queue:///xxxxxx.QUEUE?targetClient=1, the message message:JMS Message class:jms_txt JMSType: null
JMSDeliveryMode:2 JMSExpiration:0 JMSPriority: 4 JMSMessageID: null JMSTimestamp: 0

Jms adapter issue

PI 7.31 is getting issue while connecting to Webshere MQ version 6.0.2.10.
The error in JMS sender communication channel is - "Error connecting due to missing class com.ibm.mq.jms.MQQueueConnectionFactory. Please ensure all resources are present in JMS provider library : com.sap.aii.adapter.lib.sda"
Few weeks back, MQ jar files were deployed by Basis.
I have attached jar file content. Do we have to deploy different jar files,the jar files are of websphere mq 6.0.2.10.
They were deployed on com.sap.aii.adapter.lib.sda
rgds

Hi ,
Go through below links once.
Receiver JMS Adapter Communication channel Error
JMS inbound and outbound queue
Regards
Venkat

JMS Dequeue issue -- OSB

Hi,
We have created a JMS Queue in WLS 10.3.0 and OSB (10.3.1) process is using proxy service - JMS transport to dequeue messages.
WLS JMS Queue -->OSB Proxy --> Business Service (JCA Db adapter) to insert data into a table
IF error in db --> Invoke OSB error handler and write to a file
Case - Success
Messages are deleted from the queue
Case - Failure
Messages are not deleted from the queue. Error handler is invoked in OSB and messages are written to a file.
This is creating an issue since OSB retries and number of files are created. We have tried setting retry settings in OSB, but in vain.
Please provide inputs, this is a bit of emergency.
Regards,
AP
Edited by: ARPL on Oct 15, 2009 3:41 AM

Am also dumb...
You need to create a new proxy service (and select the message type which suits your process, anysoap any xml, wsdl, etc), on the second tab you can select the transport.
In here select jms from the listbox and for the endpoint insert "jms://yourhost:yourpost/yourconnectionfactory/yourqueue"
thats all what is needed to let your proxy service pick up the messages from the queue.
eventually you want to route this message to something else, so for that you need to decide what sort of business service you use (webservice wsdl based, or just some other jms endpoint,or file...you name it)
@@JMS implementation in OSB
OSB concepts are really hard to digest if u r SOA developer from start. Proxy Service will act as a Inbound for JMS. It still shows the "Destination type" in JMS Transport Config tab
Really Confussing....
Sushil
Edited by: Sushil Deshpande on Jan 26, 2011 2:22 AM

JMS channel issue

Hi
My XI system is set-up with alerts frame-work and we are able to raise almost all the system generated alerts. But we are facing one issue with JMS channel alerts. Lets me explain the problem.
We have a JMS channel connected to JMS Server and we are publishing the messages on JMS queue. When JMS server is down, the channel status is not turning into red and it is staying in gree only. If we see the messages in adapter engine (through message monitoring) they are in delivering mode and they are not going into system error state. So either of the things are not triggering any system alerts. So are there any parameters that we can set-up in JMS channel or somewhere so that when JMS server is down, we can raise the system alerts ?? We are using the EMS server for hosting the JMS queues.
thanks
kumar

Hi Moorthy
yes! as you said, my main problem is..... channel is not turning into red, eventhough my JMS server is down and there by not able to raise the alert in either of the two cases. (Adapter Engine based standard alerts or CCMS Alerts). Is there any option to set through which when jms server is down, channel will become red ??
thanks
kumar

JMS/JTA issue is case of a server crash

          Hi All
          I am having some JMS/JTA related issue in case of a server crash. This is there
          for both 6.1 and 7.0. Its like this - an MDB is getting data from a Queue and
          its CMT [ie JTA]. Now when the MDB has the onMessage call back that time a usertransaction
          has been opened by the JMS framework of WLS 7.0/6.1. Now when the onMessage block
          is executing if the server crashes - before the TX has been rolled back/commited
          then next time when that server is restarted that message does mot appear on the
          Queue for 4-5 minutes and the Queue shows the message in "Bytes Pending". So the
          user has to wait for 4-5 minutes before getting back the message. In this time
          period whatever u try - like use QueueBrowser /QueueReceiver to find the message
          shows no result. This is something to do with JTA/JMS combination.
          Is there anyway to control this "invisible time" of the message? This is causing
          a lot of problem in our user base.
          thanks
          Anamitra


I don't think there are any issues. You might get more info from the
          transaction newsgroup and/or customer support.
          Tom
          Anamitra wrote:
          > Hi Tom
          > thats good - but this brings another question. If that was to be reduced are there
          > any side effects that I should be aware of?
          > thanks
          > Anamitra
          >
          > Tom Barnes <[email protected]> wrote:
          >
          >>This is a FAQ, but is not in the FAQ.
          >>
          >>1) As an enhancement, the transaction recovery delay has been reduced,
          >>
          >>or even eliminated in 8.1.
          >>
          >>2) There are plans to back-port this reduction to 7.0 - I think the
          >>back-port is already available. Contact customer support.
          >>
          >>3) Meanwhile, there is somewhat of a work-around. You can reduce the
          >>
          >>recovery delay to as little as 60 seconds by setting
          >> RecoveryThresholdMillis="60000"
          >>in the "JTA" section of your config.xml, programmatically via JMX on
          >>the
          >>"JTAMBean".
          >>
          >>Tom
          >>
          >>Anamitra wrote:
          >>
          >>>Hi All
          >>>I am having some JMS/JTA related issue in case of a server crash. This
          >>
          >>is there
          >>
          >>>for both 6.1 and 7.0. Its like this - an MDB is getting data from a
          >>
          >>Queue and
          >>
          >>>its CMT [ie JTA]. Now when the MDB has the onMessage call back that
          >>
          >>time a usertransaction
          >>
          >>>has been opened by the JMS framework of WLS 7.0/6.1. Now when the onMessage
          >>
          >>block
          >>
          >>>is executing if the server crashes - before the TX has been rolled
          >>
          >>back/commited
          >>
          >>>then next time when that server is restarted that message does mot
          >>
          >>appear on the
          >>
          >>>Queue for 4-5 minutes and the Queue shows the message in "Bytes Pending".
          >>
          >>So the
          >>
          >>>user has to wait for 4-5 minutes before getting back the message. In
          >>
          >>this time
          >>
          >>>period whatever u try - like use QueueBrowser /QueueReceiver to find
          >>
          >>the message
          >>
          >>>shows no result. This is something to do with JTA/JMS combination.
          >>
          >>>Is there anyway to control this "invisible time" of the message? This
          >>
          >>is causing
          >>
          >>>a lot of problem in our user base.
          >>>
          >>>thanks
          >>>Anamitra
          >>
          >

How to create a JMS persistent file store using WLST in WLS 9.0?

Anybody have a good example of this? When I try to create a fileStore and set it on my jms server I am getting the following error: "TypeError: setPersistentStore(): 1st arg can't be coerced to weblogic.management.configuration.PersistentStoreMBean'
Thanks :)

Hi,
First Create Persistent Store ( FileStore / JDBCStore).
File Store Creation is as follows:
Store = create("PStore","FileStore")
Set it's File Directory and Targets.
then Create JMS Server and set its Persistent Store as File Store. Set JMS Server Target.

JNDI Lookup for JMS Topic issue.......!

Hi,
          Our application is deployed on two nodes (MS1 and MS2 in a cluster) and I created JMSServer on MS1, JMS ConnectionFactory and Distributed Topic are targeted on both MS1 and MS2 i.e on entire cluster.
          We have the JMS Code in postStart() method of starup class which extends ApplicationLifecycleListener which would create the JMS Subcriber and set the message listener on to it.
          code snippet:
               System.out.println("createSubscriber called");
               subSession = topicConnection.createTopicSession(false, Session.AUTO_ACKNOWLEDGE);
               // Lookup for the Topic
               Topic cadTopic = (Topic) ctx.lookup("JMSTopicLog4j");
               System.out.println("Topic is: " + cadTopic.getTopicName());
               // Create JMS Subscriber.
               cadSubscriber = subSession.createSubscriber(cadTopic);
               // Set the listener to Subscriber.
               cadSubscriber.setMessageListener(new CADMessageListener());
               topicConnection.start();
          When I start the cluster (managed Servers MS1 and MS2) for the first time and deploy the application on them (entire cluster) it works well i.e. message listener is active and able to receive messages published by publisher but when I try to stop and start MS2 it gives the following exception during server startup
          javax.naming.NameNotFoundException: Unable to resolve 'JMSTopicLog4j'. Resolved ''
          javax.naming.NameNotFoundException: Unable to resolve 'JMSTopicLog4j'. Resolved ''; remaining name 'JMSTopicLog4j'
          at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1123)
          at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:250)
          at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:171)
          at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:204)
          at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:267)
          at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:362)
          Note: I thought my application context is getting started before JNDI tree is loaded but I could see that it is able to lookup the ConnectionFactory and throws the given exception when it comes to lookup code of JMS Topic.
          is there any configuration issue or am I missing something? Please help me in this regard.
          Thanks in advance.
          Kris.

Very interesting, I mean in the sense that we have the same setup, but instead of topic we are using the queues.
          And our problem is exactly the same,deployment works but after restart same javax.naming.NameNotFoundException happens on server 2.

Sun Application Server Platform Edition 8.2 JMS Ordering Issue

Hi -
I have an issue where messages I have put on a JMS queue are appearing in my MDB in the wrong order.
I am creating a session, and using that session to send 2 messages to the same queue (first msg A, then msg B).
Usually A appears in the MDB onMessage method first, but sometimes B does !
This contradicts what is said in the manual for the Sun One Message Queue
see http://docs.sun.com/source/817-0354-10/overview.html, at the bottom of this page.
I can provide any of the details of my code or the Connection Factory if required.
Thanks in advance for any suggestions
Andrew

What exactly are the symptoms of the crash? If it's actually a crash and a core dump, then if you can provide more details on that (hs_err_pid file and any associated messages), we can file a bug against the JVM. If you get memory exceptions, what specifically do they say?
Also, which JVM are you actually using? There are some known bugs with JDK 1.5.0_06 and earlier around memory and file descriptor usage; we recommend that you use JDK 1.5.0_09 or a JDK 6.0 beta. For that matter, you will see better performance in general with version 9.0 of the appserver
-Scott

JMS persistance issue

Similar Messages

Maybe you are looking for