JMS persistancy

          I am using wl5.1 and AS400 as DB. In my application which uses JMS, I use persistant
          store in P2P model. The object seem to persist and whenever my listerner gets
          started they are read from the queue and processed.
          But in cases where I store the data and start the listener after a day the listener
          does not read the data. The destinations ID seem to vary between the data's already
          stored and the one which i am trying to store now. The objects currently stored
          are read and the ones stored previously are not read.
          what could be the cause for this behaviour?
          Thanks
          Krish.

Krish,
          Post this to the JMS newsgroup.
          krish wrote:
          > I am using wl5.1 and AS400 as DB. In my application which uses JMS, I use persistant
          > store in P2P model. The object seem to persist and whenever my listerner gets
          > started they are read from the queue and processed.
          >
          > But in cases where I store the data and start the listener after a day the listener
          > does not read the data. The destinations ID seem to vary between the data's already
          > stored and the one which i am trying to store now. The objects currently stored
          > are read and the ones stored previously are not read.
          >
          > what could be the cause for this behaviour?
          >
          > Thanks
          > Krish.

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

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.

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

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

JMS Persistent Mode (can I use alternate provider, ie database)

When I am using JMS Persistence in Queued messages or PubSub, can I use an alternate form of persistence.
In other words can I run persistence thru a database like DB2 or Oracle, instead of the native support by the SAP engine.
I dont mean using MQSeries or another JMS provider, but rather having the SAP JMS connect to DB2 or Oracle to provide a more robust form of persistence.
Is that possible ?
Thanks, John

Hello John,
Yes, that was exactly what I meant. In the download section there is a Sneak preview with Linux and DB2.
I think that the Sneak preview was available for MS-SQL as well while the official versions support more DBMS-s. However I am certainly no expert on the installation, I have just small JMS experience and I was trying to help.
Please have a look at :
SAP WAS 6.40 for Oracle
where another user was asking about possible installations.
Best Regards
Peter

Migration of JMS Queues from Weblogic 10.3 to 12c

Hi - We are currently planning to move our JMS Queues from existing 10.3 server to 12c and for the same we are looking for some feedback :
We need to define a rollback strategy in case our migration to 12c does not work well and we need to revert back to using weblogic 10.3. Are messages sent to weblogic 12c backward compatible with version 10.3? As part of rollback, business would want to drain out any remaining messages from 12c and feed them back to 10.3 queues to allow them for processing. Is this feasible? If yes then, could you please suggest how, If not then could you please suggest a strategy for rollback and process remaining messages in 12c?
We would also want to know if we can keep the same Database for both 10.3 and 12c JMS persistent stores for the same queues or should we define a completely new DB? With weblogic we can define prefixes for the DB stores which would make queue tables to have different names between 10.3 and 12c for same queues. However we are not sure if there are any other internal tables that JMS creates in the persistent stores DB, not using these prefixes, which would then corrupt the data since both 10.3 and 12c tables would be on the same DB.
Thanks
Nitin

Hello,
the final release for WLP is 10.3.6, running on WebLogic Server 10.3.6.
Emmanuel

