Persistence in jms

HI
I am using JBoss4.0 as application server and I am using jbossmq as messaging service.
I cannot seem to control the persistence behaviour of the server. I have edited the null-persistence.xml to avoid persisting to the database.. But persistence is still there even after setDelivaryMode to NON_PERSISTENCE in the client program.
Could anyone help me out
Sincerely yoursw
Jubin

Simply copying a persistent store's internal data into an existing persistent store won't work, and is not supported by BEA.
          To restore a JMS server's messages you either need to restart the host WL server; or, provided the WL server is up, restart the JMS server by resetting its target field (you can contact customer support for a program that does this automatically for you); or use WebLogic's migration facilities to migrate the JMS server to the running WebLogic server. If you do the latter and are using transactions, you will also need to migrate the transaction log. Search dev2dev for "BEA WebLogic JMS and JTA Migration Process Guide" for a white-paper on the topic.
          Actually, provided there are no JTA transaction records to worry about, I suppose simply changing the JMS server's target field so that it references the running WL server would do the trick (I'm not 100% sure). This can even be done programmatically (although I don't know how).
          Tom

Similar Messages

Qusetion on Persistence of JMS Messages in Weblogic 5.1

Hi All,
We have the following scenario in our project.The Weblogic Server 5.1 is running on 4 different m/c. And the same code is deployed in all those 4 different Weblogic Server. All the servers are connected to same database. Now we are using JMS and planning to use persistence in JMS. So if we create the JMS Tables (5 tables provided by BEA for JMS persistence) in Database and all the 4 different m/c s JMS queue access the same table , will there be any conflict/error? If the message stored by one server is retreived by another server then that it will be not a problem for us. Except this scenario will there be any problem? ( The jms queue is present in each and every m/c(but points to same DB tables)) . We have the requirement - No message should be picked up twice.
And does Weblogic 5.1 supports persistence in file system? If it supports then how to implement it?
Waiting for your reply.
Thanks
Srijeeb.

in a point to point messaging where you use que ,there is no question of picking up the message twice as it will be removed from the queue once it is pushed to the receiver . hope you are using clustering for the weblogic servers. then there should not be any issues due to 4 servers simultaneously accessing the database

Crazy JMS pattern

Hi,
I'm trying to implement this:
- JMS queue BS, named QUEUE, is request/response, it has a URI endpoint and a response URI endpoint
I have 3 proxy services working around this JMS queue, but for now I'm only working with two of them:
- PS 1: receives the http message and writes into the queue with transport outbound JMSMessageID = $body/messageid
- PS 3: an external entity now wants to communicate the response, and this PS routes into QUEUE response endpoint with transport outbound JMSCorrelationID = previous JMSMessageID
Is this possible to do?
I'm having an hard time implementing this, cause PS 1 just freezes and never correlates to the response.
I'm testing this using soapUI... making sure $body/messageid is common at all times.
Is there some tool to check messages (and headers) in JMS queues?
Can someone help me with this plz?

atheek1 I guess you are right.
However I still didn't manage to implement the desired correlation pattern.
I'm surely doing it wrong... but kinda running out of options.
I made two new JMS BS: requestQueue_BS and responseQueue_BS
Both are queues and text message type and requestQueue is JMSCorrelationID response pattern with response URI = responseQueue_BS
PS1 is any XML service that simply routes message to requestQueue using, inside routing, an transport header transformation of JMSCorrelationID to $body/id/text() on outbound request direction.
PS3 is any XML service that simply routes message to responseQueue using, inside routing, an transport header transformation of JMSCorrelationID to $body/id/text() on outbound request direction.
message body example is: <id>4324</id>
This doesn't work... what am I doing wrong?
PS1 just waits for the response... it doesn't matter how many times I trigger PS3 with the same JMSCorrelationID, PS1 just waits until it times out... :(
******* CONFIG FILES ************
requestQueue
<?xml version="1.0" encoding="UTF-8"?>
<xml-fragment xmlns:ser="http://www.bea.com/wli/sb/services" xmlns:tran="http://www.bea.com/wli/sb/transports" xmlns:http="http://www.bea.com/wli/sb/transports/http" xmlns:env="http://www.bea.com/wli/config/env" xmlns:jms="http://www.bea.com/wli/sb/transports/jms">
<ser:coreEntry isProxy="false" isEnabled="true">
<ser:binding type="abstract XML"/>
<ser:monitoring isEnabled="false">
<ser:aggregationInterval>10</ser:aggregationInterval>
</ser:monitoring>
<ser:sla-alerting isEnabled="true">
<ser:alertLevel>normal</ser:alertLevel>
</ser:sla-alerting>
</ser:coreEntry>
<ser:endpointConfig>
<tran:provider-id>jms</tran:provider-id>
<tran:inbound>false</tran:inbound>
<tran:URI>
<env:value>jms://localhost:7001/weblogic.jms.XAConnectionFactory/requestQueueRequest</env:value>
</tran:URI>
<tran:outbound-properties>
<tran:load-balancing-algorithm>round-robin</tran:load-balancing-algorithm>
<tran:retry-count>0</tran:retry-count>
<tran:retry-interval>30</tran:retry-interval>
<tran:retry-application-errors>true</tran:retry-application-errors>
</tran:outbound-properties>
<tran:provider-specific>
<jms:is-queue>true</jms:is-queue>
<jms:is-secure>false</jms:is-secure>
<jms:outbound-properties>
<jms:message-type>Text</jms:message-type>
<jms:expiration>0</jms:expiration>
<jms:enable-message-persistence>true</jms:enable-message-persistence>
<jms:response-required>true</jms:response-required>
<jms:response-URI>jms://localhost:7001/weblogic.jms.XAConnectionFactory/responseQueueRequest</jms:response-URI>
<jms:response-timeout>0</jms:response-timeout>
<jms:response-pattern>JMSCorrelationID</jms:response-pattern>
<jms:response-target-map>
<jms:target-pair>
<jms:target>AdminServer</jms:target>
<jms:destination/>
</jms:target-pair>
</jms:response-target-map>
<jms:pass-caller-subject>false</jms:pass-caller-subject>
</jms:outbound-properties>
<jms:request-encoding>UTF-8</jms:request-encoding>
</tran:provider-specific>
</ser:endpointConfig>
</xml-fragment>
and responseQueue
<?xml version="1.0" encoding="UTF-8"?>
<xml-fragment xmlns:ser="http://www.bea.com/wli/sb/services" xmlns:tran="http://www.bea.com/wli/sb/transports" xmlns:http="http://www.bea.com/wli/sb/transports/http" xmlns:env="http://www.bea.com/wli/config/env" xmlns:jms="http://www.bea.com/wli/sb/transports/jms">
<ser:coreEntry isProxy="false" isEnabled="true">
<ser:binding type="abstract XML"/>
<ser:monitoring isEnabled="false">
<ser:aggregationInterval>10</ser:aggregationInterval>
</ser:monitoring>
<ser:sla-alerting isEnabled="true">
<ser:alertLevel>normal</ser:alertLevel>
</ser:sla-alerting>
</ser:coreEntry>
<ser:endpointConfig>
<tran:provider-id>jms</tran:provider-id>
<tran:inbound>false</tran:inbound>
<tran:URI>
<env:value>jms://localhost:7001/weblogic.jms.XAConnectionFactory/responseQueueRequest</env:value>
</tran:URI>
<tran:outbound-properties>
<tran:load-balancing-algorithm>round-robin</tran:load-balancing-algorithm>
<tran:retry-count>0</tran:retry-count>
<tran:retry-interval>30</tran:retry-interval>
<tran:retry-application-errors>true</tran:retry-application-errors>
</tran:outbound-properties>
<tran:provider-specific>
<jms:is-queue>true</jms:is-queue>
<jms:is-secure>false</jms:is-secure>
<jms:outbound-properties>
<jms:message-type>Text</jms:message-type>
<jms:expiration>0</jms:expiration>
<jms:enable-message-persistence>true</jms:enable-message-persistence>
<jms:response-required>false</jms:response-required>
<jms:pass-caller-subject>false</jms:pass-caller-subject>
</jms:outbound-properties>
<jms:request-encoding>UTF-8</jms:request-encoding>
</tran:provider-specific>
</ser:endpointConfig>
</xml-fragment>
PS1
<?xml version="1.0" encoding="UTF-8"?>
<xml-fragment xmlns:ser="http://www.bea.com/wli/sb/services" xmlns:tran="http://www.bea.com/wli/sb/transports" xmlns:env="http://www.bea.com/wli/config/env" xmlns:http="http://www.bea.com/wli/sb/transports/http" xmlns:con="http://www.bea.com/wli/sb/stages/config">
<ser:coreEntry isProxy="true" isEnabled="true">
<ser:binding type="abstract XML"/>
<ser:monitoring isEnabled="false">
<ser:aggregationInterval>10</ser:aggregationInterval>
<ser:pipelineMonitoringLevel>Pipeline</ser:pipelineMonitoringLevel>
</ser:monitoring>
<ser:reporting>true</ser:reporting>
<ser:logging isEnabled="true">
<ser:logLevel>debug</ser:logLevel>
</ser:logging>
<ser:sla-alerting isEnabled="true">
<ser:alertLevel>normal</ser:alertLevel>
</ser:sla-alerting>
<ser:pipeline-alerting isEnabled="true">
<ser:alertLevel>normal</ser:alertLevel>
</ser:pipeline-alerting>
</ser:coreEntry>
<ser:endpointConfig>
<tran:provider-id>http</tran:provider-id>
<tran:inbound>true</tran:inbound>
<tran:URI>
<env:value>/ItevProj/proxy/test/3/ps1</env:value>
</tran:URI>
<tran:inbound-properties/>
<tran:all-headers>false</tran:all-headers>
<tran:provider-specific>
<http:inbound-properties/>
</tran:provider-specific>
</ser:endpointConfig>
<ser:router>
<con:flow xmlns:con="http://www.bea.com/wli/sb/pipeline/config">
<con:route-node name="RouteNode1">
<con:context/>
<con:actions>
<con1:route xmlns:con1="http://www.bea.com/wli/sb/stages/routing/config">
<con2:id xmlns:con2="http://www.bea.com/wli/sb/stages/config">_ActionId-9035043200913057533-78de896f.1287cc7514b.-7faf</con2:id>
<con1:service ref="ItevProj/business/common/jms/test/3/requestQueue" xsi:type="ref:BusinessServiceRef" xmlns:ref="http://www.bea.com/wli/sb/reference" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<con1:outboundTransform>
<con2:transport-headers xmlns:con2="http://www.bea.com/wli/sb/stages/transform/config">
<con3:id xmlns:con3="http://www.bea.com/wli/sb/stages/config">_ActionId-9035043200913057533-78de896f.1287cc7514b.-7da1</con3:id>
<con2:header-set>outbound-request</con2:header-set>
<con2:header name="JMSCorrelationID" value="expression">
<con3:xqueryText xmlns:con3="http://www.bea.com/wli/sb/stages/config">$body/id/text()</con3:xqueryText>
</con2:header>
</con2:transport-headers>
</con1:outboundTransform>
<con1:responseTransform/>
</con1:route>
</con:actions>
</con:route-node>
</con:flow>
</ser:router>
</xml-fragment>
PS3
<?xml version="1.0" encoding="UTF-8"?>
<xml-fragment xmlns:ser="http://www.bea.com/wli/sb/services" xmlns:tran="http://www.bea.com/wli/sb/transports" xmlns:env="http://www.bea.com/wli/config/env" xmlns:http="http://www.bea.com/wli/sb/transports/http" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:con="http://www.bea.com/wli/sb/pipeline/config" xmlns:con1="http://www.bea.com/wli/sb/stages/routing/config" xmlns:con2="http://www.bea.com/wli/sb/stages/config">
<ser:coreEntry isProxy="true" isEnabled="true">
<ser:binding type="abstract XML" xmlns:con3="http://www.bea.com/wli/sb/services/bindings/config"/>
<ser:monitoring isEnabled="false">
<ser:aggregationInterval>10</ser:aggregationInterval>
<ser:pipelineMonitoringLevel>Pipeline</ser:pipelineMonitoringLevel>
</ser:monitoring>
<ser:reporting>true</ser:reporting>
<ser:logging isEnabled="true">
<ser:logLevel>debug</ser:logLevel>
</ser:logging>
<ser:sla-alerting isEnabled="true">
<ser:alertLevel>normal</ser:alertLevel>
</ser:sla-alerting>
<ser:pipeline-alerting isEnabled="true">
<ser:alertLevel>normal</ser:alertLevel>
</ser:pipeline-alerting>
</ser:coreEntry>
<ser:endpointConfig>
<tran:provider-id>http</tran:provider-id>
<tran:inbound>true</tran:inbound>
<tran:URI>
<env:value>/ItevProj/proxy/test/3/ps3</env:value>
</tran:URI>
<tran:inbound-properties/>
<tran:all-headers>false</tran:all-headers>
<tran:provider-specific>
<http:inbound-properties/>
</tran:provider-specific>
</ser:endpointConfig>
<ser:router>
<con:flow>
<con:route-node name="RouteNode1">
<con:context>
<con2:varNsDecl namespace="http://webservice.chargingstation.itev.criticalsoftware.com" prefix="web"/>
</con:context>
<con:actions>
<con1:route>
<con2:id>_ActionId-9035043200913057533-78de896f.1287cc7514b.-7eb7</con2:id>
<con1:service ref="ItevProj/business/common/jms/test/3/responseQueue" xsi:type="ref:BusinessServiceRef" xmlns:ref="http://www.bea.com/wli/sb/reference"/>
<con1:outboundTransform>
<con3:transport-headers xmlns:con3="http://www.bea.com/wli/sb/stages/transform/config">
<con2:id>_ActionId-9035043200913057533-78de896f.1287cc7514b.-7d69</con2:id>
<con3:header-set>outbound-request</con3:header-set>
<con3:header name="JMSCorrelationID" value="expression">
<con2:xqueryText>$body/id/text()</con2:xqueryText>
</con3:header>
</con3:transport-headers>
</con1:outboundTransform>
<con1:responseTransform/>
</con1:route>
</con:actions>
</con:route-node>
</con:flow>
</ser:router>
</xml-fragment>

Problem faced while configuring the domain configuration in WLS 10.0

Hi all, I am trying to set up a Weblogic server 10.0 web application development environment in which we use persistence store, jms server, jms system module, subdeployments and jms system resources. when i configure everything and activate the changes, i get weird exception. but, i could not figure out why it happens. this is the exception
weblogic.store.io.jdbc.JDBCStoreException: [Store:280064]Expected empty table. (server="AdminServer" store="limJMSPersistentStore" table="limJMSWLStore")
     at weblogic.store.io.jdbc.JDBCStoreIO.initializeEmptyTable(JDBCStoreIO.java:656)
     at weblogic.store.io.jdbc.JDBCStoreIO.open(JDBCStoreIO.java:375)
     at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:327)
     at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:318)
