Re: WebSphere errors.

["Art Smet" <smet@xxxxxxxxxx>]

Wondering two things:
1. When you see the Database reading exception (Read by primary key),
besides this message - are you experiencing/noticing a functional failure
in your application?
2. If you inspect trace file for your admin server:
/QIBM/UserData/WebASAdv/default/logs/tracefile - do you see an exception
that corresponds to the Database reading exception that shows up at your
console?



"Mangavalli, Ramanujam" <RamM@Mvmills.com>@midrange.com on 09/21/2001
07:35:56 AM

Please respond to java400-l@midrange.com

Sent by:  java400-l-admin@midrange.com


To:   "'java400-l@midrange.com'" <java400-l@midrange.com>
cc:
Subject:  WebSphere errors.



Folks,

we have recently upgraded our system to V5R1. Latest Websphere FixPacks
have
also been applied. The Admin console has also been upgraded to V3.5.4 and
the PQ49277 has also been applied.

When I bring up the console and try to create a web application, I am
getting SMTL0010W - Database reading exception (Read by primary key) on the
Default WAS instance.

I created a new WAS instance and a new HTTP Server(Original) and changed
the
port numbers on the Default_host on the console to reflect the port number
of the HTTP server. ON this instance, I am getting the Database read
exception (REad by primary key) when trying to start the default
application
server.

ANy suggestions?

_______________________________________________
This is the Java Programming on and around the iSeries / AS400 (JAVA400-L)
mailing list
To post a message email: JAVA400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/java400-l
or email: JAVA400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/java400-l.