WLS V6.1 SP6 and Oracle 10

Does anyone know if WebLogic Server V6.1 Service Pack 6 can run ok with Oracle 10G using oracles thin driver?
Regards,
Terje Schjonneberg

We are having no problems using WLS 6.1 SP7 and 10G on Solaris.

Similar Messages

JTA with WLS 8.1 sp5 and Oracle 10.1.0.4

Hi,
          I am testing a global transaction involving two EJBs (stateless session beans) running on two separate WebLogic servers. Each ejb calls an Oracle stored procedure against a different datbase. One ejb is deployed on one server the other one on the second server.
          I want to know if it is mandatory to set up a trust relationship between the two servers. The reason I ask is that it seems the transaction is working without it (with the SecurityIdentity automatically downgraded to 'anonymous').
          However it only seems to consistently work between certain servers and randomly failing when using a different pair of servers.
          Thanks
          Cristian

Cristian Mihaila wrote:
          > Hi Joe,
          >
          > Here is the stack trace :
          Ok, you should make sure you're using consistent SecurityInteropMode settings
          on the different servers. Trust is only needed if the servers are on different
          domains otherwise trust is not needed. We made many changes to correct a downgrade
          issue on different subsystems JTA, JMS, EJB in 81sp6. There is a patch
          available for 81sp5 for this.
          Please read: http://e-docs.bea.com/wls/docs81/ConsoleHelp/jta.html#1120356
          Joe
          >
          > <Feb 20, 2007 11:53:54 AM EST> <Error> <EJB> <BEA-010026> <Exception occurred during commit of transaction Name=[EJB com.loyalty.arrow.services.epin.ejb.EPinFacadeSession.authenticate(java.lang.String,java.lang.String,java.lang.String,java.lang.String)],Xid=BEA1-02DD480140BE7F28EDB9(12622847),Status
          > =Rolling Back. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 29 seconds
          > BEA1-02DD480140BE7F28EDB9],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=89,seconds left=10,XAServerResourceInfo[OmdbXMultiPool]=(ServerResourceInfo[OmdbXMultiPool]=(state=new,assigned=pinpp2),xar=null,re-Registered = false),SCInfo[pinpp+pinpp2]=(state=rolling-back),SCInfo[mydomain+m
          > yserver]=(state=rolledback),properties=({weblogic.transaction.name=[EJB com.loyalty.arrow.services.epin.ejb.EPinFacadeSession.authenticate(java.lang.String,java.lang.String,java.lang.String,java.lang.String)]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=myserver+159
          > .175.18.251:7001+mydomain+t3+, XAResources={JMS_FileStore, shadbConnectionPool, arrow1lclprdPool},NonXAResources={})],CoordinatorURL=myserver+159.175.18.251:7001+mydomain+t3+): weblogic.transaction.internal.TimedOutException: Transaction timed out after 29 seconds
          > BEA1-02DD480140BE7F28EDB9
          > at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1600)
          > at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:1147)
          > at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1882)
          > at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:1064)
          > at weblogic.transaction.internal.WLSTimer.trigger(WLSTimer.java:31)
          > at weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:243)
          > at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
          > at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
          > at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:229)
          > at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:223)
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
          > --------------- nested within: ------------------
          > weblogic.transaction.RollbackException: Transaction timed out after 29 seconds
          > BEA1-02DD480140BE7F28EDB9 - with nested exception:
          > [weblogic.transaction.internal.TimedOutException: Transaction timed out after 29 seconds
          > BEA1-02DD480140BE7F28EDB9]
          > at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1684)
          > at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:311)
          > at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:228)
          > at weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:320)
          > at weblogic.ejb20.internal.StatelessEJBObject.postInvoke(StatelessEJBObject.java:168)
          > at com.loyalty.arrow.services.epin.ejb.EPinFacade_y6z7xe_EOImpl.authenticate(EPinFacade_y6z7xe_EOImpl.java:110)
          > at com.loyalty.arrow.services.epin.ejb.EPinFacade_y6z7xe_EOImpl_WLSkel.invoke(Unknown Source)
          > at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:492)
          > at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:108)
          > at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:435)
          > at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
          > at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
          > at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:430)
          > at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:35)
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
          >
          > Thanks
          > Cristian

ConnectionPool problems with WLS 7.0 and Oracle 9.2