Microsoft SQL Server JDBC driver and WLS JMS problem?

          Greetings,
          I'm using the Microsoft SQL Server JDBC driver with WLS with JMS
          persisted to SQL Server, during WLS startup the JMS attempts to
          read the JMSStore and JMSState tables in the db, if they are
          already present (say, from a previous run) the driver kicks out:
          java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]ResultSet can
          not re-read row data for column 1.
          If the tables are not present, then WLS creates them and
          everything proceeds fine. Now, its not a good thing to attempt
          to reread row data for a ResultSet, especially for portability. Why is WLS JMS
          doing this? is there some config I can use to adjust JMS startup behavior for
          persisted JMS stores?
          Jay Houghton
          Centiv
          [email protected]
          long exception trace follows:
          <Oct 1, 2002 8:29:11 AM EDT> <Info> <JMS> <User connection factory "BroadcastTopicFactory"
          is started.>
          <Oct 1, 2002 8:29:18 AM EDT> <Info> <JMS> <JMSServer "EnergizerJMSServer", Opening
          JDBC store tables "JMSStore
          " and "JMSState" using connection pool "JMSConnectionPool".>
          <Oct 1, 2002 8:29:20 AM EDT> <Alert> <JMS> <JMSServer "EnergizerJMSServer", store
          failed to open, java.io.IOEx
          ception: JMS JDBC store, connection pool = <JMSConnectionPool>, prefix = <null>:
          recover
          java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]ResultSet can
          not re-read row data for colum
          n 1.
          at com.microsoft.jdbc.base.BaseResultSet.getLong(Unknown Source)
          at com.microsoft.jdbc.base.BaseResultSet.getLong(Unknown Source)
          at weblogic.jdbc.pool.ResultSet.getLong(ResultSet.java:304)
          at weblogic.jms.store.JDBCIOStream.doRecover(JDBCIOStream.java:618)
          at weblogic.jms.store.JDBCIOStream.recover(JDBCIOStream.java:728)
          at weblogic.jms.store.JMSStore.recover(JMSStore.java:112)
          at weblogic.jms.backend.BEStore.open(BEStore.java:179)
          at weblogic.jms.backend.BackEnd.initialize(BackEnd.java:330)
          at weblogic.jms.JMSService.createBackEnd(JMSService.java:923)
          at weblogic.jms.JMSService.addJMSServer(JMSService.java:1277)
          at weblogic.jms.JMSService.addDeployment(JMSService.java:1174)
          at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
          at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:279)
          at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:23
          3)
          at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:193)
          at java.lang.reflect.Method.invoke(Native Method)
          at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:608)
          at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:592)
          at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:352)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:449)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:190)
          at $Proxy40.updateDeployments(Unknown Source)
          at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub
          .java:2734)
          at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:362
          at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:154)
          at java.lang.reflect.Method.invoke(Native Method)
          at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:608)
          at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:592)
          at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:352)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:449)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:190)
          at $Proxy57.start(Unknown Source)
          at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean
          _CachingStub.java:480)
          at weblogic.management.Admin.startApplicationManager(Admin.java:1151)
          at weblogic.management.Admin.finish(Admin.java:571)
          at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:508)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
          at weblogic.Server.main(Server.java:35)


          Tom,
          thanks for the info, I'll bring this to support.
          I did try the weblogic jDriver for SQL Server and it works fine, so i think it
          must be the way JMS is interacting with the MS driver.
          here are my components:
          WLS 6.1sp1
          Microsoft® SQL Server™ 2000 Driver for JDBC™ is a (Type 4 JDBC) which provides
          partial JDBC 2 support (no blobs, clobs, etc)
          MS SQL Server 2000 (sp2?)
          thanks!
          Jay Houghton
          [email protected]
          Tom Barnes <[email protected]> wrote:
          >Hi Jay,
          >
          >This is not a known issue at BEA as far as I know, perhaps it is the
          >result
          >of a new driver/database combination. Try using a different driver,
          >or a different
          >version of the current driver. Meanwhile, use a file store (just as
          >reliable but faster) and log a case with customer support, including
          >information on your version, service-pack, and what driver you are using.
          >
          >Tom, BEA
          >
          >Jay Houghton wrote:
          >
          >> Greetings,
          >>
          >> I'm using the Microsoft SQL Server JDBC driver with WLS with JMS
          >> persisted to SQL Server, during WLS startup the JMS attempts to
          >> read the JMSStore and JMSState tables in the db, if they are
          >> already present (say, from a previous run) the driver kicks out:
          >>
          >> java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]ResultSet
          >can
          >> not re-read row data for column 1.
          >>
          >> If the tables are not present, then WLS creates them and
          >> everything proceeds fine. Now, its not a good thing to attempt
          >> to reread row data for a ResultSet, especially for portability. Why
          >is WLS JMS
          >> doing this? is there some config I can use to adjust JMS startup behavior
          >for
          >> persisted JMS stores?
          >>
          >> Jay Houghton
          >> Centiv
          >> [email protected]
          >>
          >> long exception trace follows:
          >>
          >> <Oct 1, 2002 8:29:11 AM EDT> <Info> <JMS> <User connection factory
          >"BroadcastTopicFactory"
          >> is started.>
          >> <Oct 1, 2002 8:29:18 AM EDT> <Info> <JMS> <JMSServer "EnergizerJMSServer",
          >Opening
          >> JDBC store tables "JMSStore
          >> " and "JMSState" using connection pool "JMSConnectionPool".>
          >> <Oct 1, 2002 8:29:20 AM EDT> <Alert> <JMS> <JMSServer "EnergizerJMSServer",
          >store
          >> failed to open, java.io.IOEx
          >> ception: JMS JDBC store, connection pool = <JMSConnectionPool>, prefix
          >= <null>:
          >> recover
          >> java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]ResultSet
          >can
          >> not re-read row data for colum
          >> n 1.
          >> at com.microsoft.jdbc.base.BaseResultSet.getLong(Unknown Source)
          >> at com.microsoft.jdbc.base.BaseResultSet.getLong(Unknown Source)
          >> at weblogic.jdbc.pool.ResultSet.getLong(ResultSet.java:304)
          >> at weblogic.jms.store.JDBCIOStream.doRecover(JDBCIOStream.java:618)
          >> at weblogic.jms.store.JDBCIOStream.recover(JDBCIOStream.java:728)
          >> at weblogic.jms.store.JMSStore.recover(JMSStore.java:112)
          >> at weblogic.jms.backend.BEStore.open(BEStore.java:179)
          >> at weblogic.jms.backend.BackEnd.initialize(BackEnd.java:330)
          >> at weblogic.jms.JMSService.createBackEnd(JMSService.java:923)
          >> at weblogic.jms.JMSService.addJMSServer(JMSService.java:1277)
          >> at weblogic.jms.JMSService.addDeployment(JMSService.java:1174)
          >> at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
          >> at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:279)
          >> at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:23
          >> 3)
          >> at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:193)
          >> at java.lang.reflect.Method.invoke(Native Method)
          >> at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:608)
          >> at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:592)
          >> at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:352)
          >> at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
          >> at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
          >> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:449)
          >> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:190)
          >> at $Proxy40.updateDeployments(Unknown Source)
          >> at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub
          >> java:2734)
          >> at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:362
          >> )
          >> at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:154)
          >> at java.lang.reflect.Method.invoke(Native Method)
          >> at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:608)
          >> at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:592)
          >> at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:352)
          >> at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
          >> at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
          >> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:449)
          >> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:190)
          >> at $Proxy57.start(Unknown Source)
          >> at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean
          >> _CachingStub.java:480)
          >> at weblogic.management.Admin.startApplicationManager(Admin.java:1151)
          >> at weblogic.management.Admin.finish(Admin.java:571)
          >> at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:508)
          >> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
          >> at weblogic.Server.main(Server.java:35)
          >

