Thin instead of oci driver
i am working with advanced queue.
Message jms_msg = null;
TopicReceiver t_recv = null;
jms_msg = (t_recv.receive(10));
for this i need oci driver. Is it possible to use thin driver instead?
Edited by: user13256715 on 20.7.2010 23:47
AW> Hi Henry. My comments are preceded with AW>.
I upgraded my oracle client from 8i to 9i. I am trying to connect to 9ifs server running on different machine using Ifs api.
When i use the following url in IfsDefault.properties then i get the exception("ORA-12514: TNS:listener could not resolve SERVICE_NAME ") while creating LibrarySession
IFS.SERVICE.JDBC.DatabaseUrl=jdbc:oracle:oci8:@MYEST
Note: TNDPing works fine for MYTEST service. When i was using the oracle 8 client + drivers i have no problem conneting to 9ifs using the above urlAW> This problem should also manifest through SQL*Plus.
AW> You should compare your TNSNAMES.ora and your SQLNET.ora from Oracle8 versus Oracle9i, and see what the differences are. There may be a typo, or you may need to append ".world" to the end of your service name. Ask the SQL*Net people for more help on this.
Everything works file if use the following url in ifsDefault.properties file
IFS.SERVICE.JDBC.DatabaseUrl=jdbc:oracle:thin:@mydbmachine:1521:MYTEST.
My question is it ok to use thin driver instead of oci driver for ifs connection. Would it cause any problem when i move my java code to production machine and use the thin driver for ifs connection AW> Unfortunately, the thin driver is not certified. There are performance problems when retrieving large documents across the net, and there have been unconfirmed instability problems.
AW> Hope that helps.
AW> Alan
AW> iFS Product Management
Similar Messages
-
Poor performance caused by using OCI driver?
[Sorry for the multipost]
I'm working on a medium-sized Apache / Tomcat / WLS 5.10 / Oracle
system hosted on some 4-processor Suns. The Apache / Tomcat tier
uses one box, the WebLogic tier uses another, and the Oracle tier
uses a third.
We've found that the performance, measured as the time it takes user
operations like loading a page that displays database data, gets
unacceptably bad at suspiciously low loads. When the system is in
this state, none of the machines appears to be pushed very hard.
There's no significant paging going on, the disk and network I/O
isn't out of line, and the CPU load just isn't high enough to
explain what's going on. Only the WebLogic tier shows a load over
10%. When the system is perceived as too slow by the users, the
CPU load on this tier is only 30-40%.
To try to find out what's going on, I did a series of thread dumps.
When the system is heavily loaded, I only see about three Oracle
statements currently being processed (runnable threads with call
stacks inside weblogic.db.oci.*). What I do see lots of is blocked
(and one runnable) threads inside
weblogic.rjvm.RJVMImpl.removePeerGoneListener or
weblogic.rjvm.RJVMImpl.addPeerGoneListener. These threads appear to
be attempting to obtain or release database connections.
I don't know why, but the site is configured to use the WebLogic OCI
driver for Oracle, instead of the Oracle-supplied thin driver. Is what I'm
seeing what Sun is describing in this paragraph
(excerpted from http://java.sun.com/docs/hotspot/PerformanceFAQ.html#24):
Oracle provides two types of database drivers: a type-2
driver, called the OCI (Oracle Call Interface) driver
that utilizes native code, and a type-4 pure Java driver
called the thin driver. In single processor environments,
the thin driver works somewhat better than the OCI driver
because of the JNI overhead associated with the OCI
driver. On multi-processor configuations, synchronization
points within Solaris used by the OCI driver become big
bottlenecks and prevent scaling. We recommend using the
thin driver in all cases.
-- ErikHi. I'll chip in here too. Yes, you are wasting JVM cycles having all those
wasted threads. Threads aren't free, inexhaustable sources of compute power
that some people assume (I'm not saying you're one). All these threads do
share a single OS process and CPU. The JVM has to check all these all the
time to see if they have something to do. I recommend configuring the
server to run about 15 or 20 execute-threads.
I see only one thread waiting on Oracle to return data, so I don't think this
is a JDBC issue necessarily. What I do see is lots of threads trying to operate
on a Vector, all being blocked, or at least serialized by the lock this thread has, below.
Is the server hung at this point, or just slow?
"ExecuteThread-109" daemon prio=5 tid=0x311fb8 nid=0x78 runnable [0xcf9ff000..0xcf9ffc68]
at java.util.Vector.removeElementAt(Vector.java:509)
at java.util.Vector.removeElement(Vector.java:598)
at weblogic.rjvm.RJVMImpl.removePeerGoneListener(RJVMImpl.java:352)
at weblogic.time.server.ScheduledTrigger.destroy(ScheduledTrigger.java:112)
at weblogic.time.server.ScheduledTrigger.cancel(ScheduledTrigger.java:100)
at weblogic.jts.internal.CoordinatorImpl.cancelCurrentTimer(CoordinatorImpl.java:199)
at weblogic.jts.internal.CoordinatorImpl.commit(CoordinatorImpl.java:404)
at weblogic.jts.internal.TxContext.commit(TxContext.java:255)
at weblogic.ejb.internal.StatelessEJBObject.postInvokeOurTx(StatelessEJBObject.java:103
at weblogic.ejb.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:849)
at com.xxx.yyy.as.TaskSessionEJBEOImpl.findTaskByFilter(TaskSessionEJBEOImpl.java:784)
at
com.xxx.yyy.as.TaskSessionEJBEOImpl_WLSkel.invoke(TaskSessionEJBEOImpl_WLSkel.java:101)
at
weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAdapter.java:347)
at
weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandler.java:96)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:15)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
Erik Horstkotte wrote:
"Rob Woollen" <[email protected]> wrote in message
news:[email protected]...
You generally need a lot of data to find the performance problem in
a distributed system like this.Understood, but I was hoping that someone would recognize my description
as the "signature" of the locking problem with the OCI driver that Sun
describes.
It's very easy to switch to the Thin driver so you might as well
try it.I had hoped so, and in most cases, you're likely correct. Unfortunately,
the OCI driver is a touch more permissive than the thin driver. Some
errors (too many bind parameters) have crept in to our code that don't
cause problems for the OCI driver, but cause exceptions to be thrown by
the thin driver. In this particular case, I'm trying to solve a problem on
a production system - fixing the code there isn't an option (we are
switching to thin driver in our next release, so we are fixing these
problems).
If that doesn't help, I would suggest inserting some timing logic
in your code. In particular, I'd want to know the time a request
entered apache/tomcat, left apache/tomcat, entered WLS, left WLS
(to go to the database), returned from the database, left WLS, got
back to apache/tomcat, and finally left apache/tomcat to return the
response. With information like that, you should be able to narrow
down the problem a bit.In the next release, this is a good idea, and we'll probably do something
much like this. Unfortunately I can't make changes to the code on the
production site, so I have to rely on more passive methods of data
collection for the moment.
"Slava Imeshev" <[email protected]> wrote in message
news:[email protected]...
There can be other reasons for bad performance ranging from
serialized access to singletons to inefficient queries to
server mis-configuration. I have some doubts that oci driver
would affect performance at low loads.I don't see any evidence of serialization blocking, except for the
interesting locking issue that I mentioned in the original message (a
PeerGoneListener table maintained somewhere down inside WLS).
I'm certain that inefficient queries play a large role in our
performance problems.
Service mis-configuration could very well play a role here. Note for
example the large number of blocked idle execute threads in the thread
dump below. Clearly this instance has way too many execute threads. Not
knowing the internal architecture of WebLogic Server, nor the
implementation method Sun used for monitors in Solaris JVM 1.4.2, I don't
know how much of an impact an excess of execute threads has on
performance. Anyone?
Could you post a questionable thread dump here?See the bottom of this message. The dump has been "blinded" to remove some
customer-specific information.
Also, what's the load in terms of number of concurrent users
and requests per second?At peak load, there are about 60 users logged in, of whom only about 4-12
actually do much. The number of requests per second is very peaky, and
varies from about 1-10 per second. The complexity of requests also varies
wildly.
I've attached a thread dump from a point in time when the WebLogic Server
instance was taking about 30% of the CPU.
Any and all ideas are appreciated.
-- Erik
Full thread dump:
"HighPriority TimeEventGenerator" daemon prio=9 tid=0x4223ed0 nid=0xa7 waiting on monitor [0xcceff000..0xcceffc68]
at java.lang.Object.wait(Native Method)
at weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:279)
at weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:141)
at java.lang.Thread.run(Thread.java:484)
"ListenThread" prio=5 tid=0x423f7a0 nid=0xa6 runnable [0xccbff000..0xccbffc68]
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:421)
at java.net.ServerSocket.implAccept(ServerSocket.java:243)
at java.net.ServerSocket.accept(ServerSocket.java:222)
at weblogic.socket.WeblogicServerSocket.accept(WeblogicServerSocket.java:26)
at weblogic.t3.srvr.ListenThread.run(ListenThread.java:325)
"NBExecuteThread-1" daemon prio=5 tid=0x331ea0 nid=0xa2 waiting on monitor [0xccfff000..0xccfffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"NBExecuteThread-0" daemon prio=5 tid=0x3317b8 nid=0xa1 waiting on monitor [0xcd0ff000..0xcd0ffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-149" daemon prio=5 tid=0x330228 nid=0xa0 runnable [0xcd1ff000..0xcd1ffc68]
at weblogic.socket.PosixSocketMuxer.poll(Native Method)
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:290)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread-148" daemon prio=5 tid=0x32f740 nid=0x9f waiting on monitor [0xcd2ff000..0xcd2ffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-147" daemon prio=5 tid=0x32ec58 nid=0x9e waiting for monitor entry [0xcd3ff000..0xcd3ffc68]
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:289)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread-146" daemon prio=5 tid=0x32e170 nid=0x9d waiting for monitor entry [0xcd4ff000..0xcd4ffc68]
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:289)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread-145" daemon prio=5 tid=0x32ce80 nid=0x9c waiting on monitor [0xcd5ff000..0xcd5ffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-144" daemon prio=5 tid=0x32c398 nid=0x9b waiting for monitor entry [0xcd6ff000..0xcd6ffc68]
at java.util.Vector.removeElement(Vector.java:595)
at weblogic.rjvm.RJVMImpl.removePeerGoneListener(RJVMImpl.java:352)
at weblogic.jts.internal.CoordinatorImpl.unregisterClientDeathNotification(CoordinatorImpl.java:101)
at weblogic.jts.internal.CoordinatorImpl.commit(CoordinatorImpl.java:347)
at weblogic.jts.internal.TxContext.commit(TxContext.java:255)
at weblogic.ejb.internal.StatelessEJBObject.postInvokeOurTx(StatelessEJBObject.java:103)
at weblogic.ejb.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:849)
at com.xxx.yyy.as.ProfileSessionEJBEOImpl.getContactNumbers(ProfileSessionEJBEOImpl.java:5687)
at com.xxx.yyy.as.ProfileSessionEJBEOImpl_WLSkel.invoke(ProfileSessionEJBEOImpl_WLSkel.java:222)
at weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAdapter.java:347)
at weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandler.java:96)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:15)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread-143" daemon prio=5 tid=0x32b8b0 nid=0x9a waiting on monitor [0xcd7ff000..0xcd7ffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-142" daemon prio=5 tid=0x32adc8 nid=0x99 waiting on monitor [0xcd8ff000..0xcd8ffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-141" daemon prio=5 tid=0x32a2e0 nid=0x98 waiting on monitor [0xcd9ff000..0xcd9ffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-140" daemon prio=5 tid=0x3297f8 nid=0x97 waiting on monitor [0xcdaff000..0xcdaffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-139" daemon prio=5 tid=0x328d10 nid=0x96 waiting for monitor entry [0xcdbff000..0xcdbffc68]
at java.util.Vector.addElement(Vector.java:573)
at weblogic.rjvm.RJVMImpl.addPeerGoneListener(RJVMImpl.java:348)
at weblogic.time.server.ScheduledTrigger.setExecCon(ScheduledTrigger.java:46)
at weblogic.t3.srvr.T3ServerServices.getScheduledTrigger(T3ServerServices.java:177)
at weblogic.jts.internal.CoordinatorImpl.resetTimer(CoordinatorImpl.java:210)
at weblogic.jts.internal.CoordinatorImpl.<init>(CoordinatorImpl.java:83)
at weblogic.jts.internal.CoordinatorFactoryImpl.createCoordinator(CoordinatorFactoryImpl.java:95)
at weblogic.jts.internal.CoordinatorFactoryImpl_ServiceStub.createCoordinator(CoordinatorFactoryImpl_ServiceStub.java:69)
at weblogic.jts.internal.TxContext.getCoordinator(TxContext.java:139)
at weblogic.jts.internal.TxContext.begin(TxContext.java:93)
at weblogic.jts.internal.CurrentImpl.begin(CurrentImpl.java:48)
at weblogic.jts.internal.TransactionManagerImpl.begin(TransactionManagerImpl.java:56)
at weblogic.ejb.internal.EJBHomeImpl.setupTransaction(EJBHomeImpl.java:838)
at weblogic.ejb.internal.BaseEJBObject.setupTransaction(BaseEJBObject.java:281)
at weblogic.ejb.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:471)
at com.xxx.yyy.as.SecuritySessionEJBEOImpl.getClientConfigurationSiteSpecific(SecuritySessionEJBEOImpl.java:143)
at com.xxx.yyy.as.SecuritySessionEJBEOImpl_WLSkel.invoke(SecuritySessionEJBEOImpl_WLSkel.java:254)
at weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAdapter.java:347)
at weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandler.java:96)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:15)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread-138" daemon prio=5 tid=0x328228 nid=0x95 waiting on monitor [0xcdcff000..0xcdcffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-137" daemon prio=5 tid=0x326d38 nid=0x94 waiting on monitor [0xcddff000..0xcddffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-136" daemon prio=5 tid=0x326250 nid=0x93 waiting on monitor [0xcdeff000..0xcdeffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-135" daemon prio=5 tid=0x325768 nid=0x92 waiting on monitor [0xcdfff000..0xcdfffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-134" daemon prio=5 tid=0x324c80 nid=0x91 waiting on monitor [0xce0ff000..0xce0ffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-133" daemon prio=5 tid=0x324198 nid=0x90 waiting on monitor [0xce1ff000..0xce1ffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-132" daemon prio=5 tid=0x3236b0 nid=0x8f waiting on monitor [0xce2ff000..0xce2ffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-131" daemon prio=5 tid=0x322bc8 nid=0x8e waiting on monitor [0xce3ff000..0xce3ffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-130" daemon prio=5 tid=0x3220e0 nid=0x8d waiting on monitor [0xce4ff000..0xce4ffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-129" daemon prio=5 tid=0x3215f8 nid=0x8c waiting on monitor [0xce5ff000..0xce5ffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-128" daemon prio=5 tid=0x320b10 nid=0x8b waiting on monitor [0xce6ff000..0xce6ffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-127" daemon prio=5 tid=0x320028 nid=0x8a waiting on monitor [0xce7ff000..0xce7ffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-126" daemon prio=5 tid=0x31f540 nid=0x89 waiting on monitor [0xce8ff000..0xce8ffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-125" daemon prio=5 tid=0x31ea58 nid=0x88 waiting on monitor [0xce9ff000..0xce9ffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-124" daemon prio=5 tid=0x31df70 nid=0x87 waiting on monitor [0xceaff000..0xceaffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-123" daemon prio=5 tid=0x31d488 nid=0x86 waiting on monitor [0xcebff000..0xcebffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-122" daemon prio=5 tid=0x31bb90 nid=0x85 waiting on monitor [0xcecff000..0xcecffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-121" daemon prio=5 tid=0x31b0a8 nid=0x84 waiting on monitor [0xcedff000..0xcedffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-120" daemon prio=5 tid=0x31a5c0 nid=0x83 waiting for monitor entry [0xceeff000..0xceeffc68]
at java.util.Vector.addElement(Vector.java:573)
at weblogic.rjvm.RJVMImpl.addPeerGoneListener(RJVMImpl.java:348)
at weblogic.jdbc20.rmi.internal.ConnectionImpl.<init>(ConnectionImpl.java:39)
at weblogic.jdbc20.common.internal.RmiDataSource.getConnection(RmiDataSource.java:65)
at weblogic.jdbc20.common.internal.RmiDataSource_ServiceStub.getConnection(RmiDataSource_ServiceStub.java:179)
at com.xxx.yyy.asutil.DataAccessManager.getConnection(DataAccessManager.java:113)
at com.xxx.yyy.as.MetricsSessionEJB.logEvent(MetricsSessionEJB.java:222)
at com.xxx.yyy.as.MetricsSessionEJBEOImpl.logEvent(MetricsSessionEJBEOImpl.java:324)
at com.xxx.yyy.as.MetricsSessionEJBEOImpl_WLSkel.invoke(MetricsSessionEJBEOImpl_WLSkel.java:242)
at weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAdapter.java:347)
at weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandler.java:96)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:15)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread-119" daemon prio=5 tid=0x319ad8 nid=0x82 waiting on monitor [0xcefff000..0xcefffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-118" daemon prio=5 tid=0x318ff0 nid=0x81 runnable [0xcf0fe000..0xcf0ffc68]
at weblogic.db.oci.OciCursor.execAndFetch(Native Method)
at weblogic.db.oci.OciCursor.oci_execAndFetch(OciCursor.java:1890)
at weblogic.jdbcbase.oci.Statement.executeQuery(Statement.java:905)
at weblogic.jdbcbase.jts.Statement.executeQuery(Statement.java:58)
at weblogic.jdbc20.rmi.internal.PreparedStatementImpl.executeQuery(PreparedStatementImpl.java:46)
at weblogic.jdbc20.rmi.SerialPreparedStatement.executeQuery(SerialPreparedStatement.java:40)
at com.xxx.yyy.as.SecuritySessionEJB.getClientConfiguration(SecuritySessionEJB.java:1669)
at com.xxx.yyy.as.SecuritySessionEJBEOImpl.getClientConfiguration(SecuritySessionEJBEOImpl.java:985)
at com.xxx.yyy.as.SecuritySessionEJBEOImpl_WLSkel.invoke(SecuritySessionEJBEOImpl_WLSkel.java:234)
at weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAdapter.java:347)
at weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandler.java:96)
at weblogic.rmi.extensions.BasicRequestDispatcher.dispatch(BasicRequestDispatcher.java:82)
at weblogic.rmi.internal.ServerRequest.sendOneWay(ServerRequest.java:73)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:77)
at com.xxx.yyy.as.SecuritySessionEJBEOImpl_WLStub.getClientConfiguration(SecuritySessionEJBEOImpl_WLStub.java:703)
at com.xxx.yyy.as.QuestionnaireSessionEJB.getQuestionnaireBatches(QuestionnaireSessionEJB.java:3479)
at com.xxx.yyy.as.QuestionnaireSessionEJBEOImpl.getQuestionnaireBatches(QuestionnaireSessionEJBEOImpl.java:631)
at com.xxx.yyy.as.QuestionnaireSessionEJBEOImpl_WLSkel.invoke(QuestionnaireSessionEJBEOImpl_WLSkel.java:237)
at weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAdapter.java:347)
at weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandler.java:96)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:15)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread-117" daemon prio=5 tid=0x317f00 nid=0x80 waiting on monitor [0xcf1ff000..0xcf1ffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-116" daemon prio=5 tid=0x317418 nid=0x7f waiting on monitor [0xcf2ff000..0xcf2ffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-115" daemon prio=5 tid=0x316930 nid=0x7e waiting on monitor [0xcf3ff000..0xcf3ffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-114" daemon prio=5 tid=0x315e48 nid=0x7d waiting on monitor [0xcf4ff000..0xcf4ffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-113" daemon prio=5 tid=0x314b58 nid=0x7c waiting on monitor [0xcf5ff000..0xcf5ffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-112" daemon prio=5 tid=0x314070 nid=0x7b waiting on monitor [0xcf6ff000..0xcf6ffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-111" daemon prio=5 tid=0x313588 nid=0x7a waiting on monitor [0xcf7ff000..0xcf7ffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-110" daemon prio=5 tid=0x312aa0 nid=0x79 waiting on monitor [0xcf8ff000..0xcf8ffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-109" daemon prio=5 tid=0x311fb8 nid=0x78 runnable [0xcf9ff000..0xcf9ffc68]
at java.util.Vector.removeElementAt(Vector.java:509)
at java.util.Vector.removeElement(Vector.java:598)
at weblogic.rjvm.RJVMImpl.removePeerGoneListener(RJVMImpl.java:352)
at weblogic.time.server.ScheduledTrigger.destroy(ScheduledTrigger.java:112)
at weblogic.time.server.ScheduledTrigger.cancel(ScheduledTrigger.java:100)
at weblogic.jts.internal.CoordinatorImpl.cancelCurrentTimer(CoordinatorImpl.java:199)
at weblogic.jts.internal.CoordinatorImpl.commit(CoordinatorImpl.java:404)
at weblogic.jts.internal.TxContext.commit(TxContext.java:255)
at weblogic.ejb.internal.StatelessEJBObject.postInvokeOurTx(StatelessEJBObject.java:103)
at weblogic.ejb.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:849)
at com.xxx.yyy.as.TaskSessionEJBEOImpl.findTaskByFilter(TaskSessionEJBEOImpl.java:784)
at com.xxx.yyy.as.TaskSessionEJBEOImpl_WLSkel.invoke(TaskSessionEJBEOImpl_WLSkel.java:101)
at weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAdapter.java:347)
at weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandler.java:96)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:15)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread-108" daemon prio=5 tid=0x3114d0 nid=0x77 waiting on monitor [0xcfaff000..0xcfaffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-107" daemon prio=5 tid=0x3109e8 nid=0x76 waiting on monitor [0xcfbff000..0xcfbffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-106" daemon prio=5 tid=0x30ff00 nid=0x75 waiting on monitor [0xcfcff000..0xcfcffc68]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-105" daemon prio=5 tid=0x30f418 nid=0x74 waiting for monitor entry [0xcfdff000..0xcfdffc68]
at java.util.Vector.removeElement(Vector.java:595)
at weblogic.rjvm.RJVMImpl.removePeerGoneListener(RJVMImpl.java:352)
at weblogic.jdbc20.rmi.internal.ConnectionImpl.close(ConnectionImpl.java:161)
at weblogic.jdbc20.rmi.SerialConnection.close(SerialConnection.java:162)
at com.xxx.yyy.asutil.Util -
Error in configuring Oracle OCI Driver in WLS
My application uses Oracle OCI driver for making JDBC connection from the server application.I have installed Oracle client in the machine.Added the Oracle Bin directory to System Path.But when i try to create the connection Pool Weblogic throws the error saying DLL file is not found in System.Library.Path.Can you help in solving this problem,Config detailsOS - Windows 2000 ProfessionalWeblogic 5.1 serverOracle 8.1.7 clientDriver used Oracle OCI driver...Expecting a reply
You need to set your path to point to the <wls-install-home>/bin/oci8xx_x/
folder as well. I dont think 5.1 supports 817 type 2 driver, you may have to
use the thin driver from oracle instead.
sree
"Varadharajan" <[email protected]> wrote in message
news:3b8f070f$[email protected]..
My application uses Oracle OCI driver for making JDBC connection from theserver application.I have installed Oracle client in the machine.Added the
Oracle Bin directory to System Path.But when i try to create the connection
Pool Weblogic throws the error saying DLL file is not found in
System.Library.Path.Can you help in solving this problem,Config detailsOS -
Windows 2000 ProfessionalWeblogic 5.1 serverOracle 8.1.7 clientDriver used
Oracle OCI driver...Expecting a reply -
Using OCI driver with Tomcat for JSP?Servlets
We have a need to switch to OCI drivers instead of JDBC thin driver. Our tomcat is running on Sun and Linix platform. Does anyone have real world experience in terms of configuring the OCI driver and connection pooling? Please help to provide some configuration tips.
You should repost this in the JDBC forum here on OTN so that you can get some better expertise in this area.
The URL is http://forums.oracle.com/forums/forum.jsp?forum=99
Hope this helps,
Rob -
Unable to use SQLJ OCI driver in weblogic 5.1
Hi,I am trying to use SQLJ OCI driver instead of JDriver on solaries but always get an error "java.sql.SQLException: Error while trying to retrieve text for error ORA-12545" when connection pool is being created.The same works fine if I use JDriver.Moreover when I try with a standalone application which loads SQLJ OCI Driver it also works fine. Is there anything to be done/added in weblogic properties file or startWeblogic.sh for this to work on solaries? ORACLE_HOME is set properly! if not JDRIVER would have thrown the same error!!On NT it works great!!
To us, a JDBC driver is just a JDBC driver provided that it is JDBC complaint. Make sure that you have the ORACLE_HOME set to point to the base directory where the Oracle client is installed and LD_LIBRARY_PATH includes the $ORACLE_HOME/lib directory. If this still doesn't help, can you post the relevant section of the weblogic.properties file and the complete error message including the stack trace?
Samprathi wrote:
Hi,I am trying to use SQLJ OCI driver instead of JDriver on solaries but always get an error "java.sql.SQLException: Error while trying to retrieve text for error ORA-12545" when connection pool is being created.The same works fine if I use JDriver.Moreover when I try with a standalone application which loads SQLJ OCI Driver it also works fine. Is there anything to be done/added in weblogic properties file or startWeblogic.sh for this to work on solaries? ORACLE_HOME is set properly! if not JDRIVER would have thrown the same error!!On NT it works great!! -
Hi all,
We have a setup accessing an Oracle-database (9.0.1 and 9i) from a
java program using an Oracle thin driver like this:
jdbc:oracle:thin:@host:port:sid
This works fine. Now we wanted to try the OCI-driver for speed
comparision (mainly bypassing socket communication).
jdbc:oracle:oci8:@host:port:sid
This didn't work. We use the classes12.zip for Oracle 9.0.1. downloaded
from OTN. The error is:
java.lang.NoSuchFieldError: OCIEnvHandle
at oracle.jdbc.oci8.OCIDBAccess.make_c_state(Native Method)
at oracle.jdbc.oci8.OCIDBAccess.logon(OCIDBAccess.java:309)
at oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:287)
at oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.java:442)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:321)
at java.sql.DriverManager.getConnection(DriverManager.java:517)
at java.sql.DriverManager.getConnection(DriverManager.java:177)
at oracle.jdbc.pool.OracleDataSource.getConnection(OracleDataSource.java:116)
at oracle.jdbc.pool.OracleConnectionPoolDataSource.getPhysicalConnection(OracleConnectionPoolDataSource.java:98)
at oracle.jdbc.pool.OracleConnectionPoolDataSource.getPooledConnection(OracleConnectionPoolDataSource.java:77)
at de.otto.noa.standard.database.backend.ConnectionOracle.connect(ConnectionOracle.java:64)
The last line given is the first line in our own code.
The SHLIB_PATH points to the lib32 directories. If we set them to the lib directories
the error changes to :
java.lang.UnsatisfiedLinkError: /opt/oracle/app/oracle/product/9i/lib/libocijdbc9.sl: Exec format error
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary0(Unknown Source)
at java.lang.ClassLoader.loadLibrary(Unknown Source)
at java.lang.Runtime.loadLibrary0(Unknown Source)
at java.lang.System.loadLibrary(Unknown Source)
at oracle.jdbc.oci8.OCIDBAccess.logon(OCIDBAccess.java:294)
at oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:287)
at oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.java:442)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:321)
at java.sql.DriverManager.getConnection(DriverManager.java:517)
at java.sql.DriverManager.getConnection(DriverManager.java:177)
at oracle.jdbc.pool.OracleDataSource.getConnection(OracleDataSource.java:116)
at oracle.jdbc.pool.OracleConnectionPoolDataSource.getPhysicalConnection(OracleConnectionPoolDataSource.java:98)
at oracle.jdbc.pool.OracleConnectionPoolDataSource.getPooledConnection(OracleConnectionPoolDataSource.java:77)
at de.otto.noa.standard.database.backend.ConnectionOracle.connect(ConnectionOracle.java:64)
Any suggestions on what to check up on?
Also I'd like to know whether it is correct that the Oracle 9 driver uses oci8?
regards,
Frieder SchenkeHi Elango,
One cannot connect to the database using host:port:sid when using OCI driver. Strange.
It has to be a TNSname or a url .
jdbc:oracle:oci8:@(description=(address=(host=myhost)(protocol=tcp)(port=1521))(connect_data=(sid=orcl)))I tried this (adapted to our database of course) and also (because we have tnsnames.ora setup too):
jdbc:oracle:oci8:@tns_name
With the same effects. ('tnsping tns_name' works)
I think the problem lies somewhere else. The system doesn't even try to actually connect
before it throws that exception. Some driver incompatibility, I guess. But I don't know,
what I did wrong or where to look. Especially that 'Exec format error' is suspicious,
because we'd like to use 64bit if possible.
Also, for when this starts to work, I'd like to know how to make sure there is no socket
connection being used. I vaguely remember something like
jdbc:oracle:oci8:@beqlocal:tns_name
but I don't know the exact syntax. There are several database on that machine, so just
beqlocal wouldn't be enough, unless it also uses the environment-variable
ORACLE_SID
regards,
Frieder Schenke
PS : Peter is my team chef, I'm using his OTN account -
Oracle database Connectivity using OCI driver
I am getting the error only when ever I am using oci driver
oracle.url=jdbc:oracle:oci:@(description=(address=(host=url.name.com)(protocol=tcp)(port=1521))(connect_data=(sid=user)))
04:52:55,093 ERROR [STDERR] java.sql.SQLException: ???S???Y??x??
04:52:55,094 ERROR [STDERR] at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:70)
04:52:55,094 ERROR [STDERR] at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:131)
04:52:55,095 ERROR [STDERR] at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:204)
04:52:55,095 ERROR [STDERR] at oracle.jdbc.driver.T2CConnection.checkError(T2CConnection.java:650)
04:52:55,095 ERROR [STDERR] at oracle.jdbc.driver.T2CConnection.logon(T2CConnection.java:338)
04:52:55,095 ERROR [STDERR] at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:508)
04:52:55,095 ERROR [STDERR] at oracle.jdbc.driver.T2CConnection.<init>(T2CConnection.java:133)
04:52:55,096 ERROR [STDERR] at oracle.jdbc.driver.T2CDriverExtension.getConnection(T2CDriverExtension.java:53)
04:52:55,096 ERROR [STDERR] at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:510)
04:52:55,096 ERROR [STDERR] at java.sql.DriverManager.getConnection(DriverManager.java:582)
04:52:55,096 ERROR [STDERR] at java.sql.DriverManager.getConnection(DriverManager.java:185)
04:52:55,097 ERROR [STDERR] at org.apache.jsp.index_jsp._jspService(index_jsp.java:68)
04:52:55,097 ERROR [STDERR] at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
04:52:55,097 ERROR [STDERR] at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
04:52:55,097 ERROR [STDERR] at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:369)
04:52:55,097 ERROR [STDERR] at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:326)
04:52:55,098 ERROR [STDERR] at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:253)
04:52:55,098 ERROR [STDERR] at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
04:52:55,098 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:324)
04:52:55,098 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242)
04:52:55,099 ERROR [STDERR] at org.jboss.resteasy.plugins.server.servlet.FilterDispatcher.doFilter(FilterDispatcher.java:63)
04:52:55,099 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:274)
04:52:55,099 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242)
04:52:55,099 ERROR [STDERR] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)
04:52:55,099 ERROR [STDERR] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
04:52:55,100 ERROR [STDERR] at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:181)
04:52:55,100 ERROR [STDERR] at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.event(CatalinaContext.java:285)
04:52:55,100 ERROR [STDERR] at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.invoke(CatalinaContext.java:261)
04:52:55,100 ERROR [STDERR] at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:88)
04:52:55,101 ERROR [STDERR] at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:100)
04:52:55,101 ERROR [STDERR] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
04:52:55,101 ERROR [STDERR] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
04:52:55,101 ERROR [STDERR] at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
04:52:55,101 ERROR [STDERR] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
04:52:55,102 ERROR [STDERR] at org.jboss.web.tomcat.service.request.ActiveRequestResponseCacheValve.invoke(ActiveRequestResponseCacheValve.java:53)
04:52:55,102 ERROR [STDERR] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362)
04:52:55,102 ERROR [STDERR] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)
04:52:55,102 ERROR [STDERR] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653)
04:52:55,102 ERROR [STDERR] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951)
04:52:55,103 ERROR [STDERR] at java.lang.Thread.run(Thread.java:619)
04:52:55,105 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[Test].[jsp]] Servlet.service() for servlet jsp threw exception: java.sql.SQLException: ???S???Y??x??
at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:70) [ojdbc5.jar:Oracle JDBC Driver version - "11.1.0.7.0-Production"]
at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:131) [ojdbc5.jar:Oracle JDBC Driver version - "11.1.0.7.0-Production"]
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:204) [ojdbc5.jar:Oracle JDBC Driver version - "11.1.0.7.0-Production"]
at oracle.jdbc.driver.T2CConnection.checkError(T2CConnection.java:650) [ojdbc5.jar:Oracle JDBC Driver version - "11.1.0.7.0-Production"]
at oracle.jdbc.driver.T2CConnection.logon(T2CConnection.java:338) [ojdbc5.jar:Oracle JDBC Driver version - "11.1.0.7.0-Production"]
at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:508) [ojdbc5.jar:Oracle JDBC Driver version - "11.1.0.7.0-Production"]
at oracle.jdbc.driver.T2CConnection.<init>(T2CConnection.java:133) [ojdbc5.jar:Oracle JDBC Driver version - "11.1.0.7.0-Production"]
at oracle.jdbc.driver.T2CDriverExtension.getConnection(T2CDriverExtension.java:53) [ojdbc5.jar:Oracle JDBC Driver version - "11.1.0.7.0-Production"]
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:510) [ojdbc5.jar:Oracle JDBC Driver version - "11.1.0.7.0-Production"]
at java.sql.DriverManager.getConnection(DriverManager.java:582) [:1.6.0_13]
at java.sql.DriverManager.getConnection(DriverManager.java:185) [:1.6.0_13]
at org.apache.jsp.index_jsp._jspService(index_jsp.java:68)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) [:6.0.0.20100911-M5]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [:1.0.0.Beta2]
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:369) [:6.0.0.20100911-M5]
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:326) [:6.0.0.20100911-M5]
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:253) [:6.0.0.20100911-M5]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [:1.0.0.Beta2]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:324) [:6.0.0.20100911-M5]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [:6.0.0.20100911-M5]
at org.jboss.resteasy.plugins.server.servlet.FilterDispatcher.doFilter(FilterDispatcher.java:63) [:6.0.0.20100911-M5]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:274) [:6.0.0.20100911-M5]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [:6.0.0.20100911-M5]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [:6.0.0.20100911-M5]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) [:6.0.0.20100911-M5]
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:181) [:6.0.0.20100911-M5]
at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.event(CatalinaContext.java:285) [:1.1.0.CR3]
at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.invoke(CatalinaContext.java:261) [:1.1.0.CR3]
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:88) [:6.0.0.20100911-M5]
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:100) [:6.0.0.20100911-M5]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) [:6.0.0.20100911-M5]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [:6.0.0.20100911-M5]
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) [:6.0.0.20100911-M5]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [:6.0.0.20100911-M5]
at org.jboss.web.tomcat.service.request.ActiveRequestResponseCacheValve.invoke(ActiveRequestResponseCacheValve.java:53) [:6.0.0.20100911-M5]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [:6.0.0.20100911-M5]
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [:6.0.0.20100911-M5]
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [:6.0.0.20100911-M5]
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951) [:6.0.0.20100911-M5]
at java.lang.Thread.run(Thread.java:619) [:1.6.0_13]
When I am using thin driver, I am successful in connecting to the database
oracle.url=jdbc:oracle:thin:@(description=(address=(host=url.name.com)(protocol=tcp)(port=1521))(connect_data=(sid=user)))
I am using JBOSS 1.6 with oracle 11.1.0 and jdk 1.6
Please help me resolve the problem
Thanks,
KumarYou should confirm that you can connect to the DB with a simple Java class using the url that the code you posted is using.
This will show that the OCI client is installed and executing properly. If you can't connect externally you will need to fix that first.
Is the Oracle client installed on the same machine the JDBC code is running on? -
ORA-01401 error on char column with oracle oci driver
Hello,
We found a potential bug in the kodo.jdbc.sql.OracleDictionary class
shipped as source with Kodo:
In newer Kodo versions (at least in 3.3.4), the method
public void setString (PreparedStatement stmnt, int idx, String
val, Column col)
has the following code block:
// call setFixedCHAR for fixed width character columns to get padding
// semantics
if (col != null && col.getType () == Types.CHAR
&& val != null && val.length () != col.getSize ())
((OraclePreparedStatement) inner).setFixedCHAR (idx, val);
This block seems to be intended for select statements but is called on
inserts/updates also. The latter causes a known problem with the Oracle
oci driver when settings CHAR columns as FixedCHAR, which reports an
ORA-01401 error (inserted value too large for column) when definitely no
column is too long. This does not happen with the thin driver.
We reproduced this with 8.1.7 and 9.2.0 drivers.
For us we solved the problem by subclassing OracleDictionary and removing
the new code block.
Regards,
Rainer Meyer
ELAXY Financial Software & Solutions GmbH & Co. KGRainer-
I read at
re:'ORA-01401 inserted value too large for column' - 9i that:
"This is fixed in Oracle9i Release 2"
Can you try that version of the driver? Also, does it fail in the Oracle
10 OCI driver?
Rainer Meyer wrote:
Hello,
We found a potential bug in the kodo.jdbc.sql.OracleDictionary class
shipped as source with Kodo:
In newer Kodo versions (at least in 3.3.4), the method
public void setString (PreparedStatement stmnt, int idx, String
val, Column col)
has the following code block:
// call setFixedCHAR for fixed width character columns to get padding
// semantics
if (col != null && col.getType () == Types.CHAR
&& val != null && val.length () != col.getSize ())
((OraclePreparedStatement) inner).setFixedCHAR (idx, val);
This block seems to be intended for select statements but is called on
inserts/updates also. The latter causes a known problem with the Oracle
oci driver when settings CHAR columns as FixedCHAR, which reports an
ORA-01401 error (inserted value too large for column) when definitely no
column is too long. This does not happen with the thin driver.
We reproduced this with 8.1.7 and 9.2.0 drivers.
For us we solved the problem by subclassing OracleDictionary and removing
the new code block.
Regards,
Rainer Meyer
ELAXY Financial Software & Solutions GmbH & Co. KG
Marc Prud'hommeaux
SolarMetric Inc. -
Problem JDBC Connection using OCI Driver on Weblogic Portal on Linux
Hi Team,
I want a JDBC connection using OCI Driver in Weblogic Portal 8.1 sp4 on Linux. When I had tested using JDBC connection using Plain Java Code it is working. Also when I create the OCI Connection Weblogic Connection Pool it is working.
But My Requirement is to create the connection using Java Code in Portal Application
But When I create OCI connection in the code it is throwing NO SUITABLE DRIVER Found.
---------- Code in Plain Java Code ------------ Same code is used in Weblogic Portal Application --------------------------------
public static void main(String[] args) throws Exception{
Class.forName("oracle.jdbc.driver.OracleDriver");
DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver());
String url="jdbc:oracle:oci8:@TESTDB";
Properties props = new Properties();
props.put("user","scott");
props.put("password","tiger");
conn=DriverManager.getConnection(url,props);
When I am using the same code in Weblogic Portal and Deployed on Weblogic Portal Server 8.1 SP4 it is throwing following error.
-------------- Exception on Server Log --------------------
java.sql.SQLException: No suitable driver
at java.sql.DriverManager.getConnection(Ljava.lang.String;Ljava.util.Properties;Ljava.lang.ClassLoader;)Ljava.sql.Connection;(Unknown Source)
at java.sql.DriverManager.getConnection(Ljava.lang.String;Ljava.util.Properties;)Ljava.sql.Connection;(Unknown Source)
My Environment is
LINUX
Weblogic 8.1 SP4
Oracle 9i Client on Same Machine
Oracle 10g Server on Different Machine
My Environment Variables on the Linux Server also set properly as following
PATH=/apps/pmaaum/ant/apache-ant-1.6.5/bin:.:/apps/beahomedev/jdk142_05/bin:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/apps/oracle/ora9i/product/9.2.0/bin:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/apps/oracle/ora9i/bin
LD_LIBRARY_PATH=/usr/lib:/apps/oracle/ora9i/product/9.2.0/lib:/apps/oracle/ora9i/product/9.2.0/lib32:/apps/oracle/ora9i/product/9.2.0/rdbms/lib:/usr/openwin/lib:/apps/oracle/ora9i/product/9.2.0/jdbc/lib
JAVA_HOME=/apps/beahomedev/jdk142_05
JDBC_LIB=/apps/oracle/ora9i/product/9.2.0/jdbc/lib
CLASSPATH=:.:/apps/beahomedev/jdk142_05/lib/rt.jar:/apps/oracle/ora9i/product/9.2.0/jdbc/lib/classes12.jar
Please help me, Let me know if you required anything.
Thanks in Advance
Vishnu
Edited by: vishnuk on Oct 23, 2009 4:07 AM
Edited by: vishnuk on Oct 23, 2009 4:10 AMHi Vishnu
Looks like a classloader issue. BEA class loader is very tricky. Any jar added manually in classpath, will end up loading only those classes. Any imports that we have in any of those classes do not get loaded. Anyhow, coming to your point, add classes12.jar inside your portal web project Web-Inf/lib folder and see if that helps. Usually thats where we put all the JARs for 8.1 SPxx applications. If this still breaks, then remove the jar from web-inf/lib folder and add under your portal app App-Inf/lib folder. First try with app-inf/lib folder having this jar. If not then with web-inf/lib. Basically web-inf is specific to that web app only. If you have a different app having this jdbc code, then put under app-inf/lib folder. Make sure that you remove the classes12.jar that you added in classpath either in env variable or in setdomainenv.cmd file.
When weblogic uses native OCI Drivers, it refers to jars at this location: ....\beawlp814\weblogic81\server\ext\jdbc\oracle\10g or 9g. Try using one of these jars and see if that works. Most of the times I used these jars only for oracle specific native drivers.
Word of caution. Try to use Connection Pool and a DataSource created in weblogic console for your jdbc code. This Datasource can still use the Oracle drivers that you want (instead of BEA Weblogic wrapper oci drivers) located in above location. Use JNDI Lookup and get Datasource and then connection. This is more recommended approach with many advantages then using DriverManager approach..
Goud -
Using Oracle OCI Driver 8.1.6 in Compaq Tru64 fastVM
Hi!
I try to using Oracle OCI Driver in Compaq Tru64.
I used fast VM (with -fast option weblogic startup) then the result
during populating Connection Pool, weblogic server down with core dump
I attached core file.
is there anyone in this situation?
[weblogicOCITest.txt]Try using the 8.1.7 Thin Driver (the 8.1.6 Thin driver is buggy).
"jungil, kim" wrote:
Hi!
I try to using Oracle OCI Driver in Compaq Tru64.
I used fast VM (with -fast option weblogic startup) then the result
during populating Connection Pool, weblogic server down with core dump
I attached core file.
is there anyone in this situation?
^A^G^A^E}v^A^C^A^R^_!®.E^?^A@˜B^K!@”K!^W
!°o!ðµ.Ei^A@°R!Ø.E^AX^M^G!@”K!È´.E9i!Iweblogic/common/internal/ResourceAllocato
r_Descriptor.serX^M^G!@”K!.E"i!2/fsweblogic/weblogic/classes/boot/°R!.E[X^M^G!@-
”K!¶.E[^Ai!2/fsweblogic/weblogic/classes/boot/i!f/fsweblogic/weblogic/classes/b
oot/weblogic/common/internal/ResourceAllocator_Descriptor.ser°R!¶.E[i![/fsweblo
gic/weblogic/classes/boot/weblogic/common/internal/ResourceAllocator_Descriptor.
ser^T^O!x$^R!p.E^A^A ¸.Eø¸.E`K^R!¸¸.Eظ.E@X^A!^D@X^A!^D^P^M!ðµ.E^Dp.Ei!^Dread—^
M!ø¸.E0
!ðµ.E^A˜…^H!^A.Eh@¹.E¹.E'^A!^A?@X^A!
H^H!p^H!L !^L !ˆÍ !8 !, !^Pm !` !°í !'^A!/fs
weblogic/weblogic/classes/boot/weblogic/common/internal/ResourceAllocator_Descri
ptor.ser'^A!^Br'^A![/fsweblogic/weblogic/classes/boot/weblogic/common/internal/R
esourceAllocator_Descriptor.ser'^A![/fsweblogic/weblogic/classes/boot/weblogic/c
ommon/internal/ResourceAllocator_Descriptor.ser°R!ø».E[H(^G!^AÀ».Eؤ@л.Eл.Ei!^
A@X^A!^F0f^G!xB^G!`N^G!^P/^G!HZ^G!:^G!i![/fsweblogic/weblogic/classes/boot/weblo
gic/common/internal/ResourceAllocator_Descriptor.ser^C!^A^G^B@0
!H.E^AX^M^G!@”K!p.E[^Ai!1/fsweblogic/weblogic/classes/boot/i!d/fsweblogic/weblog
ic/classes/boot/weblogic/common/internal/ResourceAllocator_Descriptor.ser°R!p.E[
˜…^H!^A¾.Eh@ ¾.E ¾.E'^A!^A?@X^A!
H^H!p^H!L !^L !ˆÍ !8 !, !^Pm !` !°í !'^A!/fs
weblogic/weblogic/classes/boot/weblogic/common/internal/ResourceAllocator_Descri
ptor.ser'^A!^Br'^A![/fsweblogic/weblogic/classes/boot/weblogic/common/internal/R
esourceAllocator_Descriptor.ser°R!p.E; T^M!À.E9^A!]^B^M^C^F^H^N^K^\^A^A^Ll^C
^M^V"^^^V&^OE^A^B^AE^A^C^Z^C'^V\^D^AYY^D^PV^D^D^_V^D^B^R(^D^A'^B
^A^G^A^E}v^A^C^AX^M^G!@”K!^H.EZ^Ai!^]getResource( i!FgetResource( weblogic/commo
n/internal/ResourceAllocator_Descriptor.seri!getResource( weblogic/common/intern
al/ResourceAllocator_Descriptor.ser ) found result null°R!^H.EZX^M^G!@”K!ÈÄ.EX^A
i!-ServerClassFinder.getSource( i!\ServerClassFinder.getSource( weblogic/common/
internal/ResourceAllocator_Descriptor.ser )°R!ÈÄ.EXè³^T!(.EV^Ai!,/fsweblogic/web
logic/license/i!Z/fsweblogic/weblogic/license/weblogic/common/internal/ResourceA
llocator_Descriptor.ser0
!øÆ.E^A°R!^P.EVi!V/fsweblogic/weblogic/license/weblogic/common/internal/Resource
Allocator_Descriptor.ser˜…^H!^AøÇ.Eh@^H.E^H.E'^A!^A?@X^A!
H^H!p^H!L !^L !ˆÍ !8 !, !^Pm !` !°í !'^A!/fs
weblogic/weblogic/license/weblogic/common/internal/ResourceAllocator_Descriptor.
ser'^A!^Br'^A!V/fsweblogic/weblogic/license/weblogic/common/internal/ResourceAll
ocator_Descriptor.ser°R!^P.E6 0
!ØÊ.E^AX^M^G!@”K!^X.EV^Ai!,/fsweblogic/weblogic/classes/i!Z/fsweblogic/weblogic/
classes/weblogic/common/internal/ResourceAllocator_Descriptor.ser°R!^X.EV˜…^H!^A
[email protected]'^A!^A?@X^A!
H^H!p^H!L !^L !ˆÍ !8 !, !^Pm !` !°í !'^A!/fs
weblogic/weblogic/classes/weblogic/common/internal/ResourceAllocator_Descriptor.
ser'^A!^Br'^A!V/fsweblogic/weblogic/classes/weblogic/common/internal/ResourceAll
ocator_Descriptor.ser°R!^X.E6 0
! .E^AX^M^G!@”K!H.E\^Ai!2/fsdev/ver/bc/webapp/serverclasses/i!f/fsdev/ver/bc/web
app/serverclasses/weblogic/common/internal/ResourceAllocator_Descriptor.ser°R!H.
E\˜…^H!^[email protected]'^A!^A?@X^A!
H^H!p^H!L !^L !ˆÍ !8 !, !^Pm !` !°í !'^A!/fs
dev/ver/bc/webapp/serverclasses/weblogic/common/internal/ResourceAllocator_Descr
iptor.ser'^A!^Br'^A!\/fsdev/ver/bc/webapp/serverclasses/weblogic/common/internal
/ResourceAllocator_Descriptor.ser°R!H.E< X^M^G!@”K! .E5^Ai!A[ServerClassFinder]f
ound local classpath source: null°R! .E5i!9weblogic/common/internal/resourceallo
cator_descriptor.ser°R!`.E9i!9weblogic/common/internal/resourceallocator_descrip
tor.serX^M^G!@”K!ØÒ.EZ^Ai!^]getResource( i!FgetResource( weblogic/common/interna
l/ResourceAllocator_Descriptor.seri!getResource( weblogic/common/internal/Resour
ceAllocator_Descriptor.ser ) found source null°R!ØÒ.EZ ^_!H.E0.EX^M^G!@”K!Ô.EI
^Ai!^_Failed to find i!IFailed to find /weblogic/common/internal/ResourceAllocat
or_Descriptor.ser°R!Ô.EI9^A!9\^D^AxY^D^PV^D^D^_V^D^B^R(^D^A'^B
@^B ?6^D^HT8^D^B^Q6^D^Y^G^D^HN^B^D^Mu^B^B^A~^A^B^D:^D^A'
^A^G^A^E}v^A^C^AF*!Áå¼ ^PO.E/^\E!!/^\Eh.E°R!.E*i!*weblogic.common.internal.Resou
rceAllocator¸î!!/^\EøÖ.E°R!^P.E*i!*weblogic.common.internal.ResourceAllocator°R!
ˆ×.E i! weblogic.time.common.ScheduleDef°R!ˆ×.E^T°R!^H.E i! weblogic/time/common
/ScheduleDefp^B!p.Eð×.E9^A!?^V^P^V^Q^F^V, ^V,^W^D$^V+^CE^A^M^NE^A^AP^V+^C^A^E
^A"^B^D ^D^H^B^D^Mu^B^B^A~^A^B^D:^D^A'
^A^G^A^E}v^A^C^AxA^M!pb^[email protected]! weblogic/time/common/ScheduleDef°R!ˆÙ.E i!&weblo
gic/time/common/ScheduleDef.class°R!ðÙ.E&T^M!p.E9^A!N^B^M^C^F^H^N^K^\^A^Zl^E
^M^V,*^V,^W^D$^V+^CE^A^M^NE^A^AP^V+^C^A^E ^A"^B^D ^D^H^B^D^Mu^B^B^A~^A^B^
D:^D^A'
^A^G^A^E}v^A^C^Ap^B!ÐÛ.Ep.E9^A!B^AEl^E ^M^V,*^V,^W^D$^V+^CE^A^M^NE^A^AP^V+^C^A^
E ^A"^B^D ^D^H^B^D^Mu^B^B^A~^A^B^D:^D^A'
!°o!(.Ei^A@°R!`.EX^M^G!@”K!(.E&i!6weblogic/time/common/ScheduleDef.classX^M^G!@-
”K!¸Þ.E"i!2/fsweblogic/weblogic/classes/boot/°R!ðà.EHX^M^G!@”K!.EH^Ai!2/fsweblog
ic/weblogic/classes/boot/i!f/fsweblogic/weblogic/classes/boot/weblogic/time/comm
on/ScheduleDef.class°R!.EHi!H/fsweblogic/weblogic/classes/boot/weblogic/time/com
mon/ScheduleDef.class^T^O!0
!^H.E^AX^M^G!@”K!0.EH^Ai!1/fsweblogic/weblogic/classes/boot/i!d/fsweblogic/weblo
gic/classes/boot/weblogic/time/common/ScheduleDef.class°R!0.EH˜…^H!^AP.Eh@`.E`.E
'^A!^A?@X^A!
H^H!p^H!L !^L !ˆÍ !8 !, !^Pm !` !°í !'^A!/fs
weblogic/weblogic/classes/boot/weblogic/time/common/ScheduleDef.class'^A!^Bs'^A!
H/fsweblogic/weblogic/classes/boot/weblogic/time/common/ScheduleDef.class°R!0.E7
^QT^M!Èä.E9^A!K^B^M^C^F^H^N^K^\^A^Zl^E ^M^V,*^D$^V+^CE^A^M^NE^A^AP^V+^C^A^E
^A"^B^D ^D^H^B^D^Mu^B^B^A~^A^B^D:^D^A'
^A^G^A^E}v^A^C^Ap^B!^X.Ep.E9^A!?^AEl^E ^M^V,*^D$^V+^CE^A^M^NE^A^AP^V+^C^A^E
^A"^B^D ^D^H^B^D^Mu^B^B^A~^A^B^D:^D^A'
^A^G^A^E}v^A^C^AX^M^G!@”K!x.E+^Ai!^XLoading i!2Loading weblogic.time.common.Sche
duleDef...°R!x.E+i! weblogic/time/common/ScheduleDef°R!.E X^M^G!@”K!.E&^Ai!0webl
ogic/time/common/ScheduleDef.class°R!.E&X^M^G!@”K!ˆé.EE^Ai!-ServerClassFinder.ge
tSource( i!\ServerClassFinder.getSource( weblogic/time/common/ScheduleDef.class
)°R!ˆé.EEè³^T!èê.EC^Ai!,/fsweblogic/weblogic/license/i!Z/fsweblogic/weblogic/lic
ense/weblogic/time/common/ScheduleDef.class0
!¸ë.E^A°R!Ðë.ECi!C/fsweblogic/weblogic/license/weblogic/time/common/ScheduleDef.
class˜…^H!^A˜ì.Eh@¨ì.E¨ì.E'^A!^A?@X^A!
H^H!p^H!L !^L !ˆÍ !8 !, !^Pm !` !°í !'^A!/fs
weblogic/weblogic/license/weblogic/time/common/ScheduleDef.class'^A!^Bs'^A!C/fsw
eblogic/weblogic/license/weblogic/time/common/ScheduleDef.class°R!Ðë.E2^Q0
[email protected]^AX^M^G!@”K!.EC^Ai!,/fsweblogic/weblogic/classes/i!Z/fsweblogic/weblogic/cla
sses/weblogic/time/common/ScheduleDef.class°R!.EC˜…^H!^Aˆï.Eh@˜ï.E˜ï.E'^A!^A?@X^
A!
H^H!p^H!L !^L !ˆÍ !8 !, !^Pm !` !°í !'^A!/fs
weblogic/weblogic/classes/weblogic/time/common/ScheduleDef.class'^A!^Bs'^A!C/fsw
eblogic/weblogic/classes/weblogic/time/common/ScheduleDef.class°R!.E2^Q˜í^S!ðí.E
X^M^G!@”K!˜ñ.Et^Ai!A[ServerClassFinder]found local classpath source: i![ServerCl
assFinder]found local classpath source: /fsweblogic/weblogic/classes/weblogic/ti
me/common/ScheduleDef.class°R!˜ñ.EtX^M^G!@”K!0.E2^Ai!"Found local class i!FFound
local class weblogic.time.common.ScheduleDef°R!0.E2˜…^H!^A^P.Eh@ .E .E'^A!^A?@X
^A!
H^H!p^H!L !^L !ˆÍ !8 !, !^Pm !` !°í !'^A!/fs
weblogic/weblogic/classes/weblogic/time/common/ScheduleDef.class'^A!^Bs'^A!C/fsw
eblogic/weblogic/classes/weblogic/time/common/ScheduleDef.class'^A!^AÊþº¾^C-^T^G
^S^G^O^G^M^G^N^A^MConstantValue^A"(Lweblogic/common/T3ServicesDef;)V^A
Exceptions^A^LscheduleInit^A^OLineNumberTable^A
SourceFile^A^NLocalVariables^A^DCode^A weblogic/time/common/ScheduleDef^A weblog
ic/time/common/Schedulable^A^Pjava/lang/Object^A^](Lweblogic/common/ParamSet;)V^
A^PScheduleDef.java^A^KsetServices^A!weblogic/common/ParamSetException^B^A^C^B^A
^D^B^D^A^R^F^D^A^H^P^A^G^D^A^A^A
^B^Q(!^D!øÜ^CA@^^.E^Y/Eèß^G!˜…^H!^AP.Eh@`.E`.E'^A!^A?@X^A!
H^H!p^H!L !^L !ˆÍ !8 !, !^Pm !` !°í !'^A!/fs
weblogic/weblogic/classes/weblogic/time/common/ScheduleDef.class'^A!^Bs'^A!C/fsw
eblogic/weblogic/classes/weblogic/time/common/ScheduleDef.class°R!ˆ×.E^TE^A!X^M^
G!@”K!.Ep^Ai!^WLoaded i!0Loaded weblogic.time.common.ScheduleDef from i!pLoaded
weblogic.time.common.ScheduleDef from /fsweblogic/weblogic/classes/weblogic/time
/common/ScheduleDef.class°R!.Ep°R! ú.E^_i!^_weblogic.time.common.TriggerDef°R! ú
.E^T°R! .E^_i!^_weblogic/time/common/TriggerDefp^B!ˆû.E^H.E9^A!?^V^P^V^Q^F^V, ^V
,^W^D$^V+^CE^A^M^NE^A^AP^V+^C^A^F^D^A"'^D ^D^H^B^D^Mu^B^B^A~^A^B^D:^D^A'
^A^G^A^E}v^A^C^AxA^M!pb^A@ˆú.Ei!^_weblogic/time/common/TriggerDef°R! ü.E^_i!%web
logic/time/common/TriggerDef.class°R!^H.E%T^M!ˆý.E9^A!N^B^M^C^F^H^N^K^\^A^Zl^E
^M^V,*^V,^W^D$^V+^CE^A^M^NE^A^AP^V+^C^A^F^D^A"'^D ^D^H^B^D^Mu^B^B^A~^A^B^
D:^D^A'
^A^G^A^E}v^A^C^Ap^B!èþ.Eˆú.E9^A!B^AEl^E ^M^V,*^V,^W^D$^V+^CE^A^M^NE^A^AP^V+^C^A^
F^D^A"'^D ^D^H^B^D^Mu^B^B^A~^A^B^D:^D^A'
^A^G^A^E}v^A^C^AxA^M!^?^A@ˆú.Ei!^_weblogic/time/common/TriggerDef°R!^P/E^_i!%web
logic/time/common/TriggerDef.class°R!x/E%˜B^K!@”K!^W
!°o!@^B/Ei^A@°R!x/EX^M^G!@”K!@^A/E%i!5weblogic/time/common/TriggerDef.classX^M^G
!@”K!^A/E"i!2/fsweblogic/weblogic/classes/boot/°R!^C/EGX^M^G!@”K!^B/EG^Ai!2/fswe
blogic/weblogic/classes/boot/i!f/fsweblogic/weblogic/classes/boot/weblogic/time/
common/TriggerDef.class°R!^B/EGi!G/fsweblogic/weblogic/classes/boot/weblogic/tim
e/common/TriggerDef.class^T^O!0
!^E/E^AX^M^G!@”K!^P^E/EG^Ai!1/fsweblogic/weblogic/classes/boot/i!d/fsweblogic/we
blogic/classes/boot/weblogic/time/common/TriggerDef.class°R!^P^E/EG˜…^H!^A0^F/Eh
@@^F/E@^F/E'^A!^A?@X^A!
!^E/E^AX^M^G!@”K!^P^E/EG^Ai!1/fsweblogic/weblogic/classes/boot/i!d/fsweblogic/we
blogic/classes/boot/weblogic/time/common/TriggerDef.class°R!^P^E/EG˜…^H!^A0^F/Eh
@@^F/E@^F/E'^A!^A?@X^A!
H^H!p^H!L !^L !ˆÍ !8 !, !^Pm !` !°í !'^A!/fs
weblogic/weblogic/classes/boot/weblogic/time/common/TriggerDef.class'^A!^Bs'^A!G
/fsweblogic/weblogic/classes/boot/weblogic/time/common/TriggerDef.class°R!^P^E/E
7^PT^M!^G/E9^A!K^B^M^C^F^H^N^K^\^A^Zl^E ^M^V,*^D$^V+^CE^A^M^NE^A^AP^V+^C^A^F^D^A
"'^D ^D^H^B^D^Mu^B^B^A~^A^B^D:^D^A'
^A^G^A^E}v^A^C^Ap^B!^H/Eˆú.E9^A!?^AEl^E ^M^V,*^D$^V+^CE^A^M^NE^A^AP^V+^C^A^F^D^A
"'^D ^D^H^B^D^Mu^B^B^A~^A^B^D:^D^A'
^A^G^A^E}v^A^C^AX^M^G!@”K!X
/E*^Ai!^XLoadingi!2Loading weblogic.time.common.TriggerDef...°R!X
/E*i!^_weblogic/time/common/TriggerDef°R!
/E^_X^M^G!@”K!`^K/E%^Ai!/weblogic/time/common/TriggerDef.class°R!`^K/E%X^M^G!@”K
!h^L/ED^Ai!-ServerClassFinder.getSource( i!\ServerClassFinder.getSource( weblogi
c/time/common/TriggerDef.class )°R!h^L/EDè³^T!^M/EB^Ai!,/fsweblogic/weblogic/lic
ense/i!Z/fsweblogic/weblogic/license/weblogic/time/common/TriggerDef.class0
!^N/E^A°R!^N/EBi!B/fsweblogic/weblogic/license/weblogic/time/common/TriggerDef.c
lass˜…^H!^Ap^O/Eh@^O/E^O/E'^A!^A?@X^A!
H^H!p^H!L !^L !ˆÍ !8 !, !^Pm !` !°í !'^A!/fs
weblogic/weblogic/license/weblogic/time/common/TriggerDef.class'^A!^Bs'^A!B/fswe
blogic/weblogic/license/weblogic/time/common/TriggerDef.class°R!^N/E2^P0
!^N/E^A°R!^N/EBi!B/fsweblogic/weblogic/license/weblogic/time/common/TriggerDef.c
lass˜…^H!^Ap^O/Eh@^O/E^O/E'^A!^A?@X^A!
H^H!p^H!L !^L !ˆÍ !8 !, !^Pm !` !°í !'^A!/fs
weblogic/weblogic/license/weblogic/time/common/TriggerDef.class'^A!^Bs'^A!B/fswe
blogic/weblogic/license/weblogic/time/common/TriggerDef.class°R!^N/E2^P0
!^P^R/E^AX^M^G!@”K!P^Q/EB^Ai!,/fsweblogic/weblogic/classes/i!Z/fsweblogic/weblog
ic/classes/weblogic/time/common/TriggerDef.class°R!P^Q/EB˜…^H!^AX^R/Eh@h^R/Eh^R/
E'^A!^A?@X^A!
H^H!p^H!L !^L !ˆÍ !8 !, !^Pm !` !°í !'^A!/fs
weblogic/weblogic/classes/weblogic/time/common/TriggerDef.class'^A!^Bs'^A!B/fswe
blogic/weblogic/classes/weblogic/time/common/TriggerDef.class°R!P^Q/E2^P˜í^S!^P/
EX^M^G!@”K!`^T/Es^Ai!A[ServerClassFinder]found local classpath source: i![Server
ClassFinder]found local classpath source: /fsweblogic/weblogic/classes/weblogic/
time/common/TriggerDef.class°R!`^T/EsX^M^G!@”K!^U/E1^Ai!"Found local class i!FFo
und local class weblogic.time.common.TriggerDef°R!^U/E1˜…^H!^A^V/Eh@^V/E^V/E'^A!
^A?@X^A!
H^H!p^H!L !^L !ˆÍ !8 !, !^Pm !` !°í !'^A!/fs
weblogic/weblogic/classes/weblogic/time/common/TriggerDef.class'^A!^Bs'^A!B/fswe
blogic/weblogic/classes/weblogic/time/common/TriggerDef.class'^A!^AÊþº¾^C-^T^G^S
^G^O^G^F^G^P^A^MConstantValue^A^_weblogic/time/common/TriggerDef^A^KtriggerInit^
A"(Lweblogic/common/T3ServicesDef;)V^A
Exceptions^A^OLineNumberTable^A
ClassFinder]found local classpath source: /fsweblogic/weblogic/classes/weblogic/
time/common/TriggerDef.class°R!`^T/EsX^M^G!@”K!^U/E1^Ai!"Found local class i!FFo
und local class weblogic.time.common.TriggerDef°R!^U/E1˜…^H!^A^V/Eh@^V/E^V/E'^A!
^A?@X^A!
H^H!p^H!L !^L !ˆÍ !8 !, !^Pm !` !°í !'^A!/fs
weblogic/weblogic/classes/weblogic/time/common/TriggerDef.class'^A!^Bs'^A!B/fswe
blogic/weblogic/classes/weblogic/time/common/TriggerDef.class'^A!^AÊþº¾^C-^T^G^S
^G^O^G^F^G^P^A^MConstantValue^A^_weblogic/time/common/TriggerDef^A^KtriggerInit^
A"(Lweblogic/common/T3ServicesDef;)V^A
Exceptions^A^OLineNumberTable^A
SourceFile^A^NLocalVariables^A^DCode^A^OTriggerDef.java^A^Pjava/lang/Object^A we
blogic/time/common/Triggerable^A^](Lweblogic/common/ParamSet;)V^A^KsetServices^A
!weblogic/common/ParamSetException^B^A^C^B^A^D^B^D^A^R^H^D^A^G^Q^A ^D^A^A^A
^K^B^N(!^D!^H^CA@ðö.Eèß^G!˜…^H!^A^H^Z/Eh@^X^Z/E^X^Z/E'^A!^A?@X^A!
H^H!p^H!L !^L !ˆÍ !8 !, !^Pm !` !°í !'^A!/fs
weblogic/weblogic/classes/weblogic/time/common/TriggerDef.class'^A!^Bs'^A!B/fswe
blogic/weblogic/classes/weblogic/time/common/TriggerDef.class°R! ú.E^TE^A!X^M^G!
@”K!0^\/En^Ai!^WLoaded i!0Loaded weblogic.time.common.TriggerDef from i!nLoaded
weblogic.time.common.TriggerDef from /fsweblogic/weblogic/classes/weblogic/time/
common/TriggerDef.class°R!0^\/En(B!CDh(/^\EhüëD/^\E^D^H˜âDX^M^G!@”K!^]/E
^Ai!^A+°R!^]/E^Ai!^Q+HncbPool°R!^]/E ^P#!^P^YE^]/E/^\E8R^E!;ˆØ^]/E^]/EX^M^G!@
”K!^^/E,^Ai!^XHncbPool created with 1i!^L01°R!^^/E^Ai!^A1i!2HncbPool created wit
h 1 initial connections.°R!^^/E,^H4^E!@”K! /EK@?^^E!eøÑ6!^_/E /E^H4^E!@”K!!/EK@?
^^E!eøÑ6!!/E!/E -
Weblogic 6.1 sp5 core dump by OCI driver
I have encountered a core dump problem on weblogic server 6.1 SP5 the error message
as below, I am using weblogic oci driver for oracle "libweblogicoci37.so" , anyone
can help?
An unexpected exception has been detected in native code outside the VM.
Unexpected Signal : 4 occurred at PC=0x242795c
Function name=(N/A)
Library=(N/A)
NOTE: We are unable to locate the function name symbol for the error
just occurred. Please refer to release documentation for possible
reason and solutions.Galen Boyer wrote:
On Sun, 28 Mar 2004, [email protected] wrote:
Galen Boyer wrote:
On Sat, 27 Mar 2004, [email protected] wrote:
One way to get a substantial boost in reliability is to switch
to the latest appropriate Oracle thin driver.But then you can suffer performance losses.Actually, the latest oracle thin drivers are very fast. The 10g
driver in particular. Well, we are on 9i here and we have lots of CLOB and BLOB
operations. Understood. The latest should work. (How comfortable does that make you ;) )
It is a sad choice we used to have to make between
faster-but-buggy homicidal old OCI code (wherein a bug in one
module can cause a segfault in an innocent unrelated module's
execution, and bring down a whole JVM) and the reliability of
Java. Fortunately, the future is at hand. The future is at hand? I do believe you are starting to sound a
bit like an evangelist. :-)Yep. Back in '96 when we wrote and marketed all the first JDBC drivers
for MS SQLServer, Oracle, Informix and Sybase, we did it solely
so enable our application server to be able to do real work. We were all
absolutely sure the driver market would dry up in 6 months as all the
DBMS vendors made excellent free type-4 drivers. We were over-optimistic.
Sybase's driver still requires you to install non-standard tables and
procedures in the DBMS. Oracle drivers are sloutching toward sufficiency,
but their first GA driver had a hard-wired value of READ_UNCOMMITTED
for getTransactionIsolation, and if you tried setTransactionIsolation
of either READ_COMMITTED or SERIALIZABLE, the driver would throw an
exception! We actually had a weblogic workaround to intercept this
jdbc call and send the "ALTER SESSION " to do what the customer wanted!
At the same time we had a major struggle to get Oracle to admit that
in spite of their documentation, OCI was not threadsafe (killing our
OCI-based driver in weblogic applications) until 7.1.4 on solaris
and NT, and 8.0.5 on other platforms. Did you know they had separate
codelines for OCI on each platform? For a while each platform's OCI
had a different hard-wired limit of the number of simultaneous connections
on client could have? For a while that limited what our application server
could do. OCI was written for simple teller-like client applications.
The new thin drivers take on more of the possible client-side
processing, and can do RAC failover etc. JoeOh well. I for one am a bit skeptical that Oracle is going to
fix java driver bugs before OCI bugs and I don't have any reason
to commit to any "platform independent" solution like java's thin
driver. We are completely based on Oracle here and we have a
J2EE solution for the app just cause we had to choose something.
If thin is better, than we will go with that.The last highest-level talks I had with Oracle folks they indicated that
they wanted everyone to go thin. OCI was a headache for them. Their
OCI code was undocumented and all the original experts had left the company.
That was in 2000 or so, so it is likely better now. They may well have
invested a lot of reverse-documentation by now.
One of the benefits of Java is the reliability. I think you'll
ultimately be happier with the thin. We do want you successful.
Joe -
Oracle JDBC thick (OCI) driver
Hi!
Can someone point me where I can download oracle JDBC thick (OCI) driver. Thick JDBC is not installed by default in 10g. In the OTN download site I can find JDBC thin drivers to download.
Thanks
Rad.Rad,
Allow me to elaborate on Mark's answer. Let's say you download the "ojdbc14.jar" file from the OTN Web site. Both the "thick" and "thin" drivers are in that one file. You indicate which driver you wish to use in your java code -- via the database connection URL, for example:
jdbc:oracle:thin:@//myhost:1521/orclThe above indicates you wish to use the "thin" driver, whereas
jdbc:oracle:oci:@myhost:1521:orclindicates you wish to use the "thick" driver.
[Notice the difference?]
You can find more details from the JDBC FAQ.
Good Luck,
Avi. -
BUG: retrieving NCHAR value using ViewObject returns "???" with OCI driver
Hi,
after upgrading JDeveloper to 10.1.3.1 we cannot use OCI JDBC drivers, because they don't work correctly - characters, that do not exist in database character set (EE8ISO8859P2 in our case) are converted to "?". Thin driver works well. We need to use OCI, because we had some issues with RAC with thin driver.
Test case is easy: create table with NCHAR column, populate with unicode data, create ViewObject to select from this table and it will work only with THIN and not with OCI driver. This worked well with 10.1.3.0. When I tried to directly connect to DB and select that table using java.sql.Statement, it worked with both drivers, that's why I suspect the mechanics inside ADF BC.
I logged a SR for this in Metalink, but try this way as well, for someone else could hit the same problem.
Thanks for any help,
ViliamHi,
after upgrading JDeveloper to 10.1.3.1 we cannot use OCI JDBC drivers, because they don't work correctly - characters, that do not exist in database character set (EE8ISO8859P2 in our case) are converted to "?". Thin driver works well. We need to use OCI, because we had some issues with RAC with thin driver.
Test case is easy: create table with NCHAR column, populate with unicode data, create ViewObject to select from this table and it will work only with THIN and not with OCI driver. This worked well with 10.1.3.0. When I tried to directly connect to DB and select that table using java.sql.Statement, it worked with both drivers, that's why I suspect the mechanics inside ADF BC.
I logged a SR for this in Metalink, but try this way as well, for someone else could hit the same problem.
Thanks for any help,
Viliam -
Can I use OCI driver to test database connection in JDeveloper9.0.3
When using JDeveloper 3.2.3, I can use oci8 driver to test the databse connection.
Then I want oci8 driver work in JDeveloper9.0.2 or JDeveloper 9.0.3. However, it cannot work.
(Note: but thin driver works fine)
First, I read the help file and setup ORACLE_HOME environment variable and install
OCI client driver ocijdbc9.dll on my compuetr. Then some exception is happening when I test again.
So I want to know, does anyone succeed in testing the connection via oci driver
and how to fix this problem.
Thanks a lot.Hi !
You MUST use jdbc library supplied with Oracle client ( so classes12.zip from $ORACLE_HOME/jdbc/lib ), not with JDeveloper - this one might be incopatible with oci native libraries.
I hope , this helps.
Michal -
Hi,
We noticed that when we use the OCI driver for Oracle 8.1.7, we cannot have
an initial connection pool size greater than 249. On the 250th one, there is
a DBMS exception (ORA-24327) and weblogic says that it cannot create the
connection.
If we move to the Thin driver, there is no longer this restriction and we've
tried it with success with more than 550 connections.
Anyone know any limitation about the OCI driver and if there is any
parameter on the OCI driver side or on the DB side to tune so that we can
have more than 249 connections in our pool ?
FI, we have the following configuration (in config.xml) :
<JDBCConnectionPool CapacityIncrement="5"
Name="imJDBCConnectionPool" Targets="imadmin"
DriverName="weblogic.jdbc.oci.Driver" URL="jdbc:weblogic:oracle"
InitialCapacity="270" MaxCapacity="270"
TestTableName="dual" RefreshMinutes="40"
ShrinkingEnabled="false" ShrinkPeriodMinutes="15"
Properties="user=im;password=im;server=im09"/>
and we have the following TNSNAMES.ORA :
IM09.IM =
(DESCRIPTION =
(failover = on)
(ADDRESS = (PROTOCOL = TCP)(HOST = sf1-domaina-1)(PORT = 1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = sf1-domainb-1)(PORT = 1521))
(CONNECT_DATA = (SERVICE_NAME = IM09.im)(SERVER = shared))
and SQLNET.ORA (to resolve the IM domain name) :
NAMES.DEFAULT_DOMAIN=IM
Thanks
-VincentVincent Massol wrote:
>
"Slava Imeshev" <[email protected]> wrote in message
news:[email protected]...
Hi Vincent,
Just for curiosity sake, what are you doing with 250 connections?
It's not in the Cactus area, is it? :-)
grin ;-)
No, I'm currently working for a customer, doing some lab performance tests.
We wanted to use the OCI driver for the TAF feature of OPS (transparent
application failover) but found that the Thin driver is performing so much
better that we have switched to using it along with the multipool feature of
WebLogic. Hi. Beware of 'TAF'. Note that all cursors will be defunct on failover,
so any JDBC statement or ResultSet in progress at the time of failover will
be lost. (IE: not at all transparent).
Joe
We haven't done any failover test yet so we don't know yet how the
multipool (with a 'load-balancing' strategy) perform upon failover of one
instance. If it's ok we'll keep using the thin driver. If not, we'll switch
back to OCI drivers and try the TAF feature.
Also, I don't think we really need that big number of connections. It seems
we had some other performance issue which the DB which was making us use
lots of connections on the WL side. With the thin driver we're only using
about 39-100 connections maximum with a thread count of 40 (that's because a
given message does up to 3 SQL statements per transaction (and a connection
is only effectively released in the pool after the commit)).
I've introduced Cactus on the project, of course, but only for the unit
tests (I'm also using Mock Objects) ... :-)
Regards,
-Vincent
Regards,
Slava Imeshev
"Vincent Massol" <[email protected]> wrote in message
news:[email protected]...
Hi,
We noticed that when we use the OCI driver for Oracle 8.1.7, we cannothave
an initial connection pool size greater than 249. On the 250th one,
there
is
a DBMS exception (ORA-24327) and weblogic says that it cannot create the
connection.
If we move to the Thin driver, there is no longer this restriction andwe've
tried it with success with more than 550 connections.
Anyone know any limitation about the OCI driver and if there is any
parameter on the OCI driver side or on the DB side to tune so that we
can
have more than 249 connections in our pool ?
FI, we have the following configuration (in config.xml) :
<JDBCConnectionPool CapacityIncrement="5"
Name="imJDBCConnectionPool" Targets="imadmin"
DriverName="weblogic.jdbc.oci.Driver" URL="jdbc:weblogic:oracle"
InitialCapacity="270" MaxCapacity="270"
TestTableName="dual" RefreshMinutes="40"
ShrinkingEnabled="false" ShrinkPeriodMinutes="15"
Properties="user=im;password=im;server=im09"/>
and we have the following TNSNAMES.ORA :
IM09.IM =
(DESCRIPTION =
(failover = on)
(ADDRESS = (PROTOCOL = TCP)(HOST = sf1-domaina-1)(PORT = 1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = sf1-domainb-1)(PORT = 1521))
(CONNECT_DATA = (SERVICE_NAME = IM09.im)(SERVER = shared))
and SQLNET.ORA (to resolve the IM domain name) :
NAMES.DEFAULT_DOMAIN=IM
Thanks
-Vincent
B.E.A. is now hiring! (12/14/01) If interested send a resume to [email protected]
DIRECTOR OF PRODUCT PLANS AND STRATEGY San Francisco, CA
E-SALES BUSINESS DEVELOPMENT REPRESENTATIVE Dallas, TX
SOFTWARE ENGINEER (DBA) Liberty Corner, NJ
SENIOR WEB DEVELOPER San Jose, CA
SOFTWARE ENGINEER (ALL LEVELS), CARY, NORTH CAROLINA San Jose, CA
SR. PRODUCT MANAGER Bellevue, WA
SR. WEB DESIGNER San Jose, CA
Channel Marketing Manager - EMEA Region London, GBR
DIRECTOR OF MARKETING STRATEGY, APPLICATION SERVERS San Jose, CA
SENIOR SOFTWARE ENGINEER (PLATFORM) San Jose, CA
E-COMMERCE INTEGRATION ARCHITECT San Jose, CA
QUALITY ASSURANCE ENGINEER Redmond, WA
Services Development Manager (Business Development Manager - Services) Paris, FRA; Munich, DEU
SENIOR SOFTWARE ENGINEER (PLATFORM) Redmond, WA
E-Marketing Programs Specialist EMEA London, GBR
BUSINESS DEVELOPMENT DIRECTOR - E COMMERCE INTEGRATION San Jose, CA
MANAGER, E-SALES Plano, TX
Maybe you are looking for
-
Project system Budget Needs to be Doubled
Hi All, I am facing a issue in project system where we have to double our budget, if we need to run a settlement in the system. For a example, if we have a budget of 100,000 and that is allocated to TWO sub WBS Elements as 50,000 each and when we wan
-
hi i have a problem im using RMI comunication and one of the clases used on the server woks with rs 232 protocol, but when i compile the client class, i get this message in the console RemoteException java.rmi.ServerError: Error ocurred in server thr
-
CS4- CS5: changed behavior in file handling with points (".")
... oh, no, it's horrible -- new version, new problems I have such file names: 1_xxx_26.08.10.jpg, 2_xxx_26.08.10.jpg, ... I am creating an action which saves this file in a specific directory (after several editing steps) by using e.g. the first fil
-
How long for Raid 5 to rebuild?
I have a 2ghz g5 xserve with PCI-raid card installed. My raid 5 consists of 3 250ghz drives. The system is not being used at this time because I have a backup server running. My question is how long can I expect this process to take? Its been runnnin
-
Cannot View Output Report in SysAdmin
Hello I cannot view the output of reports generated by other users in SysAdmin Responsibility. Is it an intended functionalilty? Emgee