The following is the bug for this issue:
https://issues.apache.org/jira/browse/GERONIMO-4623
cheers
- mdasari
Jarek Gawor-2 wrote:
I think the main problem here is that we keep creating a new
TransformerFactory instance on each request which causes an expensive
provider search. We can
Based on the dependency comment, this is what I figured out.
There are several geronimo system modules referring to non existant (in
geronimo distribution) JAR files. I don't know how the geronimo instance is
still working fine if they are required or why those files are referenced if
they are
IMO, although those files are in the claspath of the manifest file of some
jars, Geronimo may not need them, like the saaj, Axis2 has their own
implementations.The search is caused by the WSDLQueryHandler, it need to
output the DOM to text. I guess that in you webservice client, the codes may
Hi,
Geronimo: v 2.1.3
OS: Windows XP, Windows Server 2003
I've a web-service that gets polled every N minutes, I noticed that when it
is servicing a request the CPU usage is hitting close to 80%. I expect to
have multiple clients to this web-service so it is going to be a problem.
Based on
It seems that the search for service provider for the TransformerFactory
takes too much time.I suggest you set the the corresponding implemenation
via system property or put it to a jaxp.properties in the jre's lib folder.
You could refer more in the Java Doc of TransformerFactory class.
Ivan
On Apr 29, 2009, at 10:32 PM, Ivan wrote:
It seems that the search for service provider for the
TransformerFactory takes too much time.
I suggest you set the the corresponding implemenation via system
property or put it to a jaxp.properties in the jre's lib folder.
You could refer more in