JDBC Persistent Store Exceptions Table needs to be renamed

we are facing a situation almost every week in production. The only workaround is to rename the table everytime an boune the Weblogic. Oracle recommended to increase the statement timeout. Not sure if that will work.
Can anyone provide what is the reason behind this. As there is only admin server in this domain with single JMS Server and JDBC Store. So not sure how the ownership is lost. Any help is appreciated .
####<Dec 25, 2010 4:32:01 AM IST> <Error> <Store> <gnnosm21> <OSMServer> <[ACTIVE] ExecuteThread: '65' for queue: 'weblogi
c.kernel.Default (self-tuning)'> <<WLS Kernel>> <1293231721099> <BEA-280075> <JDBC store "oms_jms_store" failed to r
etain ownership of database table "OM_BEAWLStore", either due to database access problems or due to concurrent accessors o
f the table. See the linked exception for more information.
weblogic.store.io.jdbc.JDBCStoreException: [Store:280065]java.sql.SQLException: ORA-01013: user requested cancel of curren
t operation
(server="OSMServer" store="oms_jms_store" table="OM_BEAWLStore"):(Linked Cause, "java.sql.SQLException: ORA-01013: user r
equested cancel of current operation
at weblogic.store.io.jdbc.JDBCStoreIO.readTableLockRecord(JDBCStoreIO.java:2078)
at weblogic.store.io.jdbc.JDBCStoreIO.updateTableOwnership(JDBCStoreIO.java:2105)
at weblogic.store.io.jdbc.ReservedConnection.timerExpired(ReservedConnection.java:436)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:265)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
java.sql.SQLException: ORA-01013: user requested cancel of current operation
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288)
at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:743)
at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:216)
at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:955)
at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1060)
at oracle.jdbc.driver.T4CPreparedStatement.executeMaybeDescribe(T4CPreparedStatement.java:839)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1124)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3316)
at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3361)
at weblogic.jdbc.wrapper.PreparedStatement.executeQuery(PreparedStatement.java:100)
at weblogic.store.io.jdbc.JDBCStoreIO.internalRead(JDBCStoreIO.java:721)
at weblogic.store.io.jdbc.JDBCStoreIO.readTableLockRecord(JDBCStoreIO.java:2066)
at weblogic.store.io.jdbc.JDBCStoreIO.updateTableOwnership(JDBCStoreIO.java:2105)
at weblogic.store.io.jdbc.ReservedConnection.timerExpired(ReservedConnection.java:436)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:265)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)

