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?

Similar Messages

JDBC Type 3 driver problem with WLS 6.1 SP4

We have Oracle 8.1.7.4 client running on WebLogic 6.1 SP4 on Solaris 2.6 connecting to Oracle OPS 8.1.7 running on Solaris 2.6. We are getting core dumps while running stress testing using Load Runner for 100 concurrent users. The performance is very good for a while in the beginning of the test and all of a sudden we see requests for connections queueing up on the WLS and the server crashes. Please send us details of any previous instances any one faced similar problem and the fix applied will be very helpful.
Regards,
Raj

The Member Feedback forum is for suggestions and feedback for OTN Developer Services. This forum is not monitored by Oracle support or product teams and so Oracle product and technology related questions cannot be answered. We recommend that you post this thread to the SQLJ/JDBC forum.
The URL is: http://forums.oracle.com/forums/forum.jsp?forum=99
Thanks, OTN Team

Hard drive problem with HP Pavillion dv7-4180us

Hard drive problem with my HP Pavillion dv7-4180us. Using Windows 7.
Boots up sometimes and very slow.
Appreciate any help.

Have you booted into the BIOS or Diagnostics Tool to run the Hard Drive Test?

General install and deployment problem with WLS clustering on two boxes

Hi,
I've come across a general installation problem with WLS with a cluster spanning two different physical machines and two Managed Servers, one Managed Server per physical machine.
The problem is, starting from scratch, you install WLS on both physical machines. You can then use the config wizard to create the domain, cluster and managed servers, but this is a manual typing in process.
So we've now got a WLST Script which we run with "java weblogic.WLST domaincreate.py domain.properties". This is good as it creates the domain, cluster, managed servers and JMS modules.
Now the trouble is, it doesn't do anything to the 2nd physical machine which will be running only the 2nd Managed Server.
One dirty way to get around this in order to start the 2nd managed server was to copy the domain directory to the 2nd server, but I'm sure this is bad practice and what you can actually do is improve the WLST script to actually, but the same as the config wizard and dump the nessary information to the 2nd physical machine in order so you don't need to copy the domain directory across so that it will startup straight after running the WLST.
Any help appriecated.
Surfbum.

Hi I think I've found the answer. You can build a managed server template using the pack command.
http://e-docs.bea.com/common/docs90/pack/tasks.html

Apache-soap Problem with WLS 5.1sp9

I have problem with WLS 5.1sp9.
My environment is the following :
jaf-1.0.1
javamail-1.2
soap-2.2
xerces-1.4.4
and I want to call EJB.
So, I write some EJB and deploy it.
And rpcrouter work!!
Success to deploy the Service.
But I run into problem with calling this ejb.
This error is the following.
SOAP-ENV:Server.BadTargetObjectURI
Unable to resolve target object: BC2_BoardSync
please, help me.
here's my example..
ps.
sorry for my poor English..T_T
[ws5.10.zip]
[vb.zip]

I have problem with WLS 5.1sp9.
My environment is the following :
jaf-1.0.1
javamail-1.2
soap-2.2
xerces-1.4.4
and I want to call EJB.
So, I write some EJB and deploy it.
And rpcrouter work!!
Success to deploy the Service.
But I run into problem with calling this ejb.
This error is the following.
SOAP-ENV:Server.BadTargetObjectURI
Unable to resolve target object: BC2_BoardSync
please, help me.
here's my example..
ps.
sorry for my poor English..T_T
[ws5.10.zip]
[vb.zip]

Problems with WAS 6.40 Installation on Oracle - Phase 11 of 34

Hello,
Problems with WAS 6.40 Installation on Oracle (Phase 11 of 34)
with the installation of the Web Application server 6,40 SR1 on a Oracle server I get in phase 11 of 34 (Create Oracle Database) the following error-message:
CJS-00084 - SQL statement or script failed. Diagnosis: Error message: ORA-12547: TNS:lost contact.
error while loading shared library: libodm9.so : cannot open shared object file: No such file or dirctory.
Best Reagrds,
Ralf Steffens

