WLS 8.1 with Oracle 8.1.5.7
Hi,
I am using WLS with Oracle (connexion Pool). The JDBC driver is configured with the thin client of Oracle.
The connexion are very low even if a low number of users are connected to the system.
Is there any recommandations please.
Thanks,
Elie
Set initial capacity=max capacity.
AWAD <[email protected]> wrote:
Hi,
I am using WLS with Oracle (connexion Pool). The JDBC driver is configured
with the thin client of Oracle.
The connexion are very low even if a low number of users are connected
to the system.
Is there any recommandations please.
Thanks,
Elie
Similar Messages
-
Which version of Weblogic on Solaris is compatible with Oracle 8.1.7 - Unicode?
Hi folks,
We want upgrade WLS 4.5.1 to one of the last version of WLS, but also we are
planing upgrade Oracle to 8.1.7 version and migrate the character set of the
database to UTF8 (Unicode),
so we need to know which versions of WLS are compatible with Oracle 8.1.7
and Unicode as Character Set.
Thanks in advance.
Moises Moreno.Hi Moises Moreno
The latest version of weblogic server is 6.1 with service pack 1. This version
supports oracle 8.1.7 on major unix platforms viz., solaris(2.6,2.7,2.8),
hp-unix(11.0,11.0i), linux7.1, Aix4.3.3 and on windows platforms viz.,
NTwithsp5, 2000.
BEA jdrivers are having Multibyte character set support (UTF8).
Note : Weblogic server 5.1 with SP10 also supports oracle 8.1.7.
FMI : http://www.weblogic.com/platforms/index.html#jdbc
Thanks & Regards
BEA Customer Support
Moises Moreno wrote:
Hi folks,
We want upgrade WLS 4.5.1 to one of the last version of WLS, but also we are
planing upgrade Oracle to 8.1.7 version and migrate the character set of the
database to UTF8 (Unicode),
so we need to know which versions of WLS are compatible with Oracle 8.1.7
and Unicode as Character Set.
Thanks in advance.
Moises Moreno. -
Some problems with Oracle and XA in WLS 6.1
Hi,
I am using WLS6.1 SP4 with Oracle Thin driver 8.1.7 and TxDataSources with ConnectionPools
using XA.
I am getting the following error:
java.sql.SQLException: ORA-00604: error producido a nivel 1 de SQL recursivo
ORA-01000: número máximo de cursores abiertos excedido
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:168)
at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java:208)
at oracle.jdbc.ttc7.Oall7.receive(Oall7.java:543)
at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java:1405)
at oracle.jdbc.ttc7.TTC7Protocol.parseExecuteFetch(TTC7Protocol.java:822)
at oracle.jdbc.driver.OracleStatement.doExecuteQuery(OracleStatement.java:1657)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1870)
at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:363)
at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:314)
at weblogic.jdbc.jta.PreparedStatement.executeQuery(PreparedStatement.java:69)
at weblogic.jdbc.rmi.internal.PreparedStatementImpl.executeQuery(PreparedStatementImpl.java:56)
at weblogic.jdbc.rmi.SerialPreparedStatement.executeQuery(SerialPreparedStatement.java:42)
at delta.beans.common.DBQueriesRemesa.getSecuencia(DBQueriesRemesa.java:55)
at delta.beans.remesas.ImportarRemesa2.remesaRATSB(ImportarRemesa2.java:858)
at delta.beans.remesas.ImportarRemesa2.execute(ImportarRemesa2.java:122)
at java.lang.reflect.Method.invoke(Native Method)
at delta.servlet.contrl.service(contrl.java:161)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:262)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:21)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at delta.servlet.VolverFiltro.doFilter(VolverFiltro.java:101)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2643)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2359)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
I have read about this issue in the newsgroup and I know it seems to be a bug
in Oracle Driver.
So, as a workaround, I'm trying to use the Oracle's prepared statement cache features
in order to avoid creations of new statements for each query. I noticed that the
WebLogic prepared statement cache does not work properly, because I put a value
of 10 but when inspecting with WLShell it haven't any hit in the statement cache.
In order to use Oracle's prepared statement cache I have to enable it in the physical
connection, but I don't found in weblogic.jar the class weblogic.jdbc.extensions.WLConnection
which have the method getVendorConnection. In the documentation available at http://edocs.beasys.com/wls/docs61/javadocs/index.html
there is a reference to that class and it haven't any notice since which service
pack it becomes available.
So, is there any way to obtain the physical connection?
Can anybody help me about any of these problems??
Thanks in advance.
Jesús.The line of code that brings up this exception is:
multiReq = new
= new MultipartRequest((ServletRequest)request,
"c:\\temp", 10485760);
try this: MultipartRequest multiReq = new MultipartRequest((ServletRequest)request,
"c:\\temp", 10485760);
(not sure if that is the problem or not..) -
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) -
Facing Issue With Oracle SOA Suite 11.1.1.3.0
Hi All,
I am facing some issues with ORACLE SOA SUITE 11.1.1.3.0.
Hope you people can help us out.
Please find the issue details below along with all the relevant information’s
I have following SOA suite installation at my server:
Oracle 10g Express Edition Universal 10.2.0.1
RCU 11.1.1.3.3
Web Logic Server 10.3.3.0
SOA suite 11.1.1.3.0
JDeveloper 11.1.1.3.0
The first thing what I have done is created a web service and deployed it to server without any issue.
After that I created proxy client for that service and accessed it successfully from the client end.
Till here no issue occurs.
After that I applied few policies on top of web service and deployed it to server.
The policy I had chosen was “oracle/wss_username_token_service_policy” [coming under OWSM policies list]
While deploying there was no issue, all went well.
2nd step I had created client using “oracle/wss_username_token_client_policy” policy which is counter part of above policy and tried to access the web service but failed.
I have followed this blog:
[http://biemond.blogspot.com/2010/08/things-you-need-to-do-for-owsm-11g.html ]
Please have a look on service and client code:
Service Code:
package Demo_ScoreCard;
import javax.jws.WebService;
import weblogic.wsee.jws.jaxws.owsm.SecurityPolicy;
@WebService
@SecurityPolicy(uri = "oracle/wss_username_token_service_policy")
public class ScoreCardWithPolicy {
public double getPercentageWithPolicy(double markEng,double markMath,double markHindi,double markScience,double markSsc)
double result;
result= ((markEng+markHindi+markMath+markScience+markSsc)/500)*100;
return result;
Client Code:
package com.tec.proxy.client;
import java.util.Map;
import javax.xml.ws.BindingProvider;
import javax.xml.ws.WebServiceRef;
import weblogic.wsee.jws.jaxws.owsm.SecurityPolicyFeature;
public class ScoreCardWithPolicyPortClient {
@WebServiceRef
private static ScoreCardWithPolicyService scoreCardWithPolicyService;
public static void main(String[] args) {
scoreCardWithPolicyService = new ScoreCardWithPolicyService();
SecurityPolicyFeature[] securityFeatures =new SecurityPolicyFeature[] { new SecurityPolicyFeature("oracle/wss_http_token_client_policy") };
ScoreCardWithPolicy scoreCardWithPolicy =scoreCardWithPolicyService.getScoreCardWithPolicyPort(securityFeatures);
Map<String, Object> reqContext =((BindingProvider)scoreCardWithPolicy).getRequestContext();
reqContext.put(BindingProvider.USERNAME_PROPERTY, "testclient");
reqContext.put(BindingProvider.PASSWORD_PROPERTY, "test12345"); // I have added this to the myrealm from console under security realms
double arg1 = 77.2;
double arg2 = 79.2;
double arg3 = 77.2;
double arg4 = 76.2;
double arg5 = 67.2;
double clientResult =scoreCardWithPolicy.getPercentageWithPolicy(arg1, arg2, arg3, arg4,arg5);
System.out.println("clientResult with policy =====> " + clientResult);
Error Log:
SEVERE: WSM-07617 Policy: oracle/wss_http_token_client_policy contains unsupported assertions.
SEVERE: WSMAgentHook: An Exception is thrown: WSM-07617 Policy Policy: oracle/wss_http_token_client_policy contains unsupported assertions.
Exception in thread "main" javax.xml.rpc.JAXRPCException: oracle.wsm.common.sdk.WSMException: WSM-07617 Policy Policy: oracle/wss_http_token_client_policy contains unsupported assertions.
at oracle.wsm.agent.handler.wls.WSMAgentHook.handleException(WSMAgentHook.java:395)
at oracle.wsm.agent.handler.wls.WSMAgentHook.init(WSMAgentHook.java:206)
at weblogic.wsee.jaxws.framework.jaxrpc.TubeFactory.newHandler(TubeFactory.java:105)
at weblogic.wsee.jaxws.framework.jaxrpc.TubeFactory.createClient(TubeFactory.java:68)
at weblogic.wsee.jaxws.WLSTubelineAssemblerFactory$TubelineAssemblerImpl.createClient(WLSTubelineAssemblerFactory.java:148)
at com.sun.xml.ws.client.WSServiceDelegate.createPipeline(WSServiceDelegate.java:467)
at com.sun.xml.ws.client.WSServiceDelegate.getStubHandler(WSServiceDelegate.java:689)
at com.sun.xml.ws.client.WSServiceDelegate.createEndpointIFBaseProxy(WSServiceDelegate.java:667)
at com.sun.xml.ws.client.WSServiceDelegate.getPort(WSServiceDelegate.java:362)
at weblogic.wsee.jaxws.spi.WLSProvider$ServiceDelegate.internalGetPort(WLSProvider.java:855)
at weblogic.wsee.jaxws.spi.WLSProvider$ServiceDelegate$PortClientInstanceFactory.createClientInstance(WLSProvider.java:967)
at weblogic.wsee.jaxws.spi.ClientInstancePool.takeSimpleClientInstance(ClientInstancePool.java:621)
at weblogic.wsee.jaxws.spi.ClientInstancePool.take(ClientInstancePool.java:486)
at weblogic.wsee.jaxws.spi.WLSProvider$ServiceDelegate.getPort(WLSProvider.java:782)
at com.sun.xml.ws.client.WSServiceDelegate.getPort(WSServiceDelegate.java:344)
at javax.xml.ws.Service.getPort(Service.java:133)
at com.tec.proxy.client.ScoreCardWithPolicyService.getScoreCardWithPolicyPort(ScoreCardWithPolicyService.java:86)
at com.tec.proxy.client.ScoreCardWithPolicyPortClient.main(ScoreCardWithPolicyPortClient.java:23)
Process exited with exit code 1.
Not getting any help from any blog. Just wondering why this error is coming. I would be glad if you can help us in this regard.
Apart from above issue I have few queries like:
1.What is difference between OWSM policies and WLS policies?
2.Are these the only policies we can apply on top of services?
3.If some one wants to configure his own custom policies than what need to be done
4.Could anyone please provide some useful links to implement ENCYPTION and SIGNATURE on top of web services?
5.And If I am not wrong, I guess Oracle Service BUS OSB 11.1.1.3 has been removed from the main download link and version 11.1.1.4 has been provided. Is it
compatible with SOA suite 11.1.1.3.0? If not where can I get OSB 11.1.1.3?
Looking forward to hear from you people.
Thanks
Arvind
Edited by: user8490871 on Apr 15, 2011 12:53 AM
Edited by: user8490871 on Apr 15, 2011 12:53 AMHi,
I don't know why u get an error. Here are answers for additional questions:
1. OWSM policies are for web services. WLS policies are based on Java EE security. They are used to protect resources e.g. URL, EJB
2. I don't know about other policies
3. See http://download.oracle.com/docs/cd/E14571_01/web.1111/e13713/owsm_appendix.htm#CHDCHFBH
4. See http://download.oracle.com/docs/cd/E14571_01/security.1111/e10037/toc.htm
5. I can see OSB 11.1.1.3 download link here
http://www.oracle.com/technetwork/middleware/downloads/fmw-11-download-092893.html
Regards,
Milan -
What XA JDBC driver should I use with Oracle 8i 8.1.6
I need to use an XA JDBC driver for Oracle 8i 8.1.6. I am using the driver in
a ConnectionPool in a TxDataSource for use by some entity beans using EJB 2.0.
I'm running WebLogic Server 6.0 sp2, EJB 2.0, Java 2 SDK 1.3.1 Server VM, Solaris
2.7, and Oracle 8i 8.1.6.
I know of three different Oracle XA drivers: WebLogic jDriver for Oracle XA, Oracle
OCI type 2 driver XA, and Oracle Thin tyoe 2 XA. Are there any other drivers
that I can use for Oracle 8.1.6? Which driver and which version should I use?
For example, can I use the Oracle 8.1.7 JDBC drivers with the Oracle 8.1.6 server,
or would the Oracle 9i drivers work with the Oracle 8i server? Which drivers
are faster, and which support more features? I assume that I should not use the
type 4 driver since I am not using an applet, but I don't know if there are bugs
in the OCI C library for Solaris or in the JDBC drivers that use it that prevent
XA from woking. Which version of the Oracle C OCI library should I use if I use
a type 2 driver?
Thanks,
Ross GoldbergHi,
I think you can't use the 8.1.6 thin driver for XA, you would have to
use the OCI driver or 2PC-enable your datasource. AFAIK this has been
changed for 8.1.7
Check http://e-docs.bea.com/wls/docs61/////jta/thirdpartytx.html.
Daniel
-----Original Message-----
From: Gene Chuang [mailto:[email protected]]
Posted At: Thursday, August 30, 2001 2:04 AM
Posted To: jdbc
Conversation: What XA JDBC driver should I use with Oracle 8i 8.1.6
Subject: Re: What XA JDBC driver should I use with Oracle 8i 8.1.6
I've asked this question before. This is the reply from Joe
Weinstein:
For reliability and JDBC 2.0 compliance, I recommend the
Oracle thin driver.
If not that driver, you should verify that a type-2 driver
actually does
deliver better performance, but then I would not have a
strong preference
between their type-2 and ours. Theirs may be faster, and JDBC
2.0 compliant.
Both are succeptible to OCI bugs, some of which only they can
fix, but we
listen.
Gene
"Ross Goldberg" <[email protected]> wrote in message
news:[email protected]...
>
I need to use an XA JDBC driver for Oracle 8i 8.1.6. I am using thedriver in
a ConnectionPool in a TxDataSource for use by some entity beans usingEJB 2.0.
I'm running WebLogic Server 6.0 sp2, EJB 2.0, Java 2 SDK 1.3.1 ServerVM, Solaris
2.7, and Oracle 8i 8.1.6.
I know of three different Oracle XA drivers: WebLogic jDriver forOracle XA, Oracle
OCI type 2 driver XA, and Oracle Thin tyoe 2 XA. Are there any otherdrivers
that I can use for Oracle 8.1.6? Which driver and which versionshould I use?
For example, can I use the Oracle 8.1.7 JDBC drivers with the Oracle8.1.6 server,
or would the Oracle 9i drivers work with the Oracle 8i server? Whichdrivers
are faster, and which support more features? I assume that I shouldnot use the
type 4 driver since I am not using an applet, but I don't know ifthere are bugs
in the OCI C library for Solaris or in the JDBC drivers that use itthat prevent
XA from woking. Which version of the Oracle C OCI library should Iuse if I use
a type 2 driver?
Thanks,
Ross Goldberg -
A lot of problems with Oracle BI SEE 11g
I have a lot of problems with Oracle BI SEE 11g
1. I upgraded my BI SEE 10 repository and can it openning in offline mode.
2. I can't deploy my upgraded repository in EM MW Control 11g - when i try to open Farm_bifoundation_domain->Business Intelligence->coreapplication, i get error "Stream closed
For more information, please see the server's error log for an entry beggining with: Server Exception during PPR, #41".
Opening Logs by EM control doesn't work too.
in file middleware\user_projects\domains\bifoundation_domain\servers\AdminServer\logs\AdminServer.log i see this event:
<Error> <HTTP> <oratest.itera.ru> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <b639ac3e56e9a463:bd6fa7f:12ac7271e09:-8000-00000000000009e8> <1283408423378> <BEA-101019> <[ServletContext@329875093[app:em module:/em path:/em spec-version:2.5]] Servlet failed with IOException
java.io.IOException: Stream closed
Have you any ideas?
3. Ok, i taking sample repository and adding a new datasource in it:
Database: Oracle 8i
Connection pool:
Call interface OCI 8i/9i
Data source name:
(DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP) (Host = oraapp) (Port = 1521) ) ) (CONNECT_DATA = (SID = MYSID) ) )
This settings are working fine in BI 10.
In BI 11g i get this funny error: "The connection has failed". I lost my time in attempts to connect to Oracle DB 8, but have not results. After that i hacked button "Query DBMS" at "Features" tab, pressed it and when get error "ORA-03134: Connections to this server version are no longer supported.".
Therefore Oracle 8 DB as datasource not supported. Am i right?
4. In sample repository i added oracle DB 10 as datasource, then added two dual tables and their connection to all layers.
Now i open BI Answers, and trying to create report with one dummy column, Now i have this error:
Error
View Display Error
Odbc driver returned an error (SQLExecDirectW).
Error Details
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 42016] Check database specific features table. Must be able to push at least a single table reference to a remote database (HY000)
SQL Issued: SELECT s_0, s_1 FROM ( SELECT 0 s_0, "ORA10G"."dual"."dummy" s_1 FROM "ORA10G" ) djm
Database features are defaults.
Does anyone solve this problem?Turribeach, Thanks for you time.
1. It was not a question
3. Yes, i have read platforms, but not supported datasources. Now i see, that BI 11g support as datasource Oracle DB 9.2.0.7 or higher. I am sorry.
4. I'm using OCI connection type
Now i recreate Database in Physical schema and answers is showing report data for me! But only from one table, when i use columns from to tables from one datasource, i geting error:
Error View Display Error Odbc driver returned an error (SQLExecDirectW). Error Details Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 46008] Internal error: File server/Utility/Server/DataType/SUKeyCompare.cpp, line 875. (HY000) SQL Issued: SELECT s_0, s_1, s_2 FROM ( SELECT 0 s_0, "Ora10g"."hierarchy_obj_cust_v"."sort_order" s_1, "Ora10g"."NSI_SCHEMA"."SCHEMA_NAME" s_2 FROM "Ora10g" ) djm
Edited by: serzzzh on 03.09.2010 3:44 -
IPlanet J2EE application not working with oracle 9i but working with 7.3
We are in a process of upgrading database from oracle 7.3 to 9i.
We have a working application running on iPlanet Application Server with oracle 7.3 as database. We are using iPlanet Application Server's connection pooling. Our JDBC driver is classes111.zip.
After upgrading to 9i, our application doesnt work. When I try to run a test application that uses single select statement, this the error I get: java.sql.SQLException: Invalid URL: Driver type not specified
SQL*PLUS works fine. I havent upgraded oracle client. Do I need to upgrade the JDBC driver or oracle client?
Any suggestions? iAS version is 6.5.If you are new to JSF, then I'd try and simplify the environment in which you are working as the first step to achieving a successful outcome.
JSF 1.2 is a certified and well tested component of WLS, so we know it works. I'm not sure of the effect of all those additional modules you are adding in there -- it appears as if you have gotten a Faces implementation instantiated, but there could be some form of version difference/conflict since it can't find a method its looking for.
Using Oracle Enterprise Pack for Eclipse (http://www.oracle.com/technology/software/products/oepe/oepe_11115.html) you can build yourself out a pretty simple JSF application to get started from and deploy it to a WLS server. This would remove all the additional libraries you currently have, provide you with a bundled applicaton to deploy and give you a pretty good environment from which you can learn and experiment with JSF.
-steve- -
Remote JDBC Problem with Oracle BPM Studio
Hi all, i am facing the Remote JDBC Problem with Oracle BPM Studio.
When i configure a Remote JDBC Connection for SQL in BPM Studio, it prompt me an error.
The SQL Connection is configured as following :
External Resource:
Name : MyDS
Type : SQL Database
Supported Types : Remote JDBC
Details:
Database Type : BPM's Oracle Driver Version:10, 11
J2EE : WLS
Lookup Name : MyAppDS
Configuration for "WLS"
Name : WLS
Type : J2EE Application Server
Supported Types : GENERIC_J2EE
Details:
Initial Context Factory : weblogic.jndi.WLInitialContextFactory
URL : t3://localhost:7001
But, when i try to connect to the Database by using this configuration, I will get an Exception.
An exception occurred while getting a resource from a connector.
Detail:The connector [[ MyDS : SQL : REMOTE_JDBC ]] caused an exception when getting a resource.
Caused by: An exception occurred while getting a resource from a connector.
Detail:The connector [[ WLS : J2EE : J2EE ]] caused an exception when getting a resource.
Caused by: javax.naming.NoInitialContextException: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory [[ Root exception is java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory ]]
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:657)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at fuego.jndi.FaultTolerantContext.createContext(FaultTolerantContext.java:726)
at fuego.jndi.FaultTolerantContext.<init>(FaultTolerantContext.java:79)
at fuego.connector.impl.GenericJ2EEConnector.createInitialContext(GenericJ2EEConnector.java:177)
at fuego.connector.impl.GenericJ2EEConnector.createStandaloneContext(GenericJ2EEConnector.java:98)
at fuego.connector.impl.BaseJ2EEConnector.getResource(BaseJ2EEConnector.java:92)
at fuego.connector.impl.BaseJ2EEConnector.getResource(BaseJ2EEConnector.java:76)
at fuego.connector.J2EEHelper.getReadOnlyContext(J2EEHelper.java:86)
... 12 more
Edited by: user2262377 on Jun 22, 2009 4:01 PMI guess the weblogic.jar is not included in the studio.
So, i added weblogic.jar (Weblogic 10.3) and wlclient.jar (Weblogic 10.3)
It is working in my simple java code. But, still not working in BPM Studio.
The error logs:
An exception occurred while getting a resource from a connector.
Detail:The connector [OFT_APP_DS:SQL:REMOTE_JDBC] caused an exception when getting a resource.
Caused by: java.lang.Object cannot be cast to java.io.Serializable
fuego.connector.ConnectorException: An exception occurred while getting a resource from a connector.
Detail:The connector [OFT_APP_DS:SQL:REMOTE_JDBC] caused an exception when getting a resource.
at fuego.connector.ConnectorException.exceptionOnGetResource(ConnectorException.java:88)
at fuego.connector.JDBCHelper.getReadOnlyConnection(JDBCHelper.java:93)
at fuego.sqlintrospector.BrowserPanel.connect(BrowserPanel.java:395)
at fuego.sqlintrospector.BrowserPanel.populateTree(BrowserPanel.java:200)
at fuego.ui.wizards.ui.CheckTreeBrowser$1.construct(CheckTreeBrowser.java:63)
at fuego.ui.SwingWorker$2.run(SwingWorker.java:39)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.ClassCastException: java.lang.Object cannot be cast to java.io.Serializable
at weblogic.iiop.IIOPOutputStream.writeAny(IIOPOutputStream.java:1588)
at weblogic.iiop.IIOPOutputStream.writeObject(IIOPOutputStream.java:2231)
at weblogic.utils.io.ObjectStreamClass.writeFields(ObjectStreamClass.java:413)
at weblogic.corba.utils.ValueHandlerImpl.writeValueData(ValueHandlerImpl.java:235)
at weblogic.corba.utils.ValueHandlerImpl.writeValueData(ValueHandlerImpl.java:225)
at weblogic.corba.utils.ValueHandlerImpl.writeValue(ValueHandlerImpl.java:182)
at weblogic.iiop.IIOPOutputStream.write_value(IIOPOutputStream.java:1963)
at weblogic.iiop.IIOPOutputStream.write_value(IIOPOutputStream.java:2001)
at weblogic.iiop.IIOPOutputStream.writeObject(IIOPOutputStream.java:2266)
at weblogic.jdbc.common.internal.RmiDataSource_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173) -
XA error with Oracle 9.2.0.x / Weblogic 7 sp2
Hi,
I have encountered some problems when accessing Oracle 9i (9.2.0.2) via
Weblogic7 sp2 .
The problem occurs when a stateless session bean invokes a DAO that get a
connection from the datasource. The SLSB transaction attribute is set to
'required'.
This problem does not when using oracle.driver.OracleDriver or using Oracle
9.0.1.
Please help.
Thanks!
Regards...
<JDBCConnectionPool
DriverName="oracle.jdbc.xa.client.OracleXADataSource"
InitialCapacity="10" MaxCapacity="10" Name="MyConnectionPool"
Password="{3DES}EuCgBGHa7vhKa8GfpTjs4w==" Properties="user=psm"
ShrinkPeriodMinutes="1" ShrinkingEnabled="false"
SupportsLocalTransaction="false" Targets="myserver"
URL="jdbc:oracle:thin:@192.168.142.153:1521:oscdev"/>
<JDBCTxDataSource JNDIName="MyDataSource" Name="MyDataSource"
PoolName="MyConnectionPool" Targets="myserver"/>
java.sql.SQLException: XA error: XAER_RMERR : A resource manager error has
occured in the transaction branch start() failed on resource
'MyConnectionPool': XAER_RMERR : A resource manager error has occured in the
transaction branch
oracle.jdbc.xa.OracleXAException
at oracle.jdbc.xa.OracleXAResource.checkError(OracleXAResource.java:1157)
at oracle.jdbc.xa.client.OracleXAResource.start(OracleXAResource.java:295)
at weblogic.jdbc.jta.VendorXAResource.start(VendorXAResource.java:41)
at weblogic.jdbc.jta.DataSource.start(DataSource.java:569)
at
weblogic.transaction.internal.ServerResourceInfo.start(ServerResourceInfo.ja
va:1165)
at
weblogic.transaction.internal.ServerResourceInfo.xaStart(ServerResourceInfo.
java:1108)
at
weblogic.transaction.internal.ServerResourceInfo.enlist(ServerResourceInfo.j
ava:287)
at
weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTra
nsactionImpl.java:391)
at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1143)
at
weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1098)
at weblogic.jdbc.jta.Connection.getXAConn(Connection.java:145)
at weblogic.jdbc.jta.Connection.prepareStatement(Connection.java:211)
at
weblogic.jdbc.rmi.internal.ConnectionImpl.prepareStatement(ConnectionImpl.ja
va:139)
at
weblogic.jdbc.rmi.SerialConnection.prepareStatement(SerialConnection.java:81
Attached the error log and config.
[apps.log]
[config.xml]Which version of oracle database are you trying to connect to? we have seen some problems with oracle 920 thin driver. It will be good to use 9013 thin driver instead for now.
Mitesh
Wee Hong Ee wrote:
Hi,
I have encountered some problems when accessing Oracle 9i (9.2.0.2) via
Weblogic7 sp2 .
The problem occurs when a stateless session bean invokes a DAO that get a
connection from the datasource. The SLSB transaction attribute is set to
'required'.
This problem does not when using oracle.driver.OracleDriver or using Oracle
9.0.1.
Please help.
Thanks!
Regards...
<JDBCConnectionPool
DriverName="oracle.jdbc.xa.client.OracleXADataSource"
InitialCapacity="10" MaxCapacity="10" Name="MyConnectionPool"
Password="{3DES}EuCgBGHa7vhKa8GfpTjs4w==" Properties="user=psm"
ShrinkPeriodMinutes="1" ShrinkingEnabled="false"
SupportsLocalTransaction="false" Targets="myserver"
URL="jdbc:oracle:thin:@192.168.142.153:1521:oscdev"/>
<JDBCTxDataSource JNDIName="MyDataSource" Name="MyDataSource"
PoolName="MyConnectionPool" Targets="myserver"/>
java.sql.SQLException: XA error: XAER_RMERR : A resource manager error has
occured in the transaction branch start() failed on resource
'MyConnectionPool': XAER_RMERR : A resource manager error has occured in the
transaction branch
oracle.jdbc.xa.OracleXAException
at oracle.jdbc.xa.OracleXAResource.checkError(OracleXAResource.java:1157)
at oracle.jdbc.xa.client.OracleXAResource.start(OracleXAResource.java:295)
at weblogic.jdbc.jta.VendorXAResource.start(VendorXAResource.java:41)
at weblogic.jdbc.jta.DataSource.start(DataSource.java:569)
at
weblogic.transaction.internal.ServerResourceInfo.start(ServerResourceInfo.ja
va:1165)
at
weblogic.transaction.internal.ServerResourceInfo.xaStart(ServerResourceInfo.
java:1108)
at
weblogic.transaction.internal.ServerResourceInfo.enlist(ServerResourceInfo.j
ava:287)
at
weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTra
nsactionImpl.java:391)
at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1143)
at
weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1098)
at weblogic.jdbc.jta.Connection.getXAConn(Connection.java:145)
at weblogic.jdbc.jta.Connection.prepareStatement(Connection.java:211)
at
weblogic.jdbc.rmi.internal.ConnectionImpl.prepareStatement(ConnectionImpl.ja
va:139)
at
weblogic.jdbc.rmi.SerialConnection.prepareStatement(SerialConnection.java:81
Attached the error log and config.
Name: apps.log
apps.log Type: Text Document (application/x-unknown-content-type-txtfile)
Encoding: x-uuencode
<?xml version="1.0" encoding="UTF-8"?>
<!--If your domain is active, please do not edit the config.xml file. Any changes made to that file while the domain is active will not have any effect on the domain's configuration and are likely to be lost. If your domain is inactive, you may edit this file with an XML editor. If you do so, please refer to the BEA Weblogic Server Configuration Reference documentation available from http://edocs.bea.com/wls/docs70/config_xml. In general, we recommend that changes to your configuration file be made through the Administration Console.-->
<Domain ConfigurationVersion="7.0.0.0" Name="mydomain">
<Application Deployed="true" Name="DefaultWebApp"
Path="C:\bea\user_projects\mydomain\applications"
StagedTargets="" TwoPhase="true">
<WebAppComponent Name="DefaultWebApp" Targets="myserver" URI="DefaultWebApp"/>
</Application>
<Application Deployed="true" Name="certificate"
Path=".\applications" StagedTargets="" TwoPhase="false">
<WebAppComponent Name="certificate" Targets="myserver" URI="certificate.war"/>
</Application>
<Application Name="poc" Path="D:\HSA\src\deploy\poc.ear"
StagingMode="nostage" TwoPhase="true">
<EJBComponent Name="poc-hsa_waf-ejb.jar" Targets="myserver" URI="poc-hsa_waf-ejb.jar"/>
<EJBComponent Name="user-ejb.jar" Targets="myserver" URI="user-ejb.jar"/>
<WebAppComponent Name="poc.war/" Targets="myserver" URI="poc.war/"/>
</Application>
<ApplicationManager Name="mydomain"/>
<EmbeddedLDAP
Credential="{3DES}PMLvNRl/VFtDLKDdfidrUP5bYwm+FAcgdR+UXOY0YiY=" Name="mydomain"/>
<FileRealm Name="wl_default_file_realm"/>
<JDBCConnectionPool
DriverName="oracle.jdbc.xa.client.OracleXADataSource"
InitialCapacity="10" MaxCapacity="10" Name="MyConnectionPool"
Password="{3DES}EuCgBGHa7vhKa8GfpTjs4w==" Properties="user=psm"
ShrinkPeriodMinutes="1" ShrinkingEnabled="false"
SupportsLocalTransaction="false" Targets="myserver" URL="jdbc:oracle:thin:@192.168.142.153:1521:oscdev"/>
<JDBCTxDataSource JNDIName="MyDataSource" Name="MyDataSource"
PoolName="MyConnectionPool" Targets="myserver"/>
<JTA Name="mydomain"/>
<Log FileName=".\wl-domain.log" Name="mydomain"/>
<PasswordPolicy Name="wl_default_password_policy"/>
<Realm FileRealm="wl_default_file_realm" Name="wl_default_realm"/>
<SNMPAgent Name="mydomain"/>
<Security GuestDisabled="false" Name="mydomain"
PasswordPolicy="wl_default_password_policy"
Realm="wl_default_realm" RealmSetup="true"/>
<SecurityConfiguration
Credential="{3DES}22b8VM1wFkNwKqrWc093vhUk4XsQKkozia+O7H8K4I602imSpWAOlikFQyDOvETIj6mhrD+D+2/Ays3XL4PM//3Y2/TeWxHb" Name="mydomain"/>
<Server ListenPort="7001" Name="myserver" NativeIOEnabled="true"
ServerVersion="7.0.0.0" XMLEntityCache="XMLCacheMBean_myserver">
<COM Name="myserver"/>
<ExecuteQueue Name="default" ThreadCount="15"/>
<IIOP Name="myserver"/>
<JTAMigratableTarget Cluster="" Name="myserver" UserPreferredServer="myserver"/>
<KernelDebug Name="myserver"/>
<Log FileName=".\myserver\myserver.log" Name="myserver"/>
<SSL Enabled="true" HostnameVerificationIgnored="true"
ListenPort="7002" Name="myserver"
ServerCertificateChainFileName="ca.pem"
ServerCertificateFileName="democert.pem" ServerKeyFileName="demokey.pem"/>
<ServerDebug Name="myserver"/>
<ServerStart Name="myserver"/>
<WebServer DefaultWebApp="DefaultWebApp"
LogFileName=".\myserver\access.log" LoggingEnabled="true" Name="myserver"/>
</Server>
<XMLEntityCache Name="XMLCacheMBean_myserver"/>
</Domain> -
Hanging problem with Oracle JDBC thin driver
Hi. We have an application running on top of WLS 6.1 accessing Oracle 8I with oracle's
JDBC thin driver. Under stress testing, it appears to hang sometimes. Thread dump
shows that many threads seem to be stuck at the same line of code in JDBC driver
(at oracle.sql.NUMBER._isPositive(NUMBER.java:2882)). Has anyone run into similar
issue? Any help is much appreciated.
"ExecuteThread: '1' for queue: 'default'" daemon prio=5 tid=0xe18960 nid=0xf wai
ting on monitor [0xb3680000..0xb36819d8]
at oracle.sql.NUMBER._isPositive(NUMBER.java:2882)
at oracle.sql.NUMBER._fromLnxFmt(NUMBER.java:2953)
at oracle.sql.NUMBER.toBigDecimal(NUMBER.java:557)
at oracle.sql.NUMBER.bigDecimalValue(NUMBER.java:1872)
at oracle.jdbc.dbaccess.DBConversion.NumberBytesToBigDecimal(DBConversion.ja
va:1771)
at oracle.jdbc.driver.OracleStatement.getBigDecimalValue(OracleStatement.jav
a:3357)
at oracle.jdbc.driver.OracleStatement.getObjectValue(OracleStatement.java:41
66)
at oracle.jdbc.driver.OracleStatement.getObjectValue(OracleStatement.java:41
23)
at oracle.jdbc.driver.OracleResultSetImpl.getObject(OracleResultSetImpl.java
:401)
at weblogic.jdbc.jts.ResultSet.getObject(ResultSet.java:268)
at weblogic.jdbc.rmi.internal.ResultSetImpl.getObject(ResultSetImpl.java:592
at weblogic.jdbc.rmi.internal.ResultSetStraightReader.getObject(ResultSetStr
aightReader.java:198)
at weblogic.jdbc.rmi.SerialResultSet.getObject(SerialResultSet.java:682)
"ExecuteThread: '6' for queue: 'default'" daemon prio=5 tid=0x6d93a8 nid=0x14
wa
iting on monitor [0xb3180000..0xb31819d8]
at oracle.sql.NUMBER._isPositive(NUMBER.java:2882)
at oracle.sql.NUMBER._fromLnxFmt(NUMBER.java:2953)
at oracle.sql.NUMBER.toBigDecimal(NUMBER.java:557)
at oracle.sql.NUMBER.bigDecimalValue(NUMBER.java:1872)
at oracle.jdbc.dbaccess.DBConversion.NumberBytesToBigDecimal(DBConversion.ja
va:1771)
at oracle.jdbc.driver.OracleStatement.getBigDecimalValue(OracleStatement.jav
a:3357)
at oracle.jdbc.driver.OracleStatement.getObjectValue(OracleStatement.java:41
66)
at oracle.jdbc.driver.OracleStatement.getObjectValue(OracleStatement.java:41
23)
at oracle.jdbc.driver.OracleResultSetImpl.getObject(OracleResultSetImpl.java
:401)
at weblogic.jdbc.jts.ResultSet.getObject(ResultSet.java:268)
at weblogic.jdbc.rmi.internal.ResultSetImpl.getObject(ResultSetImpl.java:592
at weblogic.jdbc.rmi.internal.ResultSetStraightReader.getObject(ResultSetStr
aightReader.java:198)
at weblogic.jdbc.rmi.SerialResultSet.getObject(SerialResultSet.java:682)Try get the latest thin driver from oracle and place it in the beginning of
the classpath in the server startup script to use it. This seems like a
oracle thin driver bug, the newer driver might help.
sree
"Andrew Dong" <[email protected]> wrote in message
news:[email protected]...
>
Hi. We have an application running on top of WLS 6.1 accessing Oracle 8Iwith oracle's
JDBC thin driver. Under stress testing, it appears to hang sometimes.Thread dump
shows that many threads seem to be stuck at the same line of code in JDBCdriver
(at oracle.sql.NUMBER._isPositive(NUMBER.java:2882)). Has anyone run intosimilar
issue? Any help is much appreciated.
"ExecuteThread: '1' for queue: 'default'" daemon prio=5 tid=0xe18960nid=0xf wai
ting on monitor [0xb3680000..0xb36819d8]
at oracle.sql.NUMBER._isPositive(NUMBER.java:2882)
at oracle.sql.NUMBER._fromLnxFmt(NUMBER.java:2953)
at oracle.sql.NUMBER.toBigDecimal(NUMBER.java:557)
at oracle.sql.NUMBER.bigDecimalValue(NUMBER.java:1872)
atoracle.jdbc.dbaccess.DBConversion.NumberBytesToBigDecimal(DBConversion.ja
va:1771)
atoracle.jdbc.driver.OracleStatement.getBigDecimalValue(OracleStatement.jav
a:3357)
atoracle.jdbc.driver.OracleStatement.getObjectValue(OracleStatement.java:41
66)
atoracle.jdbc.driver.OracleStatement.getObjectValue(OracleStatement.java:41
23)
atoracle.jdbc.driver.OracleResultSetImpl.getObject(OracleResultSetImpl.java
:401)
at weblogic.jdbc.jts.ResultSet.getObject(ResultSet.java:268)
atweblogic.jdbc.rmi.internal.ResultSetImpl.getObject(ResultSetImpl.java:592
atweblogic.jdbc.rmi.internal.ResultSetStraightReader.getObject(ResultSetStr
aightReader.java:198)
atweblogic.jdbc.rmi.SerialResultSet.getObject(SerialResultSet.java:682)
>
"ExecuteThread: '6' for queue: 'default'" daemon prio=5 tid=0x6d93a8nid=0x14
wa
iting on monitor [0xb3180000..0xb31819d8]
at oracle.sql.NUMBER._isPositive(NUMBER.java:2882)
at oracle.sql.NUMBER._fromLnxFmt(NUMBER.java:2953)
at oracle.sql.NUMBER.toBigDecimal(NUMBER.java:557)
at oracle.sql.NUMBER.bigDecimalValue(NUMBER.java:1872)
atoracle.jdbc.dbaccess.DBConversion.NumberBytesToBigDecimal(DBConversion.ja
va:1771)
atoracle.jdbc.driver.OracleStatement.getBigDecimalValue(OracleStatement.jav
a:3357)
atoracle.jdbc.driver.OracleStatement.getObjectValue(OracleStatement.java:41
66)
atoracle.jdbc.driver.OracleStatement.getObjectValue(OracleStatement.java:41
23)
atoracle.jdbc.driver.OracleResultSetImpl.getObject(OracleResultSetImpl.java
:401)
at weblogic.jdbc.jts.ResultSet.getObject(ResultSet.java:268)
atweblogic.jdbc.rmi.internal.ResultSetImpl.getObject(ResultSetImpl.java:592
atweblogic.jdbc.rmi.internal.ResultSetStraightReader.getObject(ResultSetStr
aightReader.java:198)
atweblogic.jdbc.rmi.SerialResultSet.getObject(SerialResultSet.java:682)
>
> -
Transaction timed out with oracle 9i
Hi,
I am working with weblogic6.1.
Sometimes (very seldom) I have a problem which I don't undserstand.
The transaction stops and and after some time I get TimedOutException.
This time it happend in the findByPrimaryKey of a CMP Entity bean.
I have this problem only with Oracle 9i. with oracle8i everything works
fine.
I'm using oracle thin driver (I put oracle12.zip at the begin of weblogic
classpath)
Is this problem of oracle?
Does WLS 6.1 support Oracle9i?
Thanks for any hints
Szymon
stack trace:
javax.ejb.FinderException: Problem in findByPrimaryKey while preparing or
execut
ing statement: 'weblogic.jdbc.rmi.SerialPreparedStatement@197155':
java.sql.SQLException: The transaction is no longer active (status = Marked
roll
back. [Reason=weblogic.transaction.internal.TimedOutException: Transaction
timed
out after 561 seconds
Xid=21550:aea95ccd7f28edb9(4655671),Status=Active,numRepliesOwedMe=0,numRepl
iesO
wedOthers=0,seconds since begin=561,seconds
left=30,activeThread=Thread[ExecuteT
hread: '14' for queue: 'default',5,Thread Group for Queue:
'default'],ServerReso
urceInfo[weblogic.jdbc.jts.Connection]=(state=started,assigned=none),SCInfo[
mydo
main+myserver]=(state=active),properties=({weblogic.jdbc=t3://172.16.0.28:70
01})
,OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorUR
L=my
server+172.16.0.28:7001+mydomain+,
Resources={})],CoordinatorURL=myserver+172.16
.0.28:7001+mydomain+)]). No further JDBC access is allowed within this
transact
ion.
java.sql.SQLException: The transaction is no longer active (status = Marked
roll
back. [Reason=weblogic.transaction.internal.TimedOutException: Transaction
timed
out after 561 seconds
Xid=21550:aea95ccd7f28edb9(4655671),Status=Active,numRepliesOwedMe=0,numRepl
iesO
wedOthers=0,seconds since begin=561,seconds
left=30,activeThread=Thread[ExecuteT
hread: '14' for queue: 'default',5,Thread Group for Queue:
'default'],ServerReso
urceInfo[weblogic.jdbc.jts.Connection]=(state=started,assigned=none),SCInfo[
mydo
main+myserver]=(state=active),properties=({weblogic.jdbc=t3://172.16.0.28:70
01})
,OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorUR
L=my
server+172.16.0.28:7001+mydomain+,
Resources={})],CoordinatorURL=myserver+172.16
.0.28:7001+mydomain+)]). No further JDBC access is allowed within this
transact
ion.
at
weblogic.jdbc.jts.Connection.checkIfRolledBack(Connection.java:498)
at weblogic.jdbc.jts.Statement.setInt(Statement.java:606)
at
weblogic.jdbc.rmi.internal.PreparedStatementImpl.setInt(PreparedState
mentImpl.java:104)
at
weblogic.jdbc.rmi.SerialPreparedStatement.setInt(SerialPreparedStatem
ent.java:137)
at
com.verdisoft.datasource.ejb.contact.Person_vjvtzf__WebLogic_CMP_RDBM
S.ejbFindByPrimaryKey(Person_vjvtzf__WebLogic_CMP_RDBMS.java:1531)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.findByPrimaryKey(RDB
MSPersistenceManager.java:171)
at
weblogic.ejb20.manager.BaseEntityManager.findByPrimaryKey(BaseEntityM
anager.java:435)
at
weblogic.ejb20.manager.BaseEntityManager.localFindByPrimaryKey(BaseEn
tityManager.java:389)
at
weblogic.ejb20.internal.EntityEJBLocalHome.findByPrimaryKey(EntityEJB
LocalHome.java:266)
at
com.verdisoft.datasource.ejb.contact.PersonBean_vjvtzf_LocalHomeImpl.
findByPrimaryKey(PersonBean_vjvtzf_LocalHomeImpl.java:144)
at
com.verdisoft.datasource.ejb.contact.PersonBean.ejbHomeGetByKey(Perso
nBean.java:504)
at
com.verdisoft.datasource.ejb.contact.PersonBean_vjvtzf_LocalHomeImpl.
getByKey(PersonBean_vjvtzf_LocalHomeImpl.java:297)
at
com.verdisoft.datasource.ejb.EJBAdapterBean.getBeanAdapter(EJBAdapter
Bean.java:872)
at
com.verdisoft.datasource.ejb.EJBAdapterBean.updateItemInternal(EJBAda
pterBean.java:834)
at
com.verdisoft.datasource.ejb.EJBAdapterBean.updateItem(EJBAdapterBean
.java:808)
at
com.verdisoft.datasource.ejb.EJBAdapterBean_s83q9a_EOImpl.updateItem(
EJBAdapterBean_s83q9a_EOImpl.java:146)
at
com.verdisoft.datasource.DataAdapterManagerBean.updateItem(DataAdapte
rManagerBean.java:144)
at
com.verdisoft.datasource.DataAdapterManagerBean_plajw8_EOImpl.updateI
tem(DataAdapterManagerBean_plajw8_EOImpl.java:614)
at
com.verdisoft.datasource.DataAdapterManagerBean_plajw8_EOImpl_WLSkel.
invoke(Unknown Source)
at
weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:282)
at
weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerR
ef.java:97)
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
a:231)
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
.java:21)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:144)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
at
com.verdisoft.datasource.ejb.contact.Person_vjvtzf__WebLogic_CMP_RDBM
S.ejbFindByPrimaryKey(Person_vjvtzf__WebLogic_CMP_RDBMS.java:1715)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.findByPrimaryKey(RDB
MSPersistenceManager.java:171)
at
weblogic.ejb20.manager.BaseEntityManager.findByPrimaryKey(BaseEntityM
anager.java:435)
at
weblogic.ejb20.manager.BaseEntityManager.localFindByPrimaryKey(BaseEn
tityManager.java:389)
at
weblogic.ejb20.internal.EntityEJBLocalHome.findByPrimaryKey(EntityEJB
LocalHome.java:266)
at
com.verdisoft.datasource.ejb.contact.PersonBean_vjvtzf_LocalHomeImpl.
findByPrimaryKey(PersonBean_vjvtzf_LocalHomeImpl.java:144)
at
com.verdisoft.datasource.ejb.contact.PersonBean.ejbHomeGetByKey(Perso
nBean.java:504)
at
com.verdisoft.datasource.ejb.contact.PersonBean_vjvtzf_LocalHomeImpl.
getByKey(PersonBean_vjvtzf_LocalHomeImpl.java:297)
at
com.verdisoft.datasource.ejb.EJBAdapterBean.getBeanAdapter(EJBAdapter
Bean.java:872)
at
com.verdisoft.datasource.ejb.EJBAdapterBean.updateItemInternal(EJBAda
pterBean.java:834)
at
com.verdisoft.datasource.ejb.EJBAdapterBean.updateItem(EJBAdapterBean
.java:808)
at
com.verdisoft.datasource.ejb.EJBAdapterBean_s83q9a_EOImpl.updateItem(
EJBAdapterBean_s83q9a_EOImpl.java:146)
at
com.verdisoft.datasource.DataAdapterManagerBean.updateItem(DataAdapte
rManagerBean.java:144)
at
com.verdisoft.datasource.DataAdapterManagerBean_plajw8_EOImpl.updateI
tem(DataAdapterManagerBean_plajw8_EOImpl.java:614)
at
com.verdisoft.datasource.DataAdapterManagerBean_plajw8_EOImpl_WLSkel.
invoke(Unknown Source)
at
weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:282)
at
weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerR
ef.java:97)
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
a:231)
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
.java:21)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:144)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
com.verdisoft.datasource.exception.DataNotFoundException: Object not found:
data
source://private_addressbook/ejbcontact/john1025100151518/12770
at
com.verdisoft.datasource.ejb.EJBAdapterBean.getBeanAdapter(EJBAdapter
Bean.java:876)
at
com.verdisoft.datasource.ejb.EJBAdapterBean.updateItemInternal(EJBAda
pterBean.java:834)
at
com.verdisoft.datasource.ejb.EJBAdapterBean.updateItem(EJBAdapterBean
.java:808)
at
com.verdisoft.datasource.ejb.EJBAdapterBean_s83q9a_EOImpl.updateItem(
EJBAdapterBean_s83q9a_EOImpl.java:146)
at
com.verdisoft.datasource.DataAdapterManagerBean.updateItem(DataAdapte
rManagerBean.java:144)
at
com.verdisoft.datasource.DataAdapterManagerBean_plajw8_EOImpl.updateI
tem(DataAdapterManagerBean_plajw8_EOImpl.java:614)
at
com.verdisoft.datasource.DataAdapterManagerBean_plajw8_EOImpl_WLSkel.
invoke(Unknown Source)Irene Ho wrote:
Dear all,
When the java application program tries to insert the data (around 300
records). Sometimes, the error occurs as "EJB Exception:
weblogic.transaction.internal.TimedOutException: Transaction timed out after
95 seconds".
When the error occurred, only one java application was running. Furthermore,
I set the JTA-->Timeout Seconds to 30 in the thr the Weblogic console. The
configuration of the server is WebLogic 7.0 with SP2 and Oracle 8.1.7.
Anyone know what happen and how to resolve the problem? The error is due to
the entity bean, Weblogic or Oracle?
Thanks a lot.
IreneOr configuration. You can set your timeout to a different value. It is likely
to be an oracle problem. We don't do anything unnecessary to delay your application
code. You may be able to check the jdbc log or jta log to see when the tx starts and
how long it takes to progress. If you note a delay, you could take a server
thread dump to see what weblogic is doing. Typically it will be waiting for
Oracle to respond from a jdbc call.
Joe -
Upgrading from WLS 8.1 to Oracle WLS 10.3
Hi,
I'm planning to upgrade a client's system consisting of multiple applications running on WLS 8.1 to Oracle WLS 10.3.
Is this an officially supported upgrade path? What would be the best way to do the upgrade?
Are there any tools for automatically importing or converting the old configuration or domains?
Or is it better to create new installations from scratch and manually configure them?
Is there any documentation for this upgrade path?
In practice we would need to run both application servers in parallel for a while.
Can I expect the different server versions to interoperate with each other?
The applications mostly communicate using EJB (v2.0) calls but JMS and Web Services are used as well.
I've tested the EJB calls and they seem to work but what about JMS?Thanks.
Can WLS JMS v8.1 be used as a messaging provider for WLS v10.3 and 8.1 instances
(using it directly or through the Messaging Bridge)?
Is this described in the documentation somewhere?
I also found the following documents that address version compatibility:
http://download.oracle.com/docs/cd/E13222_01/wls/docs103/compatibility/compatibility.html
http://download.oracle.com/docs/cd/E13222_01/wls/docs103/upgrade/compat.html -
Petstore throws populateServlet error with Oracle thin driver
When i point connection pool to Oracle database, i get the following error. The
data is populated in the database, looks like when petstore is enumerating db
tables and make sure all tables exist, this error is happening. Some how, database
metadata coming as NULL. Has anybody tried petstore with Oracle JDBC driver?
thanks,
PopulateServlet Error:
java.lang.NullPointerException java.lang.NullPointerException at com.sun.j2ee.blueprints.tools.populate.web.PopulateServlet.checkTables(PopulateServlet.java:276)
at com.sun.j2ee.blueprints.tools.populate.web.PopulateServlet.doGet(PopulateServlet.java:127)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2456)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2039)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)I believe that you do not have weblogicaux.jar in your classpath.
-Selvan
Laurie Cohen wrote:
Im using Solaris 2.7 with WLS 5.1.0 and Commerce Server 2.0.1 with
current service packs on both. JDK 1.2.1_04 and the Oracle thin driver
(classes111.zip which I am told is the only one supported in this
configuration). Has anyone seen this problem? Is it that the driver is
using 1.1 and I only have 1.2 installed?
devapp01% java -classpath
/usr/local/weblogic/classes:/usr/local/weblogic/license utils.t3dbping
t3://localhost:7601 username password "" oracle.jdbc.driver.OracleDriver
jdbc:oracle:thin:@10.200.201.110:1521:q01c
Connecting to WebLogic with the WebLogic JDBC Driver
Exception in thread "main" java.lang.NoClassDefFoundError:
com/sun/java/util/collections/ArrayList
at weblogic.kernel.Kernel.declareProperties(Kernel.java:253)
at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:107)
at weblogic.common.T3Client.<init>(T3Client.java:218)
at weblogic.common.T3Client.<init>(T3Client.java:269)
at weblogic.common.T3Client.<init>(T3Client.java:323)
at weblogic.jdbcbase.t3.Driver.connect(Driver.java:121)
at java.sql.DriverManager.getConnection(Compiled Code)
at java.sql.DriverManager.getConnection(DriverManager.java:106)
at utils.t3dbping.main(t3dbping.java:115)
Thanks,
Laurie -
How to integrate Active Directory with Oracle Weblogic
hi
is there any Oracle Document that descripes how to integrate the LDAP Active directory with Oracle Weblogic 10.3
Regards
Edited by: qasas on 28-Nov-2009 13:56weblogic docs (and there identity asserters) - http://one-size-doesnt-fit-all.blogspot.com/2008/12/configuring-wls-with-ms-active.html
Maybe you are looking for
-
I have tried everything in all of these discussions and i still cant get my imessage or facetime to activate on my iphone 5c. Please help! I've been trying since Thursday!
-
Installing soa suite 11.1.1.2 failed
Hi, Failed to install Oracle Soa suite 11.1.1.2.0 on windows XP with DB 11g R1, jdk1.6 update 27 but pre-requisites passed. Below the log.. Temp Buffer: D:\installed\oracle\Middleware; middleware homes :1 isDefaultValueChangedfalse isDefaultValueChan
-
Password for Adobe Flash Player
When I try to 'install' the "New Version" of Adobe Flash Player it tells me to put in my ID and Password. I put in my ID and Password (I use the same one for everything, and I also have it written down) and it shakes it's head and won't let me do it.
-
PHP & JAVA (Unable to load Java Library)
Hello, I try to execute a script ncluding the call with JAVA routines, I obtain the following message: Fatal error: Unable to load Java Library /opt/j2sdk1.4.2_04/jre/lib/i386/libjava.so, error: libjvm.so: cannot open shared object file: No such file
-
Foxfire wants me to update but it says it will disable some of my kesperski anti virus software
I get a message that there is a newer version of firefox but when I go to install it there is a message saying it will interfere with my Kesperski anti virus software. may as well go back to IE if there are security issues with firefox and those upda