WLS Performance .. Socket Exception...

Question

Hi
Recently we encounter the problem when we press the "Refresh" button(Browser MS IE) so quickly then WLS shows the error message as below: (The scenario is calling an entity bean from JSP.)
GMT+08:00 2000:<E> <HTTP>
Connection failure
java.net.SocketException: ReadFile on fd=916 failed with err=64
at weblogic.socket.NTSocketMuxer.initiateIO(Native Method)
     at
weblogic.socket.NTSocketMuxer.read(NTSocketMuxer.java,
Compiled Code)
     at
weblogic.socket.MuxableSocketHTTP.requeue(MuxableSocketHTTP.java,
Compiled Code)
     at
weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java,
Compiled Code)
     at
weblogic.kernel.ExecuteThread.run(ExecuteThread.java,
Compiled Code)
Basicly it's not hurt for our application, but we
usually need to convert the encoding of the string
selected from Database in the EJB(it mean I need to
convert the String because we need chinese). But if we
press the "Refresh" button so quickly, the chinese is
incorrect and appeared as "???????". And if we press
the button later and slowly then the chinese is
correct.
Can someone give me some clue about that ? Or is it related with the "Performance Pack" of WLS...?
BEST & THANKS
andrew :)
PS :
I use Window 2000, WLS 5.1 SP6 and both JDK 1.3 and JDK 1.2.2.
[weblogic.log]

Answer 1

Hi Srikant
Thanks, below the get method of my Entity Bean
public String getEname() {
// SBgen: Get variable
String empName = null;
try{
// 'ename' is the filed of the 'emp' table..., it's stored
// as chinese in Oracle...
empName = new String(new String(ename).getBytes("iso-8859-
1"));
catch (Exception e){
     e.printStackTrace(); }          
return empName;
----------------------------------------------------------------- I use the getByte('iso-8859-1') to convert the string select from database (Oracle 8.1.6, the string in the DB is stored as Chinese) because I need Chinese in web page. The tricky thing is that if I press the 'Refresh' button so quickly then the chinese is displayed as '???' in my web page. If I press the 'Refresh' button slowly then the Chinese is correct in web page(JSP).
mmmmm...., I do really have no idea about that... Can someone give me some clue about that ? Thanks a lots...
BEST
andrew:O
Srikant Subramaniam <[email protected]> wrote:
This is a benign error msg ... the client closed the socket without telling the server! We've since turned off this error msg in subsequent service packs.
Srikant, [email protected], http://weblogic.bea.com/, etc.
AndrewWang wrote:
Hi
Recently we encounter the problem when we press the "Refresh" button(Browser MS IE) so quickly then WLS shows the error message as below: (The scenario is calling an entity bean from JSP.)
GMT+08:00 2000:<E> <HTTP>
Connection failure
java.net.SocketException: ReadFile on fd=916 failed with err=64
at weblogic.socket.NTSocketMuxer.initiateIO(Native Method)
at
weblogic.socket.NTSocketMuxer.read(NTSocketMuxer.java,
Compiled Code)
at
weblogic.socket.MuxableSocketHTTP.requeue(MuxableSocketHTTP.java,
Compiled Code)
at
weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java,
Compiled Code)
at
weblogic.kernel.ExecuteThread.run(ExecuteThread.java,
Compiled Code)
Basicly it's not hurt for our application, but we
usually need to convert the encoding of the string
selected from Database in the EJB(it mean I need to
convert the String because we need chinese). But if we
press the "Refresh" button so quickly, the chinese is
incorrect and appeared as "???????". And if we press
the button later and slowly then the chinese is
correct.
Can someone give me some clue about that ? Or is it related with the "Performance Pack" of WLS...?
BEST & THANKS
andrew :)
PS :
I use Window 2000, WLS 5.1 SP6 and both JDK 1.3 and JDK 1.2.2.
Name: weblogic.log
weblogic.log Type: Text Document (application/x-unknown-content-type-txtfile)
Encoding: base64