It says weblogic.management.DeploymentException: The persistent store "limJMSPersistentStore" does not exist. but it is configured in the domain when i see in console. After that all the resources to jms system module also throws the below exception
weblogic.application.ModuleException: ERROR: Could not activate limJMSSystemModule!limLidbResponseQueue
reason is weblogic.messaging.kernel.KernelException: The Messaging Kernel limJMSServer has not yet been opened. I also have another problem with resource bundle properties file. weblogic server could not find the properties file. it throws MissingresourceException for all the properties file. i have placed the properties file inside DOMAIN_HOME/app_classes folder

Hi all,
The deployment failure of the "limJMSPersistenceStore" - jdbc store was the root cause. I use "limjms" prefix for this persistence store.It was not able to persist because of the data present in the "limJMSWLStore" table in the db schema. when i deleted all the rows and committed. then, restarted the server. Everything worked just fine :). Thanks!

Server boot takes a lot of time due to JMS persistence file store

Hi,
We're using WebLogic 9.2 on a windows machine.
Recently, we enhanced our application to work with JMS.
We're using 2 JMS servers on 2 different servers in a cluster, and working with distributed destinations.
We're using file store as our persistence store.
Lately, we found that server boot takes a lot of time due to actions which are performed on the file-store.
Analyzing this problem, we saw that the file size is ~2GB.
We understand that the file size does not shrink (unless manually compacted), and its size is matching the highest number ever of pending messages in the queues (like a high water-mark).
We also turned store debug on, using weblogic.Debug.DebugStoreIOPhysical, and we saw a lot of recovery logs after the file-store is opened.
We've checked and verified that our JMS transactions are completed successfully. We also verified that the number of pending and current messages is 0.
We've stopped the server gracefully, verifying there are no pending messages.
However, server boot repeatedly takes ~30 minutes due to heavy work done on the persistence store.
Compacting or removing the file store eliminates the delay.
However, we want to avoid manual operations every time we want to boot the server.
Please share your ideas.
Thanks,
Itsik

