APAR status |
Closed as program error.
| Error description
Performance problems when invoking EJBs in WAS 3.5.2
DNS problem still suspected, but not only that.
JNDI caching seems of no efect for EJB
Initial context on server side seems excesive
Same piece of code takes half the time in WebLogic from BEA
defect 91149 Local fix
No local fix provided yet. Problem summary
pick up changes in code from Hursley in the WebSphere Util
code. The changes needed are along the lines of:
At the beginning of readAny add:code. The changes needed are along the lines of:
if (in instanceof CDRInputStream) {
return ((CDRInputStream)in).readAnyOpt();
}
At the beginning of writeAny add:At the beginning of readAny add:if (in instanceof CDRInputStream) {return ((CDRInputStream)in).readAnyOpt();}
if (out instanceof CDROutputStream){
((CDROutputStream)out).writeAnyOpt(obj);
}else{ At the beginning of writeAny add:if (out instanceof CDROutputStream){((CDROutputStream)out).writeAnyOpt(obj);}else{ Problem conclusion
to improve performance. Temporary fixComments
APAR information | APAR number | PQ46578 | Reported component name | WAS STANDARD AI | Reported component ID | 5648C8300 | Reported release | 350 | Status | CLOSED PER | PE | NoPE | HIPER | NoHIPER | Submitted date | 2001-02-28 | Closed date | 2001-03-16 | Last modified date | 2001-03-28 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:APAR is sysrouted FROM one or more of the following:
Modules/Macros APAR is sysrouted TO one or more of the following:Modules/Macros
|
Fix information |
Fixed component name | WAS STANDARD AI | Fixed component ID | 5648C8300 |
Applicable component levels | R350 PSY | UP |
|