Hi,
We are using WLS 7.0 SP4, and Oracle 9 and the Oracle thin driver type 4. In our
application on the productive system (and only there) we constantly encounter
a whole set of SQLExceptions which have all in common that the Connection from
the pool is not valid any more when the application tries to use it.
Typical, recurring error messages are:
- Exhausted ResultSet
- Connection has already been closed
- Closed Statement
- Transaction is no longer active - status committing
- NullPointerException at
weblogic.jdbc.pool.Connection.prepareStatement()
There are no special Statements which create these errors. They are spread at
random across practically every query the application creates, and the same queries
sometimes succeed and sometimes fail.
I double and triple checked that all Connections, Statements and ResultSets are
closed immediately after use. As an example, I attached a code snippet and a resulting
StackTrace which.
The problem also seems to occur only with an (unknown) minimum of concurrent usern,
since in the approval tests on an almost identical test system these errors never
occurred.
I also followed the advice from Oracle and installed the latest Oracle JDBC driver
(Oracle 10g) - to no avail.
What else can I do?
Another question: Is it correct that my Oracle JDBC driver is in the application
classpath (via a reference in the Manifest file of the application jar), not in
the system classpath? There has never been a problem with that, but in a Newsgroup
answer from Nov 10, 2003 (subject: "ResultSet closes prematurely"), Joe Weinstein
suggested to "get it listed at the
front of the -classpath argument that the startWebLogic script creates for the
java line that starts the server".
I hesitate to do so, since the driver is in a standard WebApp- directory, WEB-INF/lib.
Is it possible and safe to add a jar located there to the system classpath? If
it is possible, why is it necessary?
Best regards,
Andreas Zehrt
[CodeSnippetsAndStackTraceForConnectionPoolProblem.txt]