hi Ralf
i've found one composite note for Oracle <a href="https://websmp203.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700001366932002">505630</a>
hope this solves...
Symptom
ORA-12547: TNS:lost contact
Brbackup, brarchive, brrestore or brconnect may terminate with errors similar to the following:
BR301E SQL error -12547 at location BrDbConnect-1
BR301E SQL error -12547 at location dbf_info_get-1
Sapdba returns the following error, for example:
SAPDBA: ORACLE error -12547 occurred while checking instance status!
The R/3 work processes or R3trans return the following error at Connect:
C *** ERROR => CONNECT failed with sql error '12547'
Other terms
TNS-12547, TNS-00517
Reason and Prerequisites
As part of the Net8 Connect, a program such as the R/3 kernel, R3trans, svrmgrl, sqlplus or ODMA establishes a connection to the Oracle database. If the connection terminates due to problems at the server end, it can result in ORA-12547.
Additional information for the error is often available in sqlnet.log. In many cases, other messages that are not reported by all tools precede ORA-12547. If ORA-12547 occurs when the ODMA accesses the old Oracle-Home during a database upgrade, for example, it may make sense to temporarily restart ORACLE_HOME on the old Oracle-Home for test purposes and then to execute sqlplus or svrmgrl.
Even if sapdba or the BR tools terminate with an ORA-12547 when calling sqlplus or svrmgrl recursively, you should, for test purposes, call sqlplus or svrmgrl manually with the operating system user that was used.
Hopefully, a more informative error message will appear in addition to ORA-12547, for example:
ld.so.1: oracleC11: fatal: relocation error: file
 /oracle/C11/817_64/libx8.so: symbol ksunsga_:
 referenced symbol not found
If you find accompanying error messages of this type, start a note search with the corresponding search terms since we are often aware of the problem and a solution may already be available. If you do not find any significant error messages or a suitable note, check the following possible causes for ORA-12547:
1. UNIX: Incorrectly linked Oracle tools
2. UNIX: Problems with XPG4 compliance and s-bit
3. Too many requests to the listener at the same time
4. HP-UX, Oracle 8.1: Missing OS patch
5. Use of CRYPTO parameters in sqlnet.ora
6. AIX: I/O Async is deactivated
7. Resource problems
8. The CONNECT_TIMEOUT_LISTENER parameter in listener.ora is too low
9. Activated Oracle trace
10. UNIX: Incorrect oracle executable authorization
11. SOLARIS: LD_LIBRARY_PATH set when you call ODMA
12. AIX: Problem with post/wait kernel enhancement
13. UNIX: Problems with the libobk library
14. SOLARIS: Incorrect search sequence in the path variable
15. UNIX: Conflicts between 32-bit and 64-bit files
Solution
1. Relink the Oracle software as ora<sid> with
cd $ORACLE_HOME/rdbms/lib
make -f ins_rdbms.mk install
 or
relink all
1. See Note 88884.
2. If individual work processes terminate with ORA-12547 when you start an R/3 instance, See Note 131561.
3. See Note 399610.
4. You can set security parameters that begin with SQLNET.CRYPTO_ in sqlnet.ora as part of the Advanced Security Option. Oracle releases < 8.1.7 cannot process these parameters correctly and result in ORA-12547. In this case, delete these types of parameters from sqlnet.ora.
5. If I/O is deactivated on AIX Async, the Net8 Connect fails with ORA-12547. In this case, activate I/O Async by using smitty.
6. Insufficient resources such as available memory on the database server can cause ORA-12547. For more information, see 384839.
7. In individual cases, it may make sense to increase the CONNECT_TIMEOUT_LISTENER parameter in listener.ora (for example, by 5 seconds, so from 10 to 15). Although a value of 10 seconds should usually be sufficient to establish a connection.
8. Delete the log files written by the Oracle trace in accordance with Note 92537.
9. Check to see whether the executable in $ORACLE_HOME/bin has the "rwsr-s--x" authorizations and the ora<sid> owner and correct this if necessary.
10. If you call ODMA on SOLARIS as part of a database upgrade and if LD_LIBRARY_PATH is set explicitly (on the lib directory of the target release), calling the old Oracle software through ODMA may fail with ORA-12547. If you use the old ORACLE_HOME to list sqlplus or svrmgrl, you get the following error:
ld.so.1: oracle<sid>: fatal: relocation error:
 file /oracle/<sid>/817_64/libx8.so: symbol ksunsga_:
 referenced symbol not found
ORA-12547: TNS:lost contact
 In this case, permanently delete LD_LIBRARY_PATH from the environment. This does not have any negative effects since the libraries are automatically found in the correct directories as of Oracle 8.1.
 If problems occur with the post/wait extension on AIX, the following type of errors will be displayed:
exec(): 0509-036 Cannot load program oracleC11 because of the
following errors:
 0509-130 Symbol resolution failed for oracle because:
 0509-136 Symbol pw_post (number 2524) is not exported
 from dependent module /unix.
 0509-136 Symbol pw_wait (number 2525) is not exported
 from dependent module /unix.
 0509-136 Symbol pw_config (number 2526) is not exported
 from dependent module /unix.
 0509-192 Examine .loader section symbols with the
 'dump -Tv' command.
ORA-12547: TNS:lost contact
1. If the libobk library was created incorrectly, the following type of errors may occur:
/oracle/C11/817_64/bin/oracle: /sbin/loader:
 Fatal Error: Cannot map library libobk.so
/usr/lib/pa20_64/dld.sl: Unable to find library
 '/oracle/C11/lib64/libobk.sl
exec(): 0509-036 Cannot load program oracleC11 because of the
 following errors:
0509-150 Dependent module /oracle/C11/817_64/lib/libobk.a(shr.o)
 could not be loaded.
0509-152 Member shr.o is not found in archive
ORA-12547: TNS:lost contact
 Check to see whether libobk exists and, if it is a link, that it points to a valid object. Note 142635 contains more information about this. The libobk link may point to this if a libsbtsh8.* file exists in the Oracle library directory. If you are using a third-party Backint tool, contact the relevant supplier, since libobk often has to point to a backint-specific library.
1. If an error such as
ld.so.1: ./svrmgrl: fatal: libucb.so.1: open failed:
 No such file or directory
ORA-12547: TNS:lost contact
 occurs, the PATH has probably been set incorrectly. For more information, see Note 44361.
1. If an error such as
ld.so.1: oracle<sid>: fatal: <library> wrong ELF class: ELFCLASS64
ORA-12547: TNS:lost contact
 concerning "wrong ELF class" occurs, check whether the <library> mistakenly has a different bit size than the tool that was called. You can determine this using
file <library>
file <tool>
 All the files involved must uniformly be either 32-bit or 64-bit.

Regards
Arunkumar

MOVED: Driver problems with Windows Professional XP 64bit Edition

This topic has been moved to Operating Systems.
Driver problems with Windows Professional XP 64bit Edition

Well, after looking around the forum here I found an answer that works! I wish I could remember who to give credit too though. I installed the latest Vista drivers and I got static all the time. I tried another members suggestion of disabling the X-Fi device in the Device manager every time I log off and then enable the X-Fi the next time I log in. I have great sound as long as I do that. Also, for connecting to a home system I am using the DTS-60, $00 on this website, but it works well if you havea DTS decoder. I am using the X-Fi extreme Music edition. Good Luck, hopefully another driver is on the way.

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 8.1.5 JDBC driver problem with LONGVARCHAR

Hi, I'm having problem with 8.1.5 release on Solaris with the
JDBC type 4 driver (thin). If I create the following table
create table test1 (col1 NUMBER, col2 LONG);
Using JDBC driver to insert into the second column any string
longer than 4000 characters causing run time exception. The type2
driver works fine, but type2 is slow.
String sql = "insert into test1 (col1, col2) values (1099,?)";
PreparedStatement stmt ;
stmt = conn.prepareStatement(sql);
// create a string with very long value , bigger than 4096
stmt.setString(1,string);
stmt.executeUpdate();
runtime exception:
java.sql.SQLException: Data size bigger than max size for this
type
at java.lang.Throwable.<init>(Compiled Code)
at java.lang.Exception.<init>(Compiled Code)
at java.sql.SQLException.<init>(Compiled Code)
at oracle.jdbc.dbaccess.DBError.check_error(Compiled
Code)
at oracle.jdbc.ttc7.TTCItem.setArrayData(Compiled Code)
at
oracle.jdbc.driver.OraclePreparedStatement.setItem(Compiled Code)
at
oracle.jdbc.driver.OraclePreparedStatement.setString(Compiled
Code)
at testi.main(Compiled Code)
Any help is appreciated.
Thanks
Steve
null

Post the full stacktrace here
Also you might want to post jdbc related questions to weblogic.developer.
interest.jdbc
Kumar
DreamNEON wrote:
Hello,
the NSAPI integration works, also the JSP files.
But I have still problems with the Jdriver for my Oracle 8.1.5.
I get the message :
Failed to invoke startup class
weblogic.jdbc.common.internal.JdbcStartup=weblogic.jdbc.common.internal.JdbcStartup
when the WebLogic Server is started.
Any ideas or hints about that?
Thanks in advance
Armin