Hi,
You didnot mention what is that everytime you mean in your question....
Did you check is there any other user also using the same database table "OM_BEAWLStore" from your development environment connecting with the same JMS persistance store?

Which compiler does JDeveloper use?

When I try to compile (rebuild) a file I get "Fatal Error: compiler internal error". This file compiles just fine when I use javac.exe that came with jdk1.3. I have set up the jdk1.3 as instructed in the JDeveloper 3.2.2 release notes. In an effort to determine which compiler is being used, I have renamed all javac.exe files on my entire system and also ojc.exe. I would think that this would keep the file from compiling at all, but I can still do a "rebuild".
So I really have 2 questions:
Where is JDeveloper finding a compiler?
How can I resolve this fatal error?
Any advice would be appreciated.

How does weblogic determine which DDL to use when          > creating JMS persistent store?
          The DDL is stored in the weblogic.jar, and a particular DDL is chosen automically based on driver meta-data.
          Version 9.0 (out in beta), provides the option of administratively configuring the DDL file location.
          For unsupported drivers, versions prior to 9.0 require manually running a DDL file to create the JDBC store's backing tables (see JMS doc).
          Tom Barnes, BEA

Which DDL does Weblogic use?

How does weblogic determine which DDL to use when creating JMS persistent store?

How does weblogic determine which DDL to use when          > creating JMS persistent store?
          The DDL is stored in the weblogic.jar, and a particular DDL is chosen automically based on driver meta-data.
          Version 9.0 (out in beta), provides the option of administratively configuring the DDL file location.
          For unsupported drivers, versions prior to 9.0 require manually running a DDL file to create the JDBC store's backing tables (see JMS doc).
          Tom Barnes, BEA

Which form does IDM use?

For reconciliation, I put in a criteria within the form of the recon admin to check if the status is equal to Termination or not, if so then disable it. If not terminated then put the users in their appropriate organization.
<Disable>
<eq>
<ref>global.status</ref>
<s>T</s>
</eq>
</Disable>
Everything is fine. All the non-terminated users were in their appropriate organization. The problem is for all the Terminated ones, they were still being created except that they were put outside of the organization.
I wonder what form does IDM use to create these Terminated users because the form of the recon admin has been disabled already.
Thanks