The only suggestions I have off the top of my head are:
* Ensure (1) the host system has at least 2GB (file store size) of free physical memory in addition to the memory used by current processes, and (2) the host system is not rebooted between each WebLogic restart. If you make sure of these two items, then the operating system will implicitly cache the store's file contents in memory even between boots -- when WebLogic subsequently boots the file store, the O/S should serve the file contents up much more quickly.
* Consider moving to a JDBC store. JDBC store runtime performance is lower, but since you have a typically only have a small amount of records to recover, boot performance should be higher in this case.
* Not that it helps your particular case, but it happens that we have boot performance enhancements in process for a future release (hopefully a near future release).
Tom

How to create OEMS JMS In-Memory and File-Based Persistence?

Anyone knows how to create OEMS JMS In-Memory and File-Based Persistence? Any help it is appreciated. I m working with Oracle BAM 11g TP4 and I want to test the capability of connecting directly to a JMS queue, and reading Oracle´s "complex" documentation I couldnt find the right way to make this happen.
tks

Hi Mario
This is explained in the soa developer's guide. Chapter 43 "Enterprise message source"should help you. You will find how to connect OEMS or JMS in-memory/file based to your BAM data objects with or without xpath transformation.
You can find sample of advanced XML formating in the 10g tech note: "Oracle BAM 10.1.3 configuration for BPEL 10.1.2 using JMS sensors" (useful even if you don't plan to use BPEL).
Anyway, if you plan to use BPEL, forget JMS and use the BAM adapter (chapter 42), it's quicker & easier.
Dominique

How to create OEMS JMS In-Memory and File-Based Persistence ? Anyone?

Anyone knows how to create OEMS JMS In-Memory and File-Based Persistence? Any help it is appreciated. I m working with Oracle BAM 11g TP4 and I want to test the capability of connecting directly to a JMS queue, and reading Oracle´s "complex" documentation I couldnt find the right way to make this happen.
tks

Hi Mario
This is explained in the soa developer's guide. Chapter 43 "Enterprise message source"should help you. You will find how to connect OEMS or JMS in-memory/file based to your BAM data objects with or without xpath transformation.
You can find sample of advanced XML formating in the 10g tech note: "Oracle BAM 10.1.3 configuration for BPEL 10.1.2 using JMS sensors" (useful even if you don't plan to use BPEL).
Anyway, if you plan to use BPEL, forget JMS and use the BAM adapter (chapter 42), it's quicker & easier.
Dominique

JMS P2P Persistence with Oracle

A couple of questions w.r.t Weblogic JMS p2p messagsing and persistence. I do realise
          that after configuring, via the console, a persistent store, that WL creates or requires two oracle tables: prefix.JMSStore and prefix.JMSState.
          Upon examining those tables in the ddl file,
          the fields in table have no reference to blobs? Where precisely are the messages destined for a queue stored? Secondly, do we
          have to create any additonal tables?
          Thanks.
          Jules


Don't Panic! ;-)
          No additional tables required - the data is stored in the "long raw"
          JMSStore.record field. Note that the schema and data formats are
          subject to change without notice between releases - (treat them as
          a black box)...
          Tom
          Jules Damji wrote:
          > A couple of questions w.r.t Weblogic JMS p2p messagsing and persistence. I do realise
          > that after configuring, via the console, a persistent store, that WL creates or requires two oracle tables: prefix.JMSStore and prefix.JMSState.
          >
          > Upon examining those tables in the ddl file,
          > the fields in table have no reference to blobs? Where precisely are the messages destined for a queue stored? Secondly, do we
          > have to create any additonal tables?
          >
          > Thanks.
          >
          > Jules

Migrating JMS Persistence from WLS 4.5.2 to WLS 6.1

Hi,
we are migrating several applications from WLS 4.5.2 to WLS 6.1. A application use
JMS with persistence in DB (JMS persistence WLS 4.5.2 is in DB) with WLS 6.1 we want
to change persistence mode to FIles. Therefore during migration process we have to
move the messages stored in the database to a file. The messages stored in the file
will be recovered for WLS 6.1.
My doubt is, Is there a automatic process for migrate messages in the DB to a persistence
file?
Thanks

Hi.
I'm not sure that there is an automatic process to accomplish this, but you might get a
better answer by posting this on the JMS newsgroup.
Regards,
Michael
Manuel Villalta wrote:
Hi,
we are migrating several applications from WLS 4.5.2 to WLS 6.1. A application use
JMS with persistence in DB (JMS persistence WLS 4.5.2 is in DB) with WLS 6.1 we want
to change persistence mode to FIles. Therefore during migration process we have to
move the messages stored in the database to a file. The messages stored in the file
will be recovered for WLS 6.1.
My doubt is, Is there a automatic process for migrate messages in the DB to a persistence
file?
Thanks--
Michael Young
Developer Relations Engineer
BEA Support

JMS Persistence with WLS 8.1SP3 in a cluster

I have been following the BEA recommendations. I have configured my JMS to write to an Oracle DB for JMS persistence. This is in a clustered environment. I have had one server go down and then come back. During the outage or right before the outage there were request in the JMS queue. I would assume when the server that failed came back up it would then receive and process the JMS request that were waiting in the DB. That doesn't seem to be happening. My setup is one JMS topic for out bound. The JMS queue is set up for internal traffic. It uses Message Beans. We are also using XADrivers.
The setup is WLS8.1SP3 on Solaris hitting an Oracle 9 db. Please forward me any questions or suggestions. Thank you in advance.

WebLogic JMS won't automatically recover messages that enter an "in-doubt" state due to persistence errors that occur while they are being sent or received. To recover such messages, JMS needs to be restarted. You can contact customer support for an 8.1 sample program that automatically restarts JMS (without restarting all of WebLogic) when this problem occurs.
Tom

JMS Database Persistence Provider in OC4J 10131:system cannot find the path

I'm walking through the steps here with OC4J standalone 10131:
http://mike-lehmann.blogspot.com/2006/09/simple-mdb-with-oracle-database-jms.html
And when I try to create the RA with a new RP I get the following exception in the logs. My datasource is setup and is tested. Thoughts?
oracle.sysman.ias.studio.j2ee.deploy.DeployUtil$DeploymentFailureException
     at oracle.sysman.ias.studio.j2ee.deploy.DeployUtil.deployArchive(DeployUtil.java:211)
     at oracle.sysman.ias.studio.j2ee.deploy.DeployUtil.deployArchive(DeployUtil.java:85)
     at oracle.sysman.ias.studio.oc4j.jms.JMXDeployDbProviderAdminBean.deployDBProviderAndConfigure(JMXDeployDbProviderAdminBean.java:121)
     at oracle.sysman.ias.studio.oc4j.jms.DeployDbProviderHelper.deployDBProvider(DeployDbProviderHelper.java:242)
     at oracle.sysman.ias.studio.oc4j.jms.DeployDbProviderHelper.handleEvent(DeployDbProviderHelper.java:127)
     at oracle.sysman.ias.studio.sdk.AbstractController.handleEvent(AbstractController.java:769)
     at oracle.sysman.emSDK.svlt.PageHandler.handleRequest(PageHandler.java:378)
     at oracle.sysman.emSDK.svlt.EMServlet.myDoGet(EMServlet.java:765)
     at oracle.sysman.emSDK.svlt.EMServlet.doGet(EMServlet.java:283)
     at oracle.sysman.ias.studio.app.StudioConsole.doGet(StudioConsole.java:297)
     at oracle.cabo.servlet.UIXServlet.doPost(Unknown Source)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
     at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
     at oracle.sysman.ias.studio.app.BrowserVersionFilter.doFilter(BrowserVersionFilter.java:75)
     at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:15)
     at oracle.sysman.ias.studio.app.MultipleJVMFilter.doFilter(MultipleJVMFilter.java:85)
     at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:17)
     at oracle.sysman.ias.studio.app.PostLogonFilter.doFilter(PostLogonFilter.java:80)
     at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:17)
     at oracle.sysman.ias.studio.app.ShortHostnameRedirectFilter.doFilter(ShortHostnameRedirectFilter.java:68)
     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:619)
     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:368)
     at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:866)
     at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:448)
     at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:216)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:117)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:110)
     at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
     at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:239)
     at oracle.oc4j.network.ServerSocketAcceptHandler.access$700(ServerSocketAcceptHandler.java:34)
     at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:880)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
     at java.lang.Thread.run(Thread.java:595)
