Menu ▾ ▴

#76 Oracle processes not released properly

open
Misc (42)
5
2005-01-05
2005-01-03
Anonymous
No

I have a tomcat working properly in console mode.
When I used the wrapper, the application in the tomcat
connecting to an oracle always gets an oracle error -
maximum processes exceeded. When I monitored the
oracle processes, the processes that are inactive
doesn't time out as compared to running tomcat in
console mode.

Any guess to what is happening?

thanks in advance!

romano
chauromano@yahoo.com

Discussion

  • Leif Mortenson

    Leif Mortenson - 2005-01-05
    • assigned_to: nobody --> mortenson
     
  • Leif Mortenson

    Leif Mortenson - 2005-01-05

    Logged In: YES
    user_id=228081

    Romano,
    What platform are you running on?

    What JDBC driver are you using? I always use the thin driver.

    How are able to tell that processes are not being closed?
    Are you seeing an increase in threads?

    You say it works in console mode. I assume you mean as a
    standalone java application. Are you seeing the problems
    when running under the Wrapper in a console as well as as a
    service.

    Normally, the JVM should be working the same under the
    Wrapper as when run standalone. Oracle has a native JDBC
    api, it is possible that you are using that when running
    standalone. If the native library is not being located
    correctly under the wrapper then it may be falling back to
    using the thin driver. The thin driver works for me, but
    that might explain the difference in behavior. Just a
    guess. If so, look at this:
    http://wrapper.tanukisoftware.org/doc/english/prop-java-library-path-append-system-path.html

    May have more ideas after I hear back from you.
    Cheers,
    Leif

     

Log in to post a comment.