How does weblogic determine which DDL to use when          > creating JMS persistent store?
          The DDL is stored in the weblogic.jar, and a particular DDL is chosen automically based on driver meta-data.
          Version 9.0 (out in beta), provides the option of administratively configuring the DDL file location.
          For unsupported drivers, versions prior to 9.0 require manually running a DDL file to create the JDBC store's backing tables (see JMS doc).
          Tom Barnes, BEA

Wl 5.1 sp 8 solaris from jdk1.2.2_07 to jdk1.3

Has anyone experienced any problems, issues when migrating jdk's? I have an
issue with ThreadDeaths when shutting down weblogic that may be corrected by
going to jdk 1.3, but before I do, want to know of any traps to look for.
Thanks
Steve Rogers
Senior System Engineer
[email protected]

found in another newsgroup posting:
Add the following to your weblogic.policy file:
permission java.sql.SQLPermission "setLog";
It should be in the last ("general") policy section.
JT
"Steve Rogers" <[email protected]> wrote in message
news:[email protected]...
Well I upgraded, and rebuilt all code with j2se 1.3 And I now get this
stack trace followed by the connection pool unable to be created, andhence
no beans deploying....
Mon Apr 09 20:02:45 EDT 2001:<E> <WebLogicServer> Failed to invoke startup
class
weblogic.jdbc.common.internal.JdbcStartup=weblogic.jdbc.common.internal.Jdbc
Sta
rtup
java.security.AccessControlException: access denied(java.sql.SQLPermission
setL
og)
at
java.security.AccessControlContext.checkPermission(AccessControlConte
xt.java:272)
at
java.security.AccessController.checkPermission(AccessController.java:
399)
at
java.lang.SecurityManager.checkPermission(SecurityManager.java:545)
at java.sql.DriverManager.setLogStream(DriverManager.java:397)
atweblogic.jdbc.common.internal.JdbcInfo.initLog(JdbcInfo.java:66)
atweblogic.jdbc.common.internal.JdbcInfo.startup(JdbcInfo.java:242)
at
weblogic.jdbc.common.internal.JdbcStartup.main(JdbcStartup.java:11)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.t3.srvr.StartupThread.runMain(StartupThread.java:219)
at weblogic.t3.srvr.StartupThread.doWork(StartupThread.java:109)
at
weblogic.t3.srvr.PropertyExecuteThread.run(PropertyExecuteThread.java
:62)
Mon Apr 09 20:02:45 EDT 2001:<I> <JMS> Beginning startup process
Mon Apr 09 20:02:45 EDT 2001:<I> <JMS> Init JMS Security
Mon Apr 09 20:02:45 EDT 2001:<I> <JMS> Init JMS persistent store
Mon Apr 09 20:02:45 EDT 2001:<E> <JMS>
javax.naming.NameNotFoundException: 'weblogic.jdbc.JdbcServices';remaining
name
'jdbc.JdbcServices'
at
weblogic.jndi.toolkit.BasicWLContext.resolveName(BasicWLContext.java:
745)
at
weblogic.jndi.toolkit.BasicWLContext.lookup(BasicWLContext.java:133)
at
weblogic.jndi.toolkit.BasicWLContext.lookup(BasicWLContext.java:574)
at weblogic.jms.server.JMSManager.init(JMSManager.java:311)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:1260)
at weblogic.t3.srvr.T3Srvr.main(T3Srvr.java:827)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.Server.startServerDynamically(Server.java:99)
at weblogic.Server.main(Server.java:65)
at weblogic.Server.main(Server.java:55)
"Mike Reiche" <[email protected]> wrote in message
news:[email protected]...
It's much faster. Hope that's not a problem.
I had one customer that was using third-party libraries
(OrbixWeb) that did not run propertly with 1.3. \
And you may have to set -XX:MaxPermSize=128m on Solaris.
Other than that, I have not seen any problems.
Mike
"Steve Rogers" <[email protected]> wrote:
Has anyone experienced any problems, issues when migrating jdk's? I
have an
issue with ThreadDeaths when shutting down weblogic that may be
corrected
by
going to jdk 1.3, but before I do, want to know of any traps to look
for.
Thanks
Steve Rogers
Senior System Engineer
[email protected]