Andreas Zehrt wrote:
Hi Joe,
Your hint that there is a threading problem was right:
On further investigation of the code I found out that the class that passes the
Connection to the DAO not only stores it as a member at some point (which is not
a good idea anyway) but is also a singleton - then, of course, it's no surprise
that the Connection gets invalid in a incalculable way when concurrent threads
share it.
The singleton instantiation was not so obvious because the way of instantiation
is controlled by a configuration parameter that can be overridden at different
levels.
I changed it and the productive logfiles indicate that the SQLExceptions related
to that class have disappeared.I am happy to have helped.
So, thanks a lot for the advice.
But I am still wondering why this code has worked for so long a time with WLS
5.1 and Oracle 8 (the system has been productive for over 2 years). Even in the
approval tests with WLS 7.0 and Oracle 9, we did not run into problems, although
it was multi-user environment.Mo idea.
I still believe that there is a difference between WLS 5.1 and 7.0 in the way
it treats pooled Oracle JDBC Connections. I wished both Oracle and Bea could be
a little more explicit about those changes and possible version incompatabilities
beyond the general advice "use the latest thin driver".Though I can think of no change to our pooling which would have had any material
effect in this case, I will certainly do what I can to see that our documentation
is explicit about changes.
Joe
Best regards, Andreas
Joe Weinstein <[email protected]> wrote:
Hi Andreas.
Andreas Zehrt wrote:
Hi,
We are using WLS 7.0 SP4, and Oracle 9 and the Oracle thin driver type4. In our
application on the productive system (and only there) we constantlyencounter
a whole set of SQLExceptions which have all in common that the Connectionfrom
the pool is not valid any more when the application tries to use it.
Typical, recurring error messages are:
- Exhausted ResultSetThat is typically if the statement that created it is either re-executed
or closed.
- Connection has already been closedAs described. If you give a stacktrace, we could make a debug patch which
would show
where it was originally closed.
- Closed Statementsame as above.
- Transaction is no longer active - status committingThat implies your code is obtaining a connection from a transactional
datasource,
and then later trying to use it after the transaction which it was associated
with,
is finished.
- NullPointerException at
weblogic.jdbc.pool.Connection.prepareStatement()Maybe any of the above.
There are no special Statements which create these errors. They arespread at
random across practically every query the application creates, andthe same queries
sometimes succeed and sometimes fail.
I double and triple checked that all Connections, Statements and ResultSetsare
closed immediately after use. As an example, I attached a code snippetand a resulting
StackTrace which.
The problem also seems to occur only with an (unknown) minimum of concurrentusern,
since in the approval tests on an almost identical test system theseerrors never
occurred.
I also followed the advice from Oracle and installed the latest OracleJDBC driver
(Oracle 10g) - to no avail.
What else can I do?
Another question: Is it correct that my Oracle JDBC driver is in theapplication
classpath (via a reference in the Manifest file of the applicationjar), not in
the system classpath? There has never been a problem with that, butin a Newsgroup
answer from Nov 10, 2003 (subject: "ResultSet closes prematurely"),Joe Weinstein
suggested to "get it listed at the
front of the -classpath argument that the startWebLogic script createsfor the
java line that starts the server".
I hesitate to do so, since the driver is in a standard WebApp- directory,WEB-INF/lib.
Is it possible and safe to add a jar located there to the system classpath?If
it is possible, why is it necessary?I was only concerned to ensure we know which driver we are working with.
We also ship
an oracle thin driver, which becomes obsolete soon...
I am concerned that your code creates pool connections to be used later.
The problems
can arise if more than one thread ever gets the same connection, or if
the connection
is used in the same thread, spanning transactions. It does also seem
that there may
be a threading issue, because if two threads each call the code to create
a connection,
and two connections are made, but one over-writes the other, the two
threads can
end up using the same connection, and closing it. The over-written one
never gets closed,
resulting in that leak message you got...
Joe
The Connection parameter is opened by a business component class, ComaServiceProviderClassicImpl.It is propagated through
several classes in the business layer, but not used, until the DAOtakes it to make the query.
So, the Connection is closed where it was opened, not in the DAO class.
public class ConcernDAOImpl extends BaseDAO {
     public Collection getConcernsForIncidents(Connection conn, Collectionincidents)
throws DataAccessException, ConstraintException, ComaParseException{>
sqlMessage.append(")");
String sqlStmt = sqlMessage.toString();
PreparedStatement pstmt = null;
ResultSet rs = null;
try {
pstmt = conn.prepareStatement(sqlStmt);
rs = pstmt.executeQuery();
while (rs != null && rs.next()) {
final Concern concern =
new Concern(DAOUtil.getComaOID(rs, ComaDBNames.KDANR));
concern.setIncidentOID(DAOUtil.getComaOID(rs, ComaDBNames.KDAVGENR));
return concerns;
} catch (SQLException sqle) {
// Wrapps real SQL exception
String[] message = new String[]{sqle.getMessage(), sqlStmt};
throw new DataAccessException(ExpCode.S_ORACLE_SQL, message,
sqle);
} finally {
closeAll(rs, pstmt);
_logger.exitDebug(method);
Here, the Connection is acquired and finally closed
public class ComaServiceProviderClassicImpl {
     public void updateComplaint(
final Request updateRequest,
final ResponseSingleElement response,
final Principal principal)
throws SystemException {
try {
logger.info("updateComplaint", "store incident");
// store the incident in the database
incidentManager.storeIncident(getConnection(), updateIncident);
// reload the incident from Cache and / or the databaseto get the ContactReferences.
Incident returnIncident = incidentManager.loadIncident(//IncidentManager passes the Connection to the DAO
getConnection(), updateIncident.getOID());
} catch (RemoteException rex) {
// remote exceptions
rollbackIfNecessary();
CoreUtils.unwrapRemoteException(rex, logger);
} catch (SystemException e) {
// all other exceptions --> rollback if necessary and rethrow
rollbackIfNecessary();
throw e;
} finally {
removeConnection();
logger.exitDebug("updateComplaint");
This is the resulting StackTrace:
sql exception: [Closed Statement: next] - sql statement: [select *
     at de.deutschepost.ubbrief.coma.persistence.dao.ConcernDAOImpl.getConcernsForIncidents(ConcernDAOImpl.java:363)
     at de.deutschepost.ubbrief.coma.persistence.dao.CachingConcernDAOImpl.getConcernsForIncidents(CachingConcernDAOImpl.java:129)
     at de.deutschepost.ubbrief.coma.persistence.incidentmanager.IncidentManagerImpl.loadConcernStructuresIntoIncidents(IncidentManagerImpl.java:1067)
     at de.deutschepost.ubbrief.coma.persistence.incidentmanager.IncidentManagerImpl.loadStructureForIncident(IncidentManagerImpl.java:320)
     at de.deutschepost.ubbrief.coma.persistence.incidentmanager.IncidentManagerImpl.loadIncidents(IncidentManagerImpl.java:264)
     at de.deutschepost.ubbrief.coma.persistence.taskmanager.TaskManagerImpl.selectTasksForUser(TaskManagerImpl.java:299)
     at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2Impl.getTaskList(ComaServiceProviderZ2Impl.java:113)
     at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2Bean_1dhrj7_EOImpl.getTaskList(ComaServiceProviderZ2Bean_1dhrj7_EOImpl.java:154)
     at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList.runServiceMethod(CMPGetTaskList.java:64)
     at de.deutschepost.ubbrief.coma.sbbx.sp.BasicMethodProvider.execute(BasicMethodProvider.java:145)
     at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl.execute(CMPGetTaskList_9b9mv5_EOImpl.java:46)
     at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl_WLSkel.invoke(UnknownSource)
     at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:159)
     at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:263)
     at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:230)
     at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl_WLStub.execute(UnknownSource)
     at de.deutschepost.ubbrief.backbone.jazz.impl.core.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:115)
     at de.deutschepost.ubbrief.backbone.common.impl.core.rpc.server.ServerKernelImpl.handleTransportMessage(ServerKernelImpl.java:270)
     at de.deutschepost.ubbrief.backbone.common.impl.core.messaging.MessageTransport.handleMessage(MessageTransport.java:454)
     at de.deutschepost.ubbrief.backbone.common.impl.core.KernelFacade.handleMessage(KernelFacade.java:209)
     at de.deutschepost.ubbrief.backbone.jazz.impl.backbone.BackboneBean.messageArrived(BackboneBean.java:637)
     at de.deutschepost.ubbrief.backbone.jazz.impl.backbone.BackboneBean_ina9d7_ELOImpl.messageArrived(BackboneBean_ina9d7_ELOImpl.java:105)
     at de.deutschepost.ubbrief.backbone.jazz.impl.transport.receive.LocalQueueReceiveBean.deliverMessage(LocalQueueReceiveBean.java:43)
     at de.deutschepost.ubbrief.backbone.jazz.impl.transport.receive.AbstractMessageReceiveBean.onMessage(AbstractMessageReceiveBean.java:127)
     at weblogic.ejb20.internal.MDListener.execute(MDListener.java:377)
     at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:311)
     at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:286)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2351)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:2267)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)
