Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

FWK005 parse may not be called while parsing

FWK005 parse may not be called while parsing

by  NuniPR  Posted    (Edited  )
Following up on thread830-1340092, my vendor has provided the following information regarding this error:

The problem is caused by a BEA defect in 8.1 SP5 and resolved in 8.1 SP6. See CR250915 and CR273129 in the 8.1.SP6 release notes (http://edocs.beasys.com/wls/docs81/notes/resolved_sp06.html).


CR250915, CR273129
Sometimes, under heavy load, messages related to BEA-101326 or BEA-101083 were logged in WebLogic Server logs when valid sockets were closed prematurely due to corruption in data structures. However, these exceptions had no impact when the client was a web browser because only idle TCP connections and not active connections were prematurely closed when this problem occurred.

A socket is now closed only after the socket times out.




Register to add this FAQ to your archive
Register to rate this FAQ  : BAD 1 2 3 4 5 6 7 8 9 10 GOOD
Please Note: 1 is Bad, 10 is Good :-)

Part and Inventory Search

Back
Top