Isolation Level vs. Locking

Hello,
I am still wrestlling a bit with the issues involved in setting an isolation
level. I am using WL 5.1, Oracle, and CMP.
I do now understand the issues involved between Oracle's
SERIALIZABLE and READ-COMMITTED isolation levels, etc.
But I also note that weblogic uses a pessimistic locking
approach for serializing access to entity ejb's. Doesn't this
locking supercede anything but an isolation level of
SERIALIZABLE? What happens with an isolation level
of READ-COMMITTED, even though the access to an
entity within any transaction will be serialized anyway?
Are there issues related to persistence issues outside of
ejb's, such as using JMS persistent messages within the
same system (same connection pool, etc.).
Also, I note that the ejb 2.0 spec in weblogic will allow
a more optimistic locking model. In this case, how will
multiple commits behave, will they behave according
to the isolation level chosen (READ-COMMITTED
or SERIALIZABLE?).
It's all confusing. What is the point, in ejb 1.1, for allowing
the bean developer to specify an isolation level, if all
access to entities will be done with exclusive locks?
What happens with multiple result finder methods? Does
this place exclusive locks on each entity found, within
a transaction?
Should I spend more time worrying about locking
models or isolation levels.
Am I just going around in circles?
Jason
Jason Rosenberg
SquareTrade
(remove 'nospam' from my return address)