Caused by: oracle.oc4j.admin.jmx.shared.exceptions.JMXRuntimeException: The system cannot find the path specified
     at oracle.oc4j.admin.jmx.shared.util.JarTool.<init>(JarTool.java:122)
     at oracle.sysman.ias.studio.j2ee.deploy.DeployPageUtil.getArchiveType(DeployPageUtil.java:105)
     at oracle.sysman.ias.studio.j2ee.deploy.DeployUtil.deployArchive(DeployUtil.java:133)
     ... 33 more
Caused by: java.util.zip.ZipException: The system cannot find the path specified
     at java.util.zip.ZipFile.open(Native Method)
     at java.util.zip.ZipFile.<init>(ZipFile.java:203)
     at java.util.jar.JarFile.<init>(JarFile.java:132)
     at java.util.jar.JarFile.<init>(JarFile.java:97)
     at oracle.oc4j.admin.jmx.shared.util.JarTool.<init>(JarTool.java:119)
     ... 35 more

gday Jason.
Not sure off the top of my head, looks like something is missing.
Caused by: java.util.zip.ZipException: The system cannot find the path specified
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.<init>(ZipFile.java:203)
at java.util.jar.JarFile.<init>(JarFile.java:132)
at java.util.jar.JarFile.<init>(JarFile.java:97)
at oracle.oc4j.admin.jmx.shared.util.JarTool.<init>(JarTool.java:119)
I'm not even sure what file is being deployed to create the RA/RP here, I'll see if I can find out.
-steve-