####<May 26, 2004 12:18:43 PM CEST> <Warning> <JDBC> <S0048016> <REMA20Z><Finalizer> <kernel identity> <> <001074> <A JDBC pool connection leak
was detected. A Connection leak occurs when a connection obtained from
the pool was not closed explicitly by calling close() and then was disposed
by the garbage collector and returned to the connection pool. The following
stack trace at create shows where the leaked connection was created.
Stack trace at connection create:
     at weblogic.jdbc.pool.Connection.<init>(Connection.java:66)
     at weblogic.jdbc.pool.Driver.allocateConnection(Driver.java:294)
     at weblogic.jdbc.pool.Driver.connect(Driver.java:210)
     at weblogic.jdbc.jts.Driver.getNonTxConnection(Driver.java:373)
     at weblogic.jdbc.jts.Driver.connect(Driver.java:129)
     at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:287)
     at de.deutschepost.ubbrief.coma.core.ComaComponentImpl.getConnectionFromPool(ComaComponentImpl.java:163)
     at de.deutschepost.ubbrief.coma.core.ComaComponentImpl.getConnectionInternal(ComaComponentImpl.java:135)
     at de.deutschepost.ubbrief.coma.core.ComaComponentImpl.getConnection(ComaComponentImpl.java:99)
     at de.deutschepost.ubbrief.coma.persistence.customermanager.CurryCustomerManagerImpl.findCustomers(CurryCustomerManagerImpl.java:73)
     at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2BaseImpl.resolveCustomerInstances(ComaServiceProviderZ2BaseImpl.java:808)
     at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2Impl.getTaskList(ComaServiceProviderZ2Impl.java:213)
     at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2Bean_1dhrj7_EOImpl.getTaskList(ComaServiceProviderZ2Bean_1dhrj7_EOImpl.java:154)
     at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList.runServiceMethod(CMPGetTaskList.java:64)
     at de.deutschepost.ubbrief.coma.sbbx.sp.BasicMethodProvider.execute(BasicMethodProvider.java:145)
     at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl.execute(CMPGetTaskList_9b9mv5_EOImpl.java:46)
     at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl_WLSkel.invoke(UnknownSource)
     at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:159)
     at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:263)
     at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:230)
     at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl_WLStub.execute(UnknownSource)
     at de.deutschepost.ubbrief.backbone.jazz.impl.core.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:115)
     at de.deutschepost.ubbrief.backbone.common.impl.core.rpc.server.ServerKernelImpl.handleTransportMessage(ServerKernelImpl.java:270)
     at de.deutschepost.ubbrief.backbone.common.impl.core.messaging.MessageTransport.handleMessage(MessageTransport.java:454)
     at de.deutschepost.ubbrief.backbone.common.impl.core.KernelFacade.handleMessage(KernelFacade.java:209)
     at de.deutschepost.ubbrief.backbone.jazz.impl.backbone.BackboneBean.messageArrived(BackboneBean.java:637)
     at de.deutschepost.ubbrief.backbone.jazz.impl.backbone.BackboneBean_ina9d7_ELOImpl.messageArrived(BackboneBean_ina9d7_ELOImpl.java:105)
     at de.deutschepost.ubbrief.backbone.jazz.impl.transport.receive.LocalQueueReceiveBean.deliverMessage(LocalQueueReceiveBean.java:43)
     at de.deutschepost.ubbrief.backbone.jazz.impl.transport.receive.AbstractMessageReceiveBean.onMessage(AbstractMessageReceiveBean.java:127)
     at weblogic.ejb20.internal.MDListener.execute(MDListener.java:377)
     at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:311)
     at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:286)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2351)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:2267)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)

Oracle XA driver problem with WLS 7.0.1.0, Oracle 9.0.1

We are using simplified chinese, after swith to bea jdriver, it messed up
all the encoding. So we cannot display Chinese character correctly.
We are using WLS 7.0.1.0, Oracle 9.0.1 on both Windows and Solaris 8
environment, BEA supplied JDK 1.3.1_03.
We have many diffrent problems with oracle drivers:
1. We want to use XA driver to support distributed transaction, However:
* bea jdriver xa messes up with encoding
* when using oracle 901 driver, everything works fince except webservices.
Workshop application access the ejb, then the workshp application sets
isolation level, but oracle driver does not support it and gives error. Is
there a way to turn off isolation level in workshop? I tried manually edit
weblogic-ejb-jar.xml, however,workshop cannot redeploy it after that.
2. When not using XA, oracle thin driver works fine. But we lost XA
capability.
Any work around?