Oracle RDB Driver fails with JDBC/ODBC Bridge

Has anyone experienced problems using the latest Oracle RDB
Driver (3.0.2.0) with the JDBC/ODBC Bridge.
We have been using the Oracle ODBC Driver for RDB (2.10.17)
successfully on NT, but it is not supported on W2K. The new
drivers work fine for Access etc., but fail with the bridge.
Specifically, you can step thru a result set, but getObject()
returns null for all fields.
Any suggestions?
Joe

This forum is for general suggestions and feedback about the OTN
site. For technical question about an Oracle product, you can
select the appropriate discussion forum in our 'Discussions'
section at: http://forums.oracle.com/forums/homepage.jsp
Best regards, OTN Team

Oracle jdbc driver problems in netbeans 5.5

need help again....i'm experience a problem. the problems are :
i connect from netbeans 5.5 to oracle database express client 10g using jdbc driver ojdbc14.jar. the connection succeded (all the tables appears and i even can view the data). but when i trying to bind data to a drop down list component (with right click to the dropdown list component and then bind data), the dataprovider of that table appear in red color and there's no field appears in that. i'm so confused? i already add the ojdbc14.jar driver to the following path :
1. i create a new class library in netbeans with consist of that driver,
then added to my project (right click in my project then add library).
2. then i added the ojdbc14.jar driver to my tomcats lib at "C:\Program
Files\netbeans-5.5\enterprise3\apache-tomcat-5.5.17\common\lib".
Is there any additional settings in using oracle jdbc driver? Does anyone knows? thanks a lot for the answers...
Message was edited by:
darma_sadha

Hi!
I'm using NetBeans 6.5 and I'm having some troubles to connect.
The steps I've made:
- Create the connection pool in Glassfish, nothing special, just standard parameters (Based on javax.sql.DataSource and including URL, Username and Password).
- Create the JDBC resource associated with that connection pool,let's say jdbc/test.
Now in NetBeans I register the driver:
- New driver -> Find the ojdbc14.jar and from the options that I can choose it shows: oracle.jdbc.OracleDriver and oracle.jdbc.driver.OracleDriver.
If i choose without +.driver+ I got the thin drivers (the ones i want) and if i chosse the one with the other one I got the OCI drivers. So I choose the first option oracle.jdbc.OracleDriver
- Then I go to my project and click New -> Entity Classes from Database and from Datasource I select jdbc/test and it shows the following error message:
Unable to find the driver oracle.jdbc.driver.OracleDriver. Please register this driver in the Databases.
I can fix it if while registering the ojdbc14.jar I select the second option (*oracle.jdbc.driver.OracleDriver*) but with this option I need to specity the connection to use OCI instead of the desired thin driver.
I hope you'll understand and help me somehow
Edited by: KILE on Oct 10, 2008 2:26 AM

Oracle JDBC Driver Problem

Hi,
When I write code as
Resultset rs = .....
rs.last();
there is no problem for MySQL JDBC Driver, but when I use this code for Oracle, I am getting error with line 2. Why ? Do you know any Oracle JDBC Driver that supports "rs.last()" ? Or is there another way to handle it?
Thanks.

Most of the JDBC Drivers can handle "rs.last()".
The question here is, how do you create a Scrollable ResultSet using DatabaseMetaData, or if this is even possible.
A thorough read of the API docs, for the Classes and methods being used here will answer this question (now that you know what the actual question is).

ODBC Driver problem with GetSchema("ProcedureParameters")

Hi,
i'm using Oracle ODBC Driver version 9.2.08 with ADO.net and trying to get
list of procedure parameters using the standard GetSchema ODBC connection method. I always get an empty datatable (of course i'm sure that on my schema i've some procedures with parameters).
Using Microsoft Oracle ODBC Driver i don't have this problem (it runs fine)
Can someone help me ?
Thanks in advance

I'm simple use the following VB net code:
Dim odbccn As System.Data.Odbc.OdbcConnection = New System.Data.Odbc.OdbcConnection("DSN=OraDSN;UID=user;PWD=pwd")
odbccn.Open()
Dim DataTable As DataTable = odbccn.GetSchema("ProcedureParameters")
the DataTable is empty when OraDSN use ORACLE ODBC Driver... it runs when use Oracle Microsoft Driver
I know how get list of Parameters using oracle catalogues but i need use standard ODBC Call...
Thanks for your reply