OIM 11g HA Configuring a Shared JMS Persistence Store

Hi Experts,
From the Oracle® Fusion Middleware High Availability Guide 11g Release 1 (11.1.1) Part Number E10106-09: http://download.oracle.com/docs/cd/E14571_01/core.1111/e10106/imha.htm#CHDGEDCI
Step 4 says:
On the Configuration tab, in the Directory field, enter the location of a persistent storage solution (such as NAS or SAN) that is available to other servers in the cluster. Specifying this location enables pending JMS messages to be sent.
Please helps me clarify how the storage (SAN in my case) is shared??, I think I need a NFS partition in the SAN, this partition is accesible, as mount point, in HOST1 and HOST2
Is it required a third-party solution, such as Veritas, to manage the shared filesystem???
My customer says that NFS is not recommended for this purpose, con someone send me documentation to clarify that
Best Regards

manin21 wrote:
Hi Experts,
From the Oracle® Fusion Middleware High Availability Guide 11g Release 1 (11.1.1) Part Number E10106-09: http://download.oracle.com/docs/cd/E14571_01/core.1111/e10106/imha.htm#CHDGEDCI
Step 4 says:
On the Configuration tab, in the Directory field, enter the location of a persistent storage solution (such as NAS or SAN) that is available to other servers in the cluster. Specifying this location enables pending JMS messages to be sent.
Please helps me clarify how the storage (SAN in my case) is shared??, I think I need a NFS partition in the SAN, this partition is accesible, as mount point, in HOST1 and HOST2
Is it required a third-party solution, such as Veritas, to manage the shared filesystem???
My customer says that NFS is not recommended for this purpose, con someone send me documentation to clarify that
Best RegardsYou need a shared filesystem. Doesn't matter how it's managed, that's up to you.