I did try to change the value in this config file as well, but did not help.
In fact, the installation default setting is with
'<transaction-isolation-level>' commented out.
And when I use bea oracle jdriver, it somehow messed up with database
character set encoding, so our Chinese characters could not be retrieved
correctly. And I try to set the encoding of jdriver to 'GBK', it did not
work.
"Anurag Pareek" <[email protected]> Ð´ÈëÏûÏ¢ÐÂÎÅ
:[email protected]..
Hello Ma,
The transaction isolation level value for EJBs backing the JWS files is
specified in the <transaction-isolation-level> tag in the
WEB-INF/weblogic-jws-config.xml file of a Workshop project. You can
manipulate this value to serve your purpose.
Please do let me know how it goes.
Regards,
Anurag
Workshop Support
"Ma Jie" <[email protected]> wrote in message
news:[email protected]..
We are using simplified chinese, after swith to bea jdriver, it messed
up
all the encoding. So we cannot display Chinese character correctly.
We are using WLS 7.0.1.0, Oracle 9.0.1 on both Windows and Solaris 8
environment, BEA supplied JDK 1.3.1_03.
We have many diffrent problems with oracle drivers:
1. We want to use XA driver to support distributed transaction, However:
* bea jdriver xa messes up with encoding
* when using oracle 901 driver, everything works fince exceptwebservices.
Workshop application access the ejb, then the workshp application sets
isolation level, but oracle driver does not support it and gives error.Is
there a way to turn off isolation level in workshop? I tried manuallyedit
weblogic-ejb-jar.xml, however,workshop cannot redeploy it after that.
2. When not using XA, oracle thin driver works fine. But we lost XA
capability.
Any work around?

How to install WLS 10.3.3 and OPFRD 11.1.1.2 + patch 11.1.1.3

I have Windows 2003 SP2 server which meets Oracle requirements. Can anybody explain me step by step how do to that? I have tried, but failed. I couldn't configure domain. On clean OS i have installed WLS withotu configure. Than I installed OPFRD 11.1.1.2. After that I installed patch 11.1.1.3. Everything passed OK w/o problems. Than I strated config.bat. I fill in the details and configuration begins. But stops on first step, when domain should be configured. How to solve the problem?
Thx in advance.

Thanks Rene, but as I said we are not using the same version of WLS and OSB so in that case is there any option that which version of OEPE i should download which support these two versions of WLS 10.3.5 and OSB 11.1.1.4.0.

Compatibility error with WLS 10.3.5 and OSB 11.1.1.4.0

As per out project requirement I am using WLS 10.3.5, OSB 11.1.1.4.0, and OEPE 11.1.1.6.1, but this oepe does not support these two WLS and OSB.
when I am trying to create a new Oracle Service Bus Configuration Project, i am getting a error:
Plug-in "com.bea.alsb.ui" was unable to instantiate class "com.bea.alsb.ui.wizards.NewALSBContainerWizard".
com/bea/alsb/core/containers/exceptions/ContainerException
Can anyone please suggest the correct version of OEPE if any.
Thanks in advance,
Jai

Thanks Rene, but as I said we are not using the same version of WLS and OSB so in that case is there any option that which version of OEPE i should download which support these two versions of WLS 10.3.5 and OSB 11.1.1.4.0.

WLS 8.1 Deployment and memory usage

Running WLS 8.1 SP2 and deploying (always manually) our application using the weblogic.Deployer tool, I am noticing a 6-8MB loss of available heap after each deploy. As you might imagine, these add up, if we redeploy 10 times in a given server instance, we end up with an Out of Memory error.
This really isn't an issue with our production apps, but is for us during development. Have there been any reports of memory/resource leaks in 8.1 deployments? I had thought it might be the JMS queues that start up and are shut down as part of our ApplicationListener, but it seems (via the console) that there is nothing extra lying around (at least not that's visible). In fact, the deployment seems to do what is promised - the system is in a consistent state after each one - except for this reduction in available memory. Any suggestions would be appreciated.
Mark

Mr. Jami Rimpela wrote:
Hi, I'm using WLS 8.1 SP2 and wondering whether WLS support automatic DB-reconnection
(to Oracle 9.x) if for some reason Oracle connection crashes while WLS is active
(up-and-running)? My WLS application is using Database connection pools by the
way. Hi. At the connection-request time, the pool can be configured to test the connection,
and replace it if needed. While a connection is in user hands, the pool and weblogic won't
be able to interfere or interpret any problem so the user code should close the connection
and obtain a new one (which the pool will verify is good if configured to test).
Second question: is WebLogic server (Administration or managed server) automatically
re-started if it for some reason crashes while excecuting?
Regards!
Jami

CachedRowSet problem in Weblogic 6.1 and Oracle thin driver 9.0.1

Has anyone used the CachedRowSet class successfully? (this classes are
new and from the JDBC extension pack)
I am experiencing "Not in a transaction" errors when executing
cachedrowset.populate(resultset), even though I'm inside a correct
ut.begin and ut.commit transaction.
Note I don't have these problems when I don't use the CachedRowSet
classes.
If I remove the setFetchSize(50) line, then I receive the ORA-01002:
fetch out of sequence error, which is discussed in another post on
this newsgroup.
I don't have any of these problems at all, if I use the Oracle Thin
Driver directly (i.e. not using Weblogic 6.1).
-H
Example of code:
stmt = getConnection().createStatement();
stmt.setFetchSize(50);
stmt.executeQuery("SELECT * FROM ASSET");
rs = stmt.getResultSet();
crs = new CachedRowSet();
crs.populate(rs);