Oracle JDBC driver problem for Canada locale

Hi, there:
I have problem on Oracle JDBC thin driver with Canada locale on client side:
I'm using Oracle9i thin jdbc driver, the nls parameters in oracle database is:
NLS_LANGUAGE: AMERICAN
NLS_TERRITORY: AMERICA
NLS_NUMERIC_CHARACTERS : .,
My java client side is running on Windows NT, which using jdbc thin driver to connect oracle database. If I set the locale in client side as "English(Canada)", it seems return me "French" number format, like ",45" (comma, instead of decimal point) for "0.45". However, If I set client side locale as "English(United States)", it returns me "0.45" as expected.
So, my question: does Oracle JDBC driver always returns "French" number format evenif I set "English(Canada)" as locale? Because Canada have both English and French locale "French(Canada), and English(Canada)". How can I get "English" number format like "0.45" with "English(Canada)" locale setting?
Really appreciated any reply, and thanks a lot in advance
David

Sounds like a question for Oracle Support to me.
Anyway, the way to avoid the problem is to not ask Oracle to format numbers. Get the number directly (via ResultSet.getInt() or getDouble() or whatever) and ask Java to format it.

Oracle 9i installation problem with RedHat 7.2 (segmentation violation)

I have try to installation 9i with RedHat 7.2 by x windows.
when i use xwin to run the "./runInstaller, i got the error
(segmentation) as below:
i have already try to follow the installation procedure in
http://staff.in2.hr/denis/oracle/901install_rh72_en.html#1 but
still got this error.
Can anyone help me??
Regards
Chris Sung
=================================================================
===============
oracle install
Connecting 192.168.1.3 via TELNET
Thursday, December 13, 2001 1:04:06
Red Hat Linux release 7.2 (Enigma)
Kernel 2.4.7-10 on an i686
login: oracle
Password:
Last login: Thu Dec 13 00:46:39 from apple
[oracle@orange oracle]$ (/home/oracle/Disk1/runInstaller -
display 192.168.1.2:0
-name "oracle install" &)
[oracle@orange oracle]$ Initializing Java Virtual Machine
from /tmp/OraInstall/jre/bin/jre. Please wait...
SIGSEGV 11* segmentation violation
 stackbase=0xbffff298, stackpointer=0xbffff160
Full thread dump:
"Finalizer thread" (TID:0x4276d210, sys_thread_t:0x4d0bfe0c,
state:R) prio=1
"Async Garbage Collector" (TID:0x4276d258,
sys_thread_t:0x4d09ee0c, state:R) prio=1
"Idle thread" (TID:0x4276d2a0, sys_thread_t:0x4d07de0c,
state:R) prio=0
"Clock" (TID:0x4276d088, sys_thread_t:0x4d05ce0c, state:CW)
prio=12
"main" (TID:0x4276d0b0, sys_thread_t:0x80d6fe8, state:R)
prio=5 *current thread*
 java.lang.System.initializeSystemClass(System.java)
Monitor Cache Dump:
Registered Monitor Dump:
Thread queue lock: <unowned>
Name and type hash table lock: <unowned>
String intern lock: <unowned>
JNI pinning lock: <unowned>
JNI global reference lock: <unowned>
BinClass lock: <unowned>
Class loading lock: <unowned>
Java stack lock: <unowned>
Code rewrite lock: <unowned>
Heap lock: <unowned>
Has finalization queue lock: <unowned>
Finalize me queue lock: <unowned>
Dynamic loading lock: <unowned>
Monitor IO lock: <unowned>
Child death monitor: <unowned>
Event monitor: <unowned>
I/O monitor: <unowned>
Alarm monitor: <unowned>
 Waiting to be notified:
 "Clock" (0x4d05ce0c)
Monitor registry: owner "main" (0x80d6fe8, 1 entry)
Thread Alarm Q:

Strange, but yesterday I nter in Oracle9i install, open
gnome-terminal window as oracle user and simply type
/tmp/Disk1/runInstaler
the DISPLAY enviroment variable was set,
using RedHat 7.2 , kernel 2.4.16-0.9, glibc-2.2.4-19
Segmentation violation 11 may mean RAM problem, sometimes
incorrect program pointer.So I think it must work (runIstaler)

Oracle XA driver problem with WLS 7.0.1.0, Oracle 9.0.1

Similar Messages

Maybe you are looking for