JMS persistence problem

          Hi,
          I have persistence half working on WLS6.1 Messages are being written to the database
          ok. When I crash the server, the message is still there. When I bring the server
          back up the message appears in the destination but is removed from the database.
          Therefore if the server crashes before the message is consumed it is lost.
          Any help appreciated.
          Fraser


The message appears in the destination but is removed
          from the database? That is strange behavior, and I
          have no explanation. I highly recommend contacting
          customer support. I also
          recommend trying the latest SP, just to see if that makes
          a difference.
          Tom, BEA
          Fraser wrote:
          > Hi,
          >
          > I have persistence half working on WLS6.1 Messages are being written to the database
          > ok. When I crash the server, the message is still there. When I bring the server
          > back up the message appears in the destination but is removed from the database.
          > Therefore if the server crashes before the message is consumed it is lost.
          >
          > Any help appreciated.
          > Fraser

JMS Persistence within WLPI 1.2.1

Hi,
We have just run some tests with persisted JMS messages into the WLPI Event Topic.
Messages arrive to start workflows and they appear in the JMSMESSAGE table within
the WLPI database. It all works rather nicely.
However, if we kill the WLPI server and restart it, persisted messages not yet
dealt with do not get picked up again by WLPI for processing. They just stay stuck
in the database. Thats not good. Any ideas intelligent peeps?
TIA
Chris