Well, for now, I am designing for Oracle. What do you mean
by hazy?
Kirk Wylie <[email protected]> wrote in message news:[email protected]...
Probably not something you can count on guaranteeing no blocking. The
database could very well block here, particularly if your'e using
anything other than Oracle on the back-end, and Oracle can be a bit,
ahem, hazy in its acceptance of its own semantics here.
Kirk Wylie
Jason Rosenberg wrote:
Well, if the database table is set up to use READ-COMMITTED,
then it shouldn't block on the database, correct?
Jason
Cameron Purdy <[email protected]> wrote in message news:[email protected]...
... which means it could block on the database, correct?
Cameron Purdy
"Rob Woollen" <[email protected]> wrote in message
news:[email protected]...
A finder will never block on a container lock. For instance, imagine
that primary keys 3 and 4 are currently participating in a transaction
and are locked in server A. If a finder is called in server A which
returns these keys, the finder will run independently of the EJB server
locks. (Of course the database isolation will still apply.)
-- Rob
Jason Rosenberg wrote:
Ah, clustering saves the day!
I'm wondering though, since we don't have control over which
server in a cluster a given ejb may run on at any given time,
the concurrent behavior may be different to control. Some
times you can have concurrent access based on
READ-COMMITTED on the db level, and some times weblogic
will force a SERIALIZABLE behavior if 2 conflicting
ejb's get instantiated in the same container.
This is what I want. I would like complex finder methods
to be able to return a collection of primary keys over a
table, based on a READ-COMMITTED basis. This
needs to happen often, and shouldn't block (it's ok
if it misses out on uncommitted data in process, or
if it returns keys that may be in the process of being
deleted). But I don't ever want it to block because
another component has uncomitted changes in process.
Ideas? Wait for ejb2.0?
Jason
Rob Woollen <[email protected]> wrote in message
news:[email protected]...
It matters if you are in a cluster, or if othercomponents/applications
are accessing the same data.
It will also matter if your db does not have row-level locking.
-- Rob
Jason Rosenberg wrote:
I've excerpted below some of the text from the weblogic
documentation.
What this says to me is that, indeed, if an ejb entity is in anywayinvolved
in a transaction, all other transactions will be blocked frominstantiating
and using the bean instance until the transaction is over.
This is a de-facto SERIALIZABLE isolation level, is it not, with allthe
plusses and minuses. The plus is that data integrity is maintained,the
minus is that concurrent access is negatively effected.
What am I missing. Given this mechanism, what difference does it
make whether I use of a transaction isolation level ofREAD-COMMITTED
or SERIALIZABLE?
It looks like the story does change for ejb2.0.....
From the weblogic online documentation at:
http://www.weblogic.com/docs51/classdocs/API_ejb/EJB_environment.html#108796
7
Locking Model for Entity EJBs
The EJB 1.1 container in WebLogic Server Version 5.1 uses apessimistic locking mechanism for entity EJB instances. As clients
enlist an EJB or EJB method in a transaction, WebLogic Server placesan exclusive lock on the EJB instance or method for the
duration of the transaction. Other clients requesting the same EJBor method block until the current transaction completes.
This method of locking provides reliable access to EJB data, andavoids unnecessary calls to ejbLoad() to refresh the EJB
instance's
persistent fields. However, in certain circumstances pessimistic
locking may not provide the best model for concurrent access to
the
EJB's data. Once a client has locked an EJB instance, other clients
are blocked from the EJB's data even if they intend only to
read
the persistent fields.
To improve concurrent access for entity EJB's, the WebLogic Server
EJB 2.0 container enables you to defer locking services to
the
underlying database. In most cases, the underlying data store can
provide finer granularity for locking EJB data, and improve
throughput for concurrent access to the bean's data. See EJB 2.0 forBEA WebLogic Server Overview for more information.
Cameron Purdy <[email protected]> wrote in message
news:[email protected]...
I believe the "locking" refers to an internal WL implementationthat
prevents multiple threads from accessing an EJB instance.
Cameron Purdy, LiveWater
"Jason Rosenberg" <[email protected]> wrote in message
news:[email protected]...
Hello,
I am still wrestlling a bit with the issues involved in setting
an
isolation
level. I am using WL 5.1, Oracle, and CMP.
I do now understand the issues involved between Oracle's
SERIALIZABLE and READ-COMMITTED isolation levels, etc.
But I also note that weblogic uses a pessimistic locking
approach for serializing access to entity ejb's. Doesn't this
locking supercede anything but an isolation level of
SERIALIZABLE? What happens with an isolation level
of READ-COMMITTED, even though the access to an
entity within any transaction will be serialized anyway?
Are there issues related to persistence issues outside of
ejb's, such as using JMS persistent messages within the
same system (same connection pool, etc.).
Also, I note that the ejb 2.0 spec in weblogic will allow
a more optimistic locking model. In this case, how will
multiple commits behave, will they behave according
to the isolation level chosen (READ-COMMITTED
or SERIALIZABLE?).
It's all confusing. What is the point, in ejb 1.1, for allowing
the bean developer to specify an isolation level, if all
access to entities will be done with exclusive locks?
What happens with multiple result finder methods? Does
this place exclusive locks on each entity found, within
a transaction?
Should I spend more time worrying about locking
models or isolation levels.
Am I just going around in circles?
Jason
Jason Rosenberg
SquareTrade
(remove 'nospam' from my return address)
Kirk Wylie | mailto:[email protected] | http://www.radik.com

Can a SMB (server message block) be used as our file share in clustered OSB/SOA instance instead of a NAS?

We like to know if a SMB (server message block) will be adequate as our file share as opposed to a NAS. The SMB will be used for hosting files (e.g.: plan.xml, jms persistent stores, adapter control files, property files, binary files,...) that our services (OSB, SOA, Java) will be accessing in a cluster.
Also, is this a recommended approach that Oracle certifies?
Let me know if you need more details.
Current instance details:
OS: AIX 6.1
Type: 64-bit
WLS: 10.3.6

Hi,
As far as I know and as suggested by Mahdi, there is no such Group Policy settings which can help us to achieve this.
However, as also suggested by Mahdi, we can ask for help in the following scripting forum to see whether some scripts can help achieving this.
The Official Scripting Guys Forum
https://social.technet.microsoft.com/Forums/scriptcenter/en-US/home?forum=ITCG
If we can get such a script, we can use Group Policy to deploy the script to clients.
Best regards,
Frank Shen

JMS persistancy

Similar Messages

Maybe you are looking for