Ian,
If you are a member of Oracle's technet, you can find the the meaning of
the error (ORA-00600) here:
http://technet.oracle.com/doc/server.815/a67785/e0.htm#1002520
I have attached the text in case you are not a member.
This appears to be an Oracle internal error, so you should contact
Oracle regarding this.
Regarding Tru64 - Orion will run on any platform with a JVM (a great
example of Java's portability).
Cheers,
Scott
--
Scott Farquhar :: [EMAIL PROTECTED]
Atlassian :: http://www.atlassian.com
Supporting YOUR J2EE World
The elephantwalker wrote:
> Ian,
>
> Make sure that you are closing your connections properly. eg:
>
> try {
>
> // open connection
>
> } catch () {
>
> // do something
>
> } finally {
>
> try {
>
> // close connections
>
> } catch () {
>
> // do something
>
> }
>
> }
>
> This could be your problem. The try/catch/finally block MUST be used with
> Oracle...or you will run out of process resources as exceptions occur.
>
> You can check if the connections are being closed properly with a debug
> property:
>
> java -Djdbc.connection.debug=true -jar orion.jar
>
> This will remote where you are not closing your connections.
>
> Regards,
>
> the elephantwalker
> www.elephantwalker.com
>
>
>
>
>
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Ian S. Hagen
> Sent: Wednesday, January 02, 2002 5:53 AM
> To: Orion-Interest
> Subject: JDBC error
>
>
>
> Has anyone experienced instability when using Orion together with Oracle
> 9i? I am currently running an Orion 1.5.2 server on a Tru64 platform
> against a 9i database using the OCI driver. Everything works fine
> initially, but after a few hours of sending HTTP requests to Orion I
> find that performance degrades. Eventually, I start getting database
> errors. I have seen Oracle go into a state where it returns an SQL
> exception:
>
> java.sql.SQLException: ORA-00600: internal error code, arguments:
> [kksfbc-new-child-thresh-exceeded], [], [], [], [], [], [], []
>
>
> I have also experienced the OCI driver core dumping when executing the
> same test:
>
> OCI-21503: program terminated by fatal error
> OCI-04030: out of process memory when trying to allocate 30056 bytes
> (Alloc environm,eoj_stmt_malloc)
>
>
> Obviously, I am running out of resources. The thing I don't understand
> is where! I have run Orion setting the JDBC debug parameters
> jdbc.connection.debug, datasource.verbose and jdbc.debug to true, and it
> seems as though the connections are being created and returned correctly
> (no connections leaked).
>
> Has this problem got anything to do with me running it on Tru64? The
> Orion FAQ doesn't mention Tru64 as a supported OS.
> My datasources.xml looks like this:
> <?xml version="1.0"?>
> <!DOCTYPE data-sources PUBLIC "Orion data-sources"
> "http://xmlns.oracle.com/ias/dtds/data-sources.dtd";>
> <data-sources>
> <!-- Setting up the data source for the ben provider -->
> <data-source
> class="com.evermind.sql.DriverManagerDataSource"
> name="zellsoft"
> location="jdbc/zellsoft"
> xa-location="jdbc/xa/zellsoft"
> ejb-location="jdbc/ejb/zellsoft"
> connection-driver="oracle.jdbc.driver.OracleDriver"
> url="jdbc:oracle:oci8:@vasp"
> username="ben"
> password="ben"
> max-connections="200"
> min-connections="25"
> max-connect-attempts="10"
> connection-retry-interval="1"
> inactivity-timeout="30"
> wait-timeout="75"
> />
> </data-sources>
>
>
> Any suggestions are appreciated!
>
> Ian
>
>
>
>
>
ORA-00600 internal error code, arguments: [string], [string], [string], [string],
[string], [string], [string], [string]
Cause: This is the generic internal error number for Oracle program exceptions. It
indicates that a process has encountered a low-level, unexpected condition. Causes of
this message include:
* timeouts
* file corruption
* failed data checks in memory
* hardware, memory, or I/O errors
* incorrectly restored files
The first argument is the internal message number. Other arguments are various
numbers, names, and character strings. The numbers may change meanings between
different versions of Oracle.
Action: Report this error to Oracle Customer Support after gathering the following
information:
* events that led up to the error
* the operations that were attempted that led to the error
* the conditions of the operating system and databases at the time of the error
* any unusual circumstances that occurred before receiving the ORA-00600
message
* contents of any trace files generated by the error
* the relevant portions of the Alter files
Note: The cause of this message may manifest itself as different errors at
different times. Be aware of the history of errors that occurred before this internal
error.