Hi Arturo,
What kind of a problem do you have? Any stacktraces?
Regards,
Slava Imeshev
"Arturo Fernandez" <[email protected]> wrote in message
news:[email protected]..
Hi! I have a problem with CLOB column in Oracle 8.1.7. My enviroment
is:
Windows 2000, BEA WLS 6.1 and Oracle 8.1.7. I'm trying to use
'classes12.zip' provided by Oracle. I added 'classes12.zip' to
CLASSPATH after than 'weblogic.jar' in my startup server script, but
it fails when trying to retrieve a CLOB data from database. Script
includes:
setCLASSPATH=.\classes12_01.zip;.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar;
>
But this driver and the code runs sucessfully with the same database
and weblogic 5.1. I'm interesting in use this driver and this code
because i'm trying to migrate two applications from WLS 5.1 to WLS 6.1
I cannot find a solution.
Can everybody help me, please? It's urgent for me...

Problem pool weblogic 6.1 and oracle thin driver 8.1.7

Hi! I have a problem with CLOB column in Oracle 8.1.7. My enviroment
is:
Windows 2000, BEA WLS 6.1 and Oracle 8.1.7. I'm trying to use
'classes12.zip' provided by Oracle. I added 'classes12.zip' to
CLASSPATH after than 'weblogic.jar' in my startup server script, but
it fails when trying to retrieve a CLOB data from database. Script
includes:
set CLASSPATH=.\classes12_01.zip;.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar;
But this driver and the code runs sucessfully with the same database
and weblogic 5.1. I'm interesting in use this driver and this code
because i'm trying to migrate two applications from WLS 5.1 to WLS 6.1
I cannot find a solution.
Can everybody help me, please? It's urgent for me...

Hi Arturo,
What kind of a problem do you have? Any stacktraces?
Regards,
Slava Imeshev
"Arturo Fernandez" <[email protected]> wrote in message
news:[email protected]..
Hi! I have a problem with CLOB column in Oracle 8.1.7. My enviroment
is:
Windows 2000, BEA WLS 6.1 and Oracle 8.1.7. I'm trying to use
'classes12.zip' provided by Oracle. I added 'classes12.zip' to
CLASSPATH after than 'weblogic.jar' in my startup server script, but
it fails when trying to retrieve a CLOB data from database. Script
includes:
setCLASSPATH=.\classes12_01.zip;.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar;
>
But this driver and the code runs sucessfully with the same database
and weblogic 5.1. I'm interesting in use this driver and this code
because i'm trying to migrate two applications from WLS 5.1 to WLS 6.1
I cannot find a solution.
Can everybody help me, please? It's urgent for me...

Installation of webgate on Solaris (sparcv9) with WLS 10.3.5 and Apache2

Problem Description: We have installed IDM 11g and OAM 10.1.4.3 on RHEL5.5 hosts, respectively. We have successfully installed all the components:
Environment Details:
- Server1 -- 64 bit Intel RHEL5
Fusion Middleware Identity Management - 11.1.1.2
WLS 10.3.2
ODSM,OID,OVD
DB 10.2.0.4
- Server 2 32-bit Intel RHEL5
OAM 10.1.4.3
OHS 11.1.1.2
After successfully installing these hosts, we needed to create a webhost from where we could test our protected resources. This host would have a sparc v9 OS, include WLS 10.3.5, and use apache2 as its web server. These have all been successfully installed by root and are running.
Our next step was to create the webgate/access gate on the OAM host and setup the necessary policy. This was successful.
We then copied Oracle_Access_Manager10_1_4_3_0_sparc-s2_APACHE2_WebGate to the host and started the installation. Since the host is headless (just a host -- no keyboard, mouse, or gui attached to it) we have to ssh to the host and execute all the installs from the command line without gui. When we got to entering the webgate id and hit return... the process just ended without any error or logfiles. We are assuming that at that point the webgate software was installed but not configured.
We went ahead and tried the configureWebGate script:
./start_configureWebGate -i /opt/oracle/middleware/webgate -l WebGate
ld.so.1: configureWebGate: fatal: /opt/oracle/middleware/webgate/access/oblix/tools/configureWebGate/../../../oblix/lib/libstdc++.so.5: wrong ELF data format: ELFDATA2LSB
Killed
We have successfully installed OAM and IDM many times and have installed webhosts as well... but the webhosts have always been RHEL5 with WLS and OHS instead of Sparc, wls, and apache. Is there anything special about a sparc or apache install?
WLS and apache were installed as root... we have tried installing the webgate as root, oracle, even apache... but get the same results. The gcc libs are downloaded and available, but the error we see during configuration seems to indicate that they are not found. We have tried seting the LD_LIBRARY_PATH to include the directory containing the libs.
Edited by: OldGuy on Jul 7, 2011 4:04 AM