Chris
In 1.2.1 the best way to implement the solution was to write the message
to eventQueue not the topic. All messages that get posted to the topic
simply get processed by a MessageDrivenBean and forwarded to eventQueue
which in turn gets processed by the eventListener. The first step would be
to correct that problem.
Tony
"Chris Salisbury" <[email protected]> wrote in message
news:3bcc4913$[email protected]..
>
Hi,
We have just run some tests with persisted JMS messages into the WLPIEvent Topic.
Messages arrive to start workflows and they appear in the JMSMESSAGE tablewithin
the WLPI database. It all works rather nicely.
However, if we kill the WLPI server and restart it, persisted messages notyet
dealt with do not get picked up again by WLPI for processing. They juststay stuck
in the database. Thats not good. Any ideas intelligent peeps?
TIA
Chris

Viewing message from DB persistence JMS queue in oc4j

Hi,
I want to the actual message posted to the DB persistent JMS queue residing in oc4j container. In jdeveloper 10.1.3.4, i can see the posted messages in QTab for that queue in msgid column but it does not have actual message.
Please help in this.

I have used Both Java JMS Webservice wizard in JDeveloper to Insert a TextMessage in JMS queue and Java Code to do so.
Code Writing JMS Message to queue is as Follows:
try{
Hashtable environment=new Hashtable();
environment.put(Context.INITIAL_CONTEXT_FACTORY,"oracle.j2ee.rmi.RMIInitialContextFactory");
environment.put(Context.PROVIDER_URL,"opmn:ormi://url");
environment.put(Context.SECURITY_PRINCIPAL,"user");
environment.put(Context.SECURITY_CREDENTIALS,"pass");
Context context=new InitialContext(environment);
QueueConnectionFactory queueConnectionFactory=
(QueueConnectionFactory)context.lookup("jms/ESBQueueConnection1");
QueueConnection queueConnection=queueConnectionFactory.createQueueConnection();
queueConnection.start();
Queue queue=(Queue)context.lookup("jms/ESBQueue1");
QueueSession queueSession=
queueConnection.createQueueSession(false,Session.AUTO_ACKNOWLEDGE);
QueueSender queueSender=
queueSession.createSender(queue);
TextMessage mess1=queueSession.createTextMessage();
mess1.setText("HELLO MESSAGE");
queueSender.send(mess1);
queueSender.close();
queueSession.close();
queueConnection.close();
catch(JMSException ex) {
catch(NamingException ex) {
}

Persistence in jms

Similar Messages

Maybe you are looking for