Hi Jochen,
let's see whether investigating classloading in general takes you
anywhere. If that is not the case, we mitgh have to look at this again
in one oway or the other.
Though - as you have noted yourself - the fact that this cannot be
reproduced anywhere but on Weblogic 8.1 will make any progress quite ..
well, expensive, as normally we (committers) do not have access to
application servers such as Weblogic.
But let's first see how your investigation into classloading takes off ...
Werner
[EMAIL PROTECTED] wrote:
Hi Jochen,
another user reported similar performance issues within JBoss in another thread
of this mailing list this week. He could track down the issue to a class
loading problem of the server. Please try to find the thread and ask him how he
was able to resolve it.
Regards
Ralf
Hi Werner,
thanks for the information, I though it is Xerces and not Castor that
causes the slowdown, but as I understand you it is more likely that
this is a problem within Castor.
Having said that, it looks like there's an issue with some code
introduced between 0.9.7 and 1.1, and I'd like to learn it. Have you got
some code that I can use to replay your problem, and test things against
SVN trunk ?
The problem is a bit more difficult, because we can't reproduce this
problem in a different environment. If we run a marshalling test
program outside of the Bea Weblogic 8.1 Server on the same machine,
Castor performs well. If we execute it inside the Bea Server it is
slow. But we see this problem only on the test server (Itanium). If we
run the program on a developer machine (x86 old CPU), it is fast as
well.
So currently what we know, is that after we switched our application
to a new version and only changed to a new castor version, we see this
slowdown. But only inside of the Bea 8.1 on the Itanium Server.
We checked all the environment (jars, libs, parameter) over and over
again, but with no luck.
Do you have any idea's how we can better narrow down this problem?
Should we try to use the SVN trunk version of castor?
Or are there some debug properties, that we can enable to better
understand what's going wrong there?
Thanks a lot!
An Kind Regards,
Jochen
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