On another note... is there a Sparc equivalent for the mod_wl_ohs.conf where we would place
<Location /<deployed app>>
SetHandler weblogic-handler
WebLogicHost <weblogichost>
WebLogicPort 7001
</Location>
It appears that this goes into the apache httpd.conf file, correct? Or does the mod_wl_ohs.conf equivalent exist?
We have just about completed everything in regard to being able to include a solaris host in our list of hosts that are tied to OAM. The webgate was created and software installed, the deployed app protected, etc... Everything that we have done for Linux and XP in the past we have done for this Sparc host.
When we try to access the Sparc's protected uri... nothing happens. The browser stays blank... the url does not change to display the oamsso login.html (as the other installs do)... nothing is returned... no error, no remarks, no logfile entries... just a blank browser.

WLS10.3.0 and Oracle DB 12c

Hi
we've WLS 10.3.0 (we've extended support) and Oracle Database 11g DB 11.2.0.4 running under HPUX 11.31 U ia64
We plan first to upgrade to Oracle 12c.
Question: is WLS10.3.0 supported together with Oracle DB 12c.
Its planned to to do WLS10.3.6 upgrade in a separate step - later - 10.3.6 and 12c - this combination is valid (according the Certifcation page)
Best regards
Thomas

You can also patch up 10.1.3.0.0 with 10.1.3.1.0 patchset and then deploy SOA Suite components like BPEL, ESB, OWSM to the same OC4J. This will reduce the number of Oracle Homes on your machine.

IIOP connection problems .: JDeveloper 3.1 and Oracle 8.1.6

This is my 4th day working on this problem. I cannot get an IIOP connection to work.
I have verfied that the listener is running on port 2481, I have been inside of the init.ora, listeners.ora, I have read the error inside of listeners.log, and I have been trying things with the Net8 Assistant also.
Most of the posts on this subject seem older, I am wondering if anyone has had this problem recently with the versions that I am using. There are so many things I have been told to change, I'm wondering if there is a definitive list of steps to fix this problem.
Any help is greatly appreciated.

r singh wrote:
>
I am getting "No Suitable Driver" exception from WebLogic 6.1 (sp1) at
the start up of the server.
My settings:
- WLS 6.1 on a solaris 8 machine and Oracle 8.1.6 on a WIN2K machine.
- I created the connection pool for oracle with the following
parameters:
connection name: OracleConnectionPool
url: jdbc.oracle.thin:@myOracleServer:1521:myDBName
driver class name: oracle.jdbc.driver.OracleDriver
properties: user=scott
password=tiger
- I have also downloaded classes12.zip and nls_charset12.zip from
Oracle.com
and have placed under $WL_HOME/lib.
- I have added $WL_HOME/lib/classes12.zip:$WL_HOME/lib/nls_charset12.zip
in
front of the $CLASSPATH in the startWeblogic.sh script. The echoed
classpath
from the startup script is:
/opt/tools/bea/wlserver6.1/lib/classes12.zip:/opt/tools/bea/wlserver6.1/lib/nls_
charset12.zip:/opt/tools/bea/wlserver6.1:/opt/tools/bea/wlserver6.1/lib/weblogic
_sp.jar:/opt/tools/bea/wlserver6.1/lib/weblogic.jar
- Still I get the error:
<Jan 16, 2002 1:38:45 PM EST> <Error> <JDBC> <Cannot startup
connection pool "Or
acleConnectionPool" No suitable driver>
Can somebody point me out if i am doing anything wrong here.
Thanks.
RamanandHi,
Sure. Your URL should be "jdbc:oracle:thin:@myOracleServer:1521:myDBName"
not "jdbc.oracle.thin:@myOracleServer:1521:myDBName"
Joe

WLS 5.1 SP6 with JRE 1.3 - Cannot start server from Start Menu or as NT service

Hi:
I am trying to setup WLS 5.1 SP6 runing with JRE 1.3 on Windows 2000 Server to
run as an NT Service or from the start menu. The wlserver program is invoked the
following error message is returned. (A similar error is returned when starting
as an NT Service)
=====================================================
D:\weblogic>bin\wlserver
Java dll not found. Bad value for JAVA_HOME.
The system cannot find the path specified.
Java dll not found. Bad value for JAVA_HOME.
The system cannot find the path specified.
loadIt: Java DLL not found.
The Windows registry is misconfigured
for the WebLogic Server
JAVA dll not found: d:\jre1.3.0_02\jre\bin\javai.dll:
The Windows registry is misconfigured
for the WebLogic Server
Can't start WebLogic Server: (Can't start Java VM) err=0x2000001
D:\weblogic>
=========================================================
I found old messages in the newsgroups indicating that there have been issues
with WLS 5.1 and Java 1.3 on NT running as a service or from the start menu.
But there does not seem to be a resolution to this problem yet.
Is there a workaround to this issue. Is there a new wlserver that supports 1.3
for WLS 5.1. I am running with SP6 because we need to run with WLCS 3.2 also.
WLS 5.1 starts up fine as a service or from the start menu with the JRE 1.2 shipped
with the product or from a command window with startWeblogic running SDK 1.3
Thanks in advance for any help to clear this up.
-William

Thanks for the suggestion... the registry already has this setting... that does
not seem to be it.
From looking closer at what is installed with the 1.3 JRE versus the 1.2 JRE packaged
with the 5.1 server... it seems to me that the issue has to do with support for
the Hotspot VM.
The 1.3 JRE has a hotspot subdirectory under the bin, there is no classic subdirectory,
as is the case with the 1.2 JRE in the 5.1 package or even with a standard SDK
1.3 installation.
Does 5.1 support the hotspot vm. How can I switch it to use the 'older' JVM instead?
If I copy the 'classic' jvm.dll from the sdk 1.3 installation into the bin\classic
directory of the 1.3 JRE, the server does start, but an error message indicating
that the javai.dll was not found still comes up. Followed by the following error:
Warning: JIT compiler "symcjit" not found. Will use interpreter.
The server startup output then comes up ... Please help, anyone?
"Jcmuppy" <[email protected]> wrote:
Registry key 'Software\JavaSoft\Java Runtime Environment\CurrentVersion'
has value '1.1', but '1.3' is required.
If the value is "1.1", chage the value into "1.3"
"William Rojas" <[email protected]> wrote:
>
Hi:
I am trying to setup WLS 5.1 SP6 runing with JRE 1.3 on Windows 2000
Server to
run as an NT Service or from the start menu. The wlserver program is
invoked the
following error message is returned. (A similar error is returned when
starting
as an NT Service)
=====================================================
D:\weblogic>bin\wlserver
Java dll not found. Bad value for JAVA_HOME.
The system cannot find the path specified.
Java dll not found. Bad value for JAVA_HOME.
The system cannot find the path specified.
loadIt: Java DLL not found.
The Windows registry is misconfigured
for the WebLogic Server
JAVA dll not found: d:\jre1.3.0_02\jre\bin\javai.dll:
The Windows registry is misconfigured
for the WebLogic Server
Can't start WebLogic Server: (Can't start Java VM) err=0x2000001
D:\weblogic>
=========================================================
I found old messages in the newsgroups indicating that there have been
issues
with WLS 5.1 and Java 1.3 on NT running as a service or from the start
menu.
But there does not seem to be a resolution to this problem yet.
Is there a workaround to this issue. Is there a new wlserver that supports
1.3
for WLS 5.1. I am running with SP6 because we need to run with WLCS
3.2 also.
WLS 5.1 starts up fine as a service or from the start menu with the JRE
1.2 shipped
with the product or from a command window with startWeblogic running
SDK 1.3
Thanks in advance for any help to clear this up.
-William

Problem setting up APEX 4 with WebLogic and Oracle XE

I'm am trying to install and test Application Express 4 (latest version) on a brand new installation of Oracle WebLogic Server and Oracle XE.
I have followed the Installation Guide for APEX and have successfully installed all tables and scripts into my Oracle XE schema and am able to connect to the Application Express Workspace login page (http://localhost:8080/apex) but am not able to log in. All styles and images are missing.
I have followed the steps in the Application Express Listener Guide to install the Listener to my WebLogic deployments and have my i.war and apex.war files deployed but these apparently are not working. When I go to my WebLogic server and view the /apex/ListenerConfigure page I can see the page but get an HTTP 404 "Page Not Found" error and appears to be looking for the WLS's apex/apex directory.
Note: My Oracle XE / APEX setup is on a separate server than my WebLogic server.
Also, I see the APEX Listener file (apex-confix.xml) from the install zip file but I don't believe it is being used anywhere, as the documentation never told me what to do with it.
Any help would be awesome. Let me know what I can provide that I haven't. Thanks!

Thank you, I was able to use what you said as well as this information here: Installing Apex 4 on Oracle XE: Almost there, but no cigar yet!
Thank you for the help :)

Weblogic 7 and Oracle

I was wondering, does Weblogic 7 work with Oracle 8.16?? Or do I need
to upgrade to 8.17?
Thanks,
Stephen.

I was looking up that kind of thing today for an official support case. In the
WLS 6.1 migration guide, it says that 8.16 is not supported and you must use 8.17.
This is the upgrade guide from 4.5 and 5.1 to 7.0.
http://edocs.beasys.com/wls/docs70/upgrade/upgrade45_51to70.html#1102044
the Upgrading Oracle section ->
http://edocs.beasys.com/wls/docs70/upgrade/upgrade45_51to70.html#1080633
it has pointers to other references you will want to explore.
If you go to the 7.0 docs http://edocs.beasys.com/wls/docs70/index.html and
look at the topics: "Upgrading" ; JDBC related parts ; just poke around and you
will find what you are looking for.
/wws
Stephen wrote:
I was wondering, does Weblogic 7 work with Oracle 8.16?? Or do I need
to upgrade to 8.17?
Thanks,
Stephen.

WLS V6.1 SP6 and Oracle 10

Similar Messages

Maybe you are looking for