11:52 a.m.
Never create the same JAXBContext more than once
------------------------------------------------
Key: JBWS-1857
URL: http://jira.jboss.com/jira/browse/JBWS-1857
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jbossws-jaxws
Affects Versions: jbossws-1.2.1
Reporter: Johann Gyger
service.getPort() may become an expensive operation (i.e., several seconds) when using a
non-trivial WSDL with complex types. We have been able to track down our performance
problems to an incorrect usage of JAXB-RI in JBOSS-JAXWS. According to
https://wsit.dev.java.net/servlets/ReadMsg?list=dev&msgNo=66, creating new instances
of JAXBContext is an expensive operation.
In our WSDL we counted 28 instance creations of JAXBContext. Most of them are created
through the following call hierarchy:
JAXBContext.newInstance(Class[], Map<String,?>) line: 570
JAXBContext.newInstance(Class...) line: 522
JAXBAccessor$1.create(Class) line: 67
JAXBAccessor$1.create(ParameterMetaData) line: 54
ParameterMetaData.eagerInitialize() line: 470
OperationMetaData.eagerInitialize(List<Method>) line: 469
ClientEndpointMetaData(EndpointMetaData).eagerInitializeOperations() line: 516
ClientEndpointMetaData(EndpointMetaData).initializeInternal() line: 502
ClientEndpointMetaData(EndpointMetaData).eagerInitialize() line: 490
JAXWSClientMetaDataBuilder.rebuildEndpointMetaData(EndpointMetaData, Class<?>) line:
292
ServiceDelegateImpl.getPortInternal(EndpointMetaData, Class<T>) line: 274
ServiceDelegateImpl.getPort(QName, Class<T>) line: 200
A JProbe analysis (see attached file) revealed that actually most of the time (96.4%) of
service.getPort() is spent in JAXBContext.newInstance(). Please see attached JProbe
report.
Compared to JAX-WS RI (Metro) the performance of service.getPort() is extremely bad.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:54 a.m.
New subject: [JBoss JIRA] Updated: (JBWS-1857) Never create the same JAXBContext more than once
[ http://jira.jboss.com/jira/browse/JBWS-1857?page=all ]
Johann Gyger updated JBWS-1857:
-------------------------------
Attachment: jprobe_service_get_port.txt
JProbe analysis of service.getPort()
Never create the same JAXBContext more than once
------------------------------------------------
Key: JBWS-1857
URL: http://jira.jboss.com/jira/browse/JBWS-1857
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-jaxws
Affects Versions: jbossws-1.2.1
Reporter: Johann Gyger
Attachments: jprobe_service_get_port.txt
service.getPort() may become an expensive operation (i.e., several seconds) when using a
non-trivial WSDL with complex types. We have been able to track down our performance
problems to an incorrect usage of JAXB-RI in JBOSS-JAXWS. According to
https://wsit.dev.java.net/servlets/ReadMsg?list=dev&msgNo=66, creating new instances
of JAXBContext is an expensive operation.
In our WSDL we counted 28 instance creations of JAXBContext. Most of them are created
through the following call hierarchy:
JAXBContext.newInstance(Class[], Map<String,?>) line: 570
JAXBContext.newInstance(Class...) line: 522
JAXBAccessor$1.create(Class) line: 67
JAXBAccessor$1.create(ParameterMetaData) line: 54
ParameterMetaData.eagerInitialize() line: 470
OperationMetaData.eagerInitialize(List<Method>) line: 469
ClientEndpointMetaData(EndpointMetaData).eagerInitializeOperations() line: 516
ClientEndpointMetaData(EndpointMetaData).initializeInternal() line: 502
ClientEndpointMetaData(EndpointMetaData).eagerInitialize() line: 490
JAXWSClientMetaDataBuilder.rebuildEndpointMetaData(EndpointMetaData, Class<?>)
line: 292
ServiceDelegateImpl.getPortInternal(EndpointMetaData, Class<T>) line: 274
ServiceDelegateImpl.getPort(QName, Class<T>) line: 200
A JProbe analysis (see attached file) revealed that actually most of the time (96.4%) of
service.getPort() is spent in JAXBContext.newInstance(). Please see attached JProbe
report.
Compared to JAX-WS RI (Metro) the performance of service.getPort() is extremely bad.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:56 a.m.
New subject: [JBoss JIRA] Updated: (JBWS-1857) Never create the same JAXBContext more than once
[ http://jira.jboss.com/jira/browse/JBWS-1857?page=all ]
Johann Gyger updated JBWS-1857:
-------------------------------
Description:
service.getPort() may become an expensive operation (i.e., several seconds) when using a
non-trivial WSDL with complex types. We have been able to track down our performance
problems to an incorrect usage of JAXB-RI in JBOSS-JAXWS. According to
https://wsit.dev.java.net/servlets/ReadMsg?list=dev&msgNo=66 creating new instances of
JAXBContext is an expensive operation.
In our WSDL we counted 28 instance creations of JAXBContext. Most of them are created
through the following call hierarchy:
JAXBContext.newInstance(Class[], Map<String,?>) line: 570
JAXBContext.newInstance(Class...) line: 522
JAXBAccessor$1.create(Class) line: 67
JAXBAccessor$1.create(ParameterMetaData) line: 54
ParameterMetaData.eagerInitialize() line: 470
OperationMetaData.eagerInitialize(List<Method>) line: 469
ClientEndpointMetaData(EndpointMetaData).eagerInitializeOperations() line: 516
ClientEndpointMetaData(EndpointMetaData).initializeInternal() line: 502
ClientEndpointMetaData(EndpointMetaData).eagerInitialize() line: 490
JAXWSClientMetaDataBuilder.rebuildEndpointMetaData(EndpointMetaData, Class<?>) line:
292
ServiceDelegateImpl.getPortInternal(EndpointMetaData, Class<T>) line: 274
ServiceDelegateImpl.getPort(QName, Class<T>) line: 200
A JProbe analysis (see attached file) revealed that actually most of the time (96.4%) of
service.getPort() is spent in JAXBContext.newInstance(). Please see attached JProbe
report.
Compared to JAX-WS RI (Metro) the performance of service.getPort() is extremely bad.
was:
service.getPort() may become an expensive operation (i.e., several seconds) when using a
non-trivial WSDL with complex types. We have been able to track down our performance
problems to an incorrect usage of JAXB-RI in JBOSS-JAXWS. According to
https://wsit.dev.java.net/servlets/ReadMsg?list=dev&msgNo=66, creating new instances
of JAXBContext is an expensive operation.
In our WSDL we counted 28 instance creations of JAXBContext. Most of them are created
through the following call hierarchy:
JAXBContext.newInstance(Class[], Map<String,?>) line: 570
JAXBContext.newInstance(Class...) line: 522
JAXBAccessor$1.create(Class) line: 67
JAXBAccessor$1.create(ParameterMetaData) line: 54
ParameterMetaData.eagerInitialize() line: 470
OperationMetaData.eagerInitialize(List<Method>) line: 469
ClientEndpointMetaData(EndpointMetaData).eagerInitializeOperations() line: 516
ClientEndpointMetaData(EndpointMetaData).initializeInternal() line: 502
ClientEndpointMetaData(EndpointMetaData).eagerInitialize() line: 490
JAXWSClientMetaDataBuilder.rebuildEndpointMetaData(EndpointMetaData, Class<?>) line:
292
ServiceDelegateImpl.getPortInternal(EndpointMetaData, Class<T>) line: 274
ServiceDelegateImpl.getPort(QName, Class<T>) line: 200
A JProbe analysis (see attached file) revealed that actually most of the time (96.4%) of
service.getPort() is spent in JAXBContext.newInstance(). Please see attached JProbe
report.
Compared to JAX-WS RI (Metro) the performance of service.getPort() is extremely bad.
Never create the same JAXBContext more than once
------------------------------------------------
Key: JBWS-1857
URL: http://jira.jboss.com/jira/browse/JBWS-1857
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-jaxws
Affects Versions: jbossws-1.2.1
Reporter: Johann Gyger
Attachments: jprobe_service_get_port.txt
service.getPort() may become an expensive operation (i.e., several seconds) when using a
non-trivial WSDL with complex types. We have been able to track down our performance
problems to an incorrect usage of JAXB-RI in JBOSS-JAXWS. According to
https://wsit.dev.java.net/servlets/ReadMsg?list=dev&msgNo=66 creating new instances of
JAXBContext is an expensive operation.
In our WSDL we counted 28 instance creations of JAXBContext. Most of them are created
through the following call hierarchy:
JAXBContext.newInstance(Class[], Map<String,?>) line: 570
JAXBContext.newInstance(Class...) line: 522
JAXBAccessor$1.create(Class) line: 67
JAXBAccessor$1.create(ParameterMetaData) line: 54
ParameterMetaData.eagerInitialize() line: 470
OperationMetaData.eagerInitialize(List<Method>) line: 469
ClientEndpointMetaData(EndpointMetaData).eagerInitializeOperations() line: 516
ClientEndpointMetaData(EndpointMetaData).initializeInternal() line: 502
ClientEndpointMetaData(EndpointMetaData).eagerInitialize() line: 490
JAXWSClientMetaDataBuilder.rebuildEndpointMetaData(EndpointMetaData, Class<?>)
line: 292
ServiceDelegateImpl.getPortInternal(EndpointMetaData, Class<T>) line: 274
ServiceDelegateImpl.getPort(QName, Class<T>) line: 200
A JProbe analysis (see attached file) revealed that actually most of the time (96.4%) of
service.getPort() is spent in JAXBContext.newInstance(). Please see attached JProbe
report.
Compared to JAX-WS RI (Metro) the performance of service.getPort() is extremely bad.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:43 p.m.
New subject: [JBoss JIRA] Updated: (JBWS-1857) Never create the same JAXBContext more than once
[ http://jira.jboss.com/jira/browse/JBWS-1857?page=all ]
Johann Gyger updated JBWS-1857:
-------------------------------
Attachment: jbossws-src-1.2.1.GA-jaxb-context.patch
This little patch illustrates how to reuse the JAXB context of JAXWSMetaDataBuilder in
JAXBAccessor. The patch is not a proper solution and is not thread safe, however, it
proofs that the same JAXB context can be reused.
Never create the same JAXBContext more than once
------------------------------------------------
Key: JBWS-1857
URL: http://jira.jboss.com/jira/browse/JBWS-1857
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-jaxws
Affects Versions: jbossws-1.2.1
Reporter: Johann Gyger
Attachments: jbossws-src-1.2.1.GA-jaxb-context.patch,
jprobe_service_get_port.txt
service.getPort() may become an expensive operation (i.e., several seconds) when using a
non-trivial WSDL with complex types. We have been able to track down our performance
problems to an incorrect usage of JAXB-RI in JBOSS-JAXWS. According to
https://wsit.dev.java.net/servlets/ReadMsg?list=dev&msgNo=66 creating new instances of
JAXBContext is an expensive operation.
In our WSDL we counted 28 instance creations of JAXBContext. Most of them are created
through the following call hierarchy:
JAXBContext.newInstance(Class[], Map<String,?>) line: 570
JAXBContext.newInstance(Class...) line: 522
JAXBAccessor$1.create(Class) line: 67
JAXBAccessor$1.create(ParameterMetaData) line: 54
ParameterMetaData.eagerInitialize() line: 470
OperationMetaData.eagerInitialize(List<Method>) line: 469
ClientEndpointMetaData(EndpointMetaData).eagerInitializeOperations() line: 516
ClientEndpointMetaData(EndpointMetaData).initializeInternal() line: 502
ClientEndpointMetaData(EndpointMetaData).eagerInitialize() line: 490
JAXWSClientMetaDataBuilder.rebuildEndpointMetaData(EndpointMetaData, Class<?>)
line: 292
ServiceDelegateImpl.getPortInternal(EndpointMetaData, Class<T>) line: 274
ServiceDelegateImpl.getPort(QName, Class<T>) line: 200
A JProbe analysis (see attached file) revealed that actually most of the time (96.4%) of
service.getPort() is spent in JAXBContext.newInstance(). Please see attached JProbe
report.
Compared to JAX-WS RI (Metro) the performance of service.getPort() is extremely bad.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:25 p.m.
New subject: [JBoss JIRA] Updated: (JBWS-1857) Never create the same JAXBContext more than once
[ http://jira.jboss.com/jira/browse/JBWS-1857?page=all ]
Johann Gyger updated JBWS-1857:
-------------------------------
Affects Version/s: jbossws-2.0.1
Never create the same JAXBContext more than once
------------------------------------------------
Key: JBWS-1857
URL: http://jira.jboss.com/jira/browse/JBWS-1857
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-1.2.1, jbossws-2.0.1
Reporter: Johann Gyger
Attachments: jbossws-src-1.2.1.GA-jaxb-context.patch,
jprobe_service_get_port.txt
service.getPort() may become an expensive operation (i.e., several seconds) when using a
non-trivial WSDL with complex types. We have been able to track down our performance
problems to an incorrect usage of JAXB-RI in JBOSS-JAXWS. According to
https://wsit.dev.java.net/servlets/ReadMsg?list=dev&msgNo=66 creating new instances of
JAXBContext is an expensive operation.
In our WSDL we counted 28 instance creations of JAXBContext. Most of them are created
through the following call hierarchy:
JAXBContext.newInstance(Class[], Map<String,?>) line: 570
JAXBContext.newInstance(Class...) line: 522
JAXBAccessor$1.create(Class) line: 67
JAXBAccessor$1.create(ParameterMetaData) line: 54
ParameterMetaData.eagerInitialize() line: 470
OperationMetaData.eagerInitialize(List<Method>) line: 469
ClientEndpointMetaData(EndpointMetaData).eagerInitializeOperations() line: 516
ClientEndpointMetaData(EndpointMetaData).initializeInternal() line: 502
ClientEndpointMetaData(EndpointMetaData).eagerInitialize() line: 490
JAXWSClientMetaDataBuilder.rebuildEndpointMetaData(EndpointMetaData, Class<?>)
line: 292
ServiceDelegateImpl.getPortInternal(EndpointMetaData, Class<T>) line: 274
ServiceDelegateImpl.getPort(QName, Class<T>) line: 200
A JProbe analysis (see attached file) revealed that actually most of the time (96.4%) of
service.getPort() is spent in JAXBContext.newInstance(). Please see attached JProbe
report.
Compared to JAX-WS RI (Metro) the performance of service.getPort() is extremely bad.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:20 a.m.
New subject: [JBoss JIRA] Updated: (JBWS-1857) Never create the same JAXBContext more than once
[ http://jira.jboss.com/jira/browse/JBWS-1857?page=all ]
Thomas Diesler updated JBWS-1857:
---------------------------------
Fix Version/s: jbossws-native-2.0.4
Never create the same JAXBContext more than once
------------------------------------------------
Key: JBWS-1857
URL: http://jira.jboss.com/jira/browse/JBWS-1857
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-1.2.1, jbossws-2.0.1
Reporter: Johann Gyger
Fix For: jbossws-native-2.0.4
Attachments: jbossws-src-1.2.1.GA-jaxb-context.patch,
jprobe_service_get_port.txt
service.getPort() may become an expensive operation (i.e., several seconds) when using a
non-trivial WSDL with complex types. We have been able to track down our performance
problems to an incorrect usage of JAXB-RI in JBOSS-JAXWS. According to
https://wsit.dev.java.net/servlets/ReadMsg?list=dev&msgNo=66 creating new instances of
JAXBContext is an expensive operation.
In our WSDL we counted 28 instance creations of JAXBContext. Most of them are created
through the following call hierarchy:
JAXBContext.newInstance(Class[], Map<String,?>) line: 570
JAXBContext.newInstance(Class...) line: 522
JAXBAccessor$1.create(Class) line: 67
JAXBAccessor$1.create(ParameterMetaData) line: 54
ParameterMetaData.eagerInitialize() line: 470
OperationMetaData.eagerInitialize(List<Method>) line: 469
ClientEndpointMetaData(EndpointMetaData).eagerInitializeOperations() line: 516
ClientEndpointMetaData(EndpointMetaData).initializeInternal() line: 502
ClientEndpointMetaData(EndpointMetaData).eagerInitialize() line: 490
JAXWSClientMetaDataBuilder.rebuildEndpointMetaData(EndpointMetaData, Class<?>)
line: 292
ServiceDelegateImpl.getPortInternal(EndpointMetaData, Class<T>) line: 274
ServiceDelegateImpl.getPort(QName, Class<T>) line: 200
A JProbe analysis (see attached file) revealed that actually most of the time (96.4%) of
service.getPort() is spent in JAXBContext.newInstance(). Please see attached JProbe
report.
Compared to JAX-WS RI (Metro) the performance of service.getPort() is extremely bad.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:57 p.m.
New subject: [JBoss JIRA] Updated: (JBWS-1857) JAXBContext created for every invokation of service.getPort()
[ http://jira.jboss.com/jira/browse/JBWS-1857?page=all ]
Thomas Diesler updated JBWS-1857:
---------------------------------
Summary: JAXBContext created for every invokation of service.getPort() (was: Never
create the same JAXBContext more than once)
JAXBContext created for every invokation of service.getPort()
-------------------------------------------------------------
Key: JBWS-1857
URL: http://jira.jboss.com/jira/browse/JBWS-1857
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-1.2.1, jbossws-2.0.1
Reporter: Johann Gyger
Assigned To: Thomas Diesler
Attachments: jbossws-src-1.2.1.GA-jaxb-context.patch,
jprobe_service_get_port.txt
service.getPort() may become an expensive operation (i.e., several seconds) when using a
non-trivial WSDL with complex types. We have been able to track down our performance
problems to an incorrect usage of JAXB-RI in JBOSS-JAXWS. According to
https://wsit.dev.java.net/servlets/ReadMsg?list=dev&msgNo=66 creating new instances of
JAXBContext is an expensive operation.
In our WSDL we counted 28 instance creations of JAXBContext. Most of them are created
through the following call hierarchy:
JAXBContext.newInstance(Class[], Map<String,?>) line: 570
JAXBContext.newInstance(Class...) line: 522
JAXBAccessor$1.create(Class) line: 67
JAXBAccessor$1.create(ParameterMetaData) line: 54
ParameterMetaData.eagerInitialize() line: 470
OperationMetaData.eagerInitialize(List<Method>) line: 469
ClientEndpointMetaData(EndpointMetaData).eagerInitializeOperations() line: 516
ClientEndpointMetaData(EndpointMetaData).initializeInternal() line: 502
ClientEndpointMetaData(EndpointMetaData).eagerInitialize() line: 490
JAXWSClientMetaDataBuilder.rebuildEndpointMetaData(EndpointMetaData, Class<?>)
line: 292
ServiceDelegateImpl.getPortInternal(EndpointMetaData, Class<T>) line: 274
ServiceDelegateImpl.getPort(QName, Class<T>) line: 200
A JProbe analysis (see attached file) revealed that actually most of the time (96.4%) of
service.getPort() is spent in JAXBContext.newInstance(). Please see attached JProbe
report.
Compared to JAX-WS RI (Metro) the performance of service.getPort() is extremely bad.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:20 p.m.
New subject: [JBoss JIRA] Commented: (JBWS-1857) JAXBContext created for every invokation of service.getPort()
[ http://jira.jboss.com/jira/browse/JBWS-1857?page=comments#action_12400517 ]
Johann Gyger commented on JBWS-1857:
------------------------------------
I fully agree with your first sentence that the JAXBContext cannot be a static field of
JAXWSMetaDataBuilder. But this is not the point. The problem is that _one_ invocation of
service.getPort() creates _more_ than one instance of JAXBContext. In our case we counted
28 instances.
I would say that every port instance must have exactly one instance of JAXBContext.
JAXBContext created for every invokation of service.getPort()
-------------------------------------------------------------
Key: JBWS-1857
URL: http://jira.jboss.com/jira/browse/JBWS-1857
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-1.2.1, jbossws-2.0.1
Reporter: Johann Gyger
Assigned To: Thomas Diesler
Attachments: jbossws-src-1.2.1.GA-jaxb-context.patch,
jprobe_service_get_port.txt
service.getPort() may become an expensive operation (i.e., several seconds) when using a
non-trivial WSDL with complex types. We have been able to track down our performance
problems to an incorrect usage of JAXB-RI in JBOSS-JAXWS. According to
https://wsit.dev.java.net/servlets/ReadMsg?list=dev&msgNo=66 creating new instances of
JAXBContext is an expensive operation.
In our WSDL we counted 28 instance creations of JAXBContext. Most of them are created
through the following call hierarchy:
JAXBContext.newInstance(Class[], Map<String,?>) line: 570
JAXBContext.newInstance(Class...) line: 522
JAXBAccessor$1.create(Class) line: 67
JAXBAccessor$1.create(ParameterMetaData) line: 54
ParameterMetaData.eagerInitialize() line: 470
OperationMetaData.eagerInitialize(List<Method>) line: 469
ClientEndpointMetaData(EndpointMetaData).eagerInitializeOperations() line: 516
ClientEndpointMetaData(EndpointMetaData).initializeInternal() line: 502
ClientEndpointMetaData(EndpointMetaData).eagerInitialize() line: 490
JAXWSClientMetaDataBuilder.rebuildEndpointMetaData(EndpointMetaData, Class<?>)
line: 292
ServiceDelegateImpl.getPortInternal(EndpointMetaData, Class<T>) line: 274
ServiceDelegateImpl.getPort(QName, Class<T>) line: 200
A JProbe analysis (see attached file) revealed that actually most of the time (96.4%) of
service.getPort() is spent in JAXBContext.newInstance(). Please see attached JProbe
report.
Compared to JAX-WS RI (Metro) the performance of service.getPort() is extremely bad.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:22 p.m.
New subject: [JBoss JIRA] Reopened: (JBWS-1857) JAXBContext created for every invokation of service.getPort()
[ http://jira.jboss.com/jira/browse/JBWS-1857?page=all ]
Johann Gyger reopened JBWS-1857:
--------------------------------
JAXBContext created for every invokation of service.getPort()
-------------------------------------------------------------
Key: JBWS-1857
URL: http://jira.jboss.com/jira/browse/JBWS-1857
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-1.2.1, jbossws-2.0.1
Reporter: Johann Gyger
Assigned To: Thomas Diesler
Attachments: jbossws-src-1.2.1.GA-jaxb-context.patch,
jprobe_service_get_port.txt
service.getPort() may become an expensive operation (i.e., several seconds) when using a
non-trivial WSDL with complex types. We have been able to track down our performance
problems to an incorrect usage of JAXB-RI in JBOSS-JAXWS. According to
https://wsit.dev.java.net/servlets/ReadMsg?list=dev&msgNo=66 creating new instances of
JAXBContext is an expensive operation.
In our WSDL we counted 28 instance creations of JAXBContext. Most of them are created
through the following call hierarchy:
JAXBContext.newInstance(Class[], Map<String,?>) line: 570
JAXBContext.newInstance(Class...) line: 522
JAXBAccessor$1.create(Class) line: 67
JAXBAccessor$1.create(ParameterMetaData) line: 54
ParameterMetaData.eagerInitialize() line: 470
OperationMetaData.eagerInitialize(List<Method>) line: 469
ClientEndpointMetaData(EndpointMetaData).eagerInitializeOperations() line: 516
ClientEndpointMetaData(EndpointMetaData).initializeInternal() line: 502
ClientEndpointMetaData(EndpointMetaData).eagerInitialize() line: 490
JAXWSClientMetaDataBuilder.rebuildEndpointMetaData(EndpointMetaData, Class<?>)
line: 292
ServiceDelegateImpl.getPortInternal(EndpointMetaData, Class<T>) line: 274
ServiceDelegateImpl.getPort(QName, Class<T>) line: 200
A JProbe analysis (see attached file) revealed that actually most of the time (96.4%) of
service.getPort() is spent in JAXBContext.newInstance(). Please see attached JProbe
report.
Compared to JAX-WS RI (Metro) the performance of service.getPort() is extremely bad.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9 a.m.
New subject: [JBoss JIRA] Updated: (JBWS-1857) JAXBContext created for every invokation of service.getPort()
[ http://jira.jboss.com/jira/browse/JBWS-1857?page=all ]
Thomas Diesler updated JBWS-1857:
---------------------------------
Fix Version/s: jbossws-native-2.0.4
Please attach the wsdl that you construct the client with
JAXBContext created for every invokation of service.getPort()
-------------------------------------------------------------
Key: JBWS-1857
URL: http://jira.jboss.com/jira/browse/JBWS-1857
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-1.2.1, jbossws-2.0.1
Reporter: Johann Gyger
Assigned To: Thomas Diesler
Fix For: jbossws-native-2.0.4
Attachments: jbossws-src-1.2.1.GA-jaxb-context.patch,
jprobe_service_get_port.txt
service.getPort() may become an expensive operation (i.e., several seconds) when using a
non-trivial WSDL with complex types. We have been able to track down our performance
problems to an incorrect usage of JAXB-RI in JBOSS-JAXWS. According to
https://wsit.dev.java.net/servlets/ReadMsg?list=dev&msgNo=66 creating new instances of
JAXBContext is an expensive operation.
In our WSDL we counted 28 instance creations of JAXBContext. Most of them are created
through the following call hierarchy:
JAXBContext.newInstance(Class[], Map<String,?>) line: 570
JAXBContext.newInstance(Class...) line: 522
JAXBAccessor$1.create(Class) line: 67
JAXBAccessor$1.create(ParameterMetaData) line: 54
ParameterMetaData.eagerInitialize() line: 470
OperationMetaData.eagerInitialize(List<Method>) line: 469
ClientEndpointMetaData(EndpointMetaData).eagerInitializeOperations() line: 516
ClientEndpointMetaData(EndpointMetaData).initializeInternal() line: 502
ClientEndpointMetaData(EndpointMetaData).eagerInitialize() line: 490
JAXWSClientMetaDataBuilder.rebuildEndpointMetaData(EndpointMetaData, Class<?>)
line: 292
ServiceDelegateImpl.getPortInternal(EndpointMetaData, Class<T>) line: 274
ServiceDelegateImpl.getPort(QName, Class<T>) line: 200
A JProbe analysis (see attached file) revealed that actually most of the time (96.4%) of
service.getPort() is spent in JAXBContext.newInstance(). Please see attached JProbe
report.
Compared to JAX-WS RI (Metro) the performance of service.getPort() is extremely bad.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:16 p.m.
New subject: [JBoss JIRA] Updated: (JBWS-1857) JAXBContext created for every invokation of service.getPort()
[ http://jira.jboss.com/jira/browse/JBWS-1857?page=all ]
Johann Gyger updated JBWS-1857:
-------------------------------
Attachment: StammdatenService.wsdl
WSDL file being requested
JAXBContext created for every invokation of service.getPort()
-------------------------------------------------------------
Key: JBWS-1857
URL: http://jira.jboss.com/jira/browse/JBWS-1857
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-1.2.1, jbossws-2.0.1
Reporter: Johann Gyger
Assigned To: Thomas Diesler
Fix For: jbossws-native-2.0.4
Attachments: jbossws-src-1.2.1.GA-jaxb-context.patch,
jprobe_service_get_port.txt, StammdatenService.wsdl
service.getPort() may become an expensive operation (i.e., several seconds) when using a
non-trivial WSDL with complex types. We have been able to track down our performance
problems to an incorrect usage of JAXB-RI in JBOSS-JAXWS. According to
https://wsit.dev.java.net/servlets/ReadMsg?list=dev&msgNo=66 creating new instances of
JAXBContext is an expensive operation.
In our WSDL we counted 28 instance creations of JAXBContext. Most of them are created
through the following call hierarchy:
JAXBContext.newInstance(Class[], Map<String,?>) line: 570
JAXBContext.newInstance(Class...) line: 522
JAXBAccessor$1.create(Class) line: 67
JAXBAccessor$1.create(ParameterMetaData) line: 54
ParameterMetaData.eagerInitialize() line: 470
OperationMetaData.eagerInitialize(List<Method>) line: 469
ClientEndpointMetaData(EndpointMetaData).eagerInitializeOperations() line: 516
ClientEndpointMetaData(EndpointMetaData).initializeInternal() line: 502
ClientEndpointMetaData(EndpointMetaData).eagerInitialize() line: 490
JAXWSClientMetaDataBuilder.rebuildEndpointMetaData(EndpointMetaData, Class<?>)
line: 292
ServiceDelegateImpl.getPortInternal(EndpointMetaData, Class<T>) line: 274
ServiceDelegateImpl.getPort(QName, Class<T>) line: 200
A JProbe analysis (see attached file) revealed that actually most of the time (96.4%) of
service.getPort() is spent in JAXBContext.newInstance(). Please see attached JProbe
report.
Compared to JAX-WS RI (Metro) the performance of service.getPort() is extremely bad.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:38 a.m.
New subject: [JBoss JIRA] Commented: (JBWS-1857) JAXBContext created for every invokation of service.getPort()
[ http://jira.jboss.com/jira/browse/JBWS-1857?page=comments#action_12400818 ]
Thomas Diesler commented on JBWS-1857:
--------------------------------------
Confirmed
public void testPortCreation() throws Exception
{
File wsdlFile = new
File("resources/jaxws/jbws1857/StammdatenService.wsdl");
QName serviceName = new QName("http://example.com",
"StammdatenService");
Service service = Service.create(wsdlFile.toURL(), serviceName);
Stammdaten port = service.getPort(Stammdaten.class);
}
tests-run-internal:
[junit] Running org.jboss.test.ws.jaxws.jbws1857.JBWS1857TestCase
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 36.02 sec
BUILD SUCCESSFUL
Total time: 40 seconds
JAXBContext created for every invokation of service.getPort()
-------------------------------------------------------------
Key: JBWS-1857
URL: http://jira.jboss.com/jira/browse/JBWS-1857
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-1.2.1, jbossws-2.0.1
Reporter: Johann Gyger
Assigned To: Thomas Diesler
Fix For: jbossws-native-2.0.4
Attachments: jbossws-src-1.2.1.GA-jaxb-context.patch,
jprobe_service_get_port.txt, StammdatenService.wsdl
service.getPort() may become an expensive operation (i.e., several seconds) when using a
non-trivial WSDL with complex types. We have been able to track down our performance
problems to an incorrect usage of JAXB-RI in JBOSS-JAXWS. According to
https://wsit.dev.java.net/servlets/ReadMsg?list=dev&msgNo=66 creating new instances of
JAXBContext is an expensive operation.
In our WSDL we counted 28 instance creations of JAXBContext. Most of them are created
through the following call hierarchy:
JAXBContext.newInstance(Class[], Map<String,?>) line: 570
JAXBContext.newInstance(Class...) line: 522
JAXBAccessor$1.create(Class) line: 67
JAXBAccessor$1.create(ParameterMetaData) line: 54
ParameterMetaData.eagerInitialize() line: 470
OperationMetaData.eagerInitialize(List<Method>) line: 469
ClientEndpointMetaData(EndpointMetaData).eagerInitializeOperations() line: 516
ClientEndpointMetaData(EndpointMetaData).initializeInternal() line: 502
ClientEndpointMetaData(EndpointMetaData).eagerInitialize() line: 490
JAXWSClientMetaDataBuilder.rebuildEndpointMetaData(EndpointMetaData, Class<?>)
line: 292
ServiceDelegateImpl.getPortInternal(EndpointMetaData, Class<T>) line: 274
ServiceDelegateImpl.getPort(QName, Class<T>) line: 200
A JProbe analysis (see attached file) revealed that actually most of the time (96.4%) of
service.getPort() is spent in JAXBContext.newInstance(). Please see attached JProbe
report.
Compared to JAX-WS RI (Metro) the performance of service.getPort() is extremely bad.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:40 a.m.
New subject: [JBoss JIRA] Updated: (JBWS-1857) JAXBContext created for every wrapper type
[ http://jira.jboss.com/jira/browse/JBWS-1857?page=all ]
Thomas Diesler updated JBWS-1857:
---------------------------------
Summary: JAXBContext created for every wrapper type (was: JAXBContext created for
every invokation of service.getPort())
JAXBContext created for every wrapper type
------------------------------------------
Key: JBWS-1857
URL: http://jira.jboss.com/jira/browse/JBWS-1857
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-1.2.1, jbossws-2.0.1
Reporter: Johann Gyger
Assigned To: Thomas Diesler
Fix For: jbossws-native-2.0.4
Attachments: jbossws-src-1.2.1.GA-jaxb-context.patch,
jprobe_service_get_port.txt, StammdatenService.wsdl
service.getPort() may become an expensive operation (i.e., several seconds) when using a
non-trivial WSDL with complex types. We have been able to track down our performance
problems to an incorrect usage of JAXB-RI in JBOSS-JAXWS. According to
https://wsit.dev.java.net/servlets/ReadMsg?list=dev&msgNo=66 creating new instances of
JAXBContext is an expensive operation.
In our WSDL we counted 28 instance creations of JAXBContext. Most of them are created
through the following call hierarchy:
JAXBContext.newInstance(Class[], Map<String,?>) line: 570
JAXBContext.newInstance(Class...) line: 522
JAXBAccessor$1.create(Class) line: 67
JAXBAccessor$1.create(ParameterMetaData) line: 54
ParameterMetaData.eagerInitialize() line: 470
OperationMetaData.eagerInitialize(List<Method>) line: 469
ClientEndpointMetaData(EndpointMetaData).eagerInitializeOperations() line: 516
ClientEndpointMetaData(EndpointMetaData).initializeInternal() line: 502
ClientEndpointMetaData(EndpointMetaData).eagerInitialize() line: 490
JAXWSClientMetaDataBuilder.rebuildEndpointMetaData(EndpointMetaData, Class<?>)
line: 292
ServiceDelegateImpl.getPortInternal(EndpointMetaData, Class<T>) line: 274
ServiceDelegateImpl.getPort(QName, Class<T>) line: 200
A JProbe analysis (see attached file) revealed that actually most of the time (96.4%) of
service.getPort() is spent in JAXBContext.newInstance(). Please see attached JProbe
report.
Compared to JAX-WS RI (Metro) the performance of service.getPort() is extremely bad.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:20 p.m.
New subject: [JBoss JIRA] Reopened: (JBWS-1857) JAXBContext created for every wrapper type
[ http://jira.jboss.com/jira/browse/JBWS-1857?page=all ]
Richard Opalka reopened JBWS-1857:
----------------------------------
Assignee: (was: Thomas Diesler)
JAXB context cache isn't properly scoped.
The JAXB context cache should be e.g. property of jaxws service
and not thread property as it is now.
JAXBContext created for every wrapper type
------------------------------------------
Key: JBWS-1857
URL: http://jira.jboss.com/jira/browse/JBWS-1857
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-1.2.1, jbossws-2.0.1
Reporter: Johann Gyger
Attachments: jbossws-src-1.2.1.GA-jaxb-context.patch,
jprobe_service_get_port.txt, StammdatenService.wsdl
service.getPort() may become an expensive operation (i.e., several seconds) when using a
non-trivial WSDL with complex types. We have been able to track down our performance
problems to an incorrect usage of JAXB-RI in JBOSS-JAXWS. According to
https://wsit.dev.java.net/servlets/ReadMsg?list=dev&msgNo=66 creating new instances of
JAXBContext is an expensive operation.
In our WSDL we counted 28 instance creations of JAXBContext. Most of them are created
through the following call hierarchy:
JAXBContext.newInstance(Class[], Map<String,?>) line: 570
JAXBContext.newInstance(Class...) line: 522
JAXBAccessor$1.create(Class) line: 67
JAXBAccessor$1.create(ParameterMetaData) line: 54
ParameterMetaData.eagerInitialize() line: 470
OperationMetaData.eagerInitialize(List<Method>) line: 469
ClientEndpointMetaData(EndpointMetaData).eagerInitializeOperations() line: 516
ClientEndpointMetaData(EndpointMetaData).initializeInternal() line: 502
ClientEndpointMetaData(EndpointMetaData).eagerInitialize() line: 490
JAXWSClientMetaDataBuilder.rebuildEndpointMetaData(EndpointMetaData, Class<?>)
line: 292
ServiceDelegateImpl.getPortInternal(EndpointMetaData, Class<T>) line: 274
ServiceDelegateImpl.getPort(QName, Class<T>) line: 200
A JProbe analysis (see attached file) revealed that actually most of the time (96.4%) of
service.getPort() is spent in JAXBContext.newInstance(). Please see attached JProbe
report.
Compared to JAX-WS RI (Metro) the performance of service.getPort() is extremely bad.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:21 p.m.
New subject: [JBoss JIRA] Updated: (JBWS-1857) JAXBContext created for every wrapper type
[ http://jira.jboss.com/jira/browse/JBWS-1857?page=all ]
Richard Opalka updated JBWS-1857:
---------------------------------
Fix Version/s: (was: jbossws-native-3.0.1)
JAXBContext created for every wrapper type
------------------------------------------
Key: JBWS-1857
URL: http://jira.jboss.com/jira/browse/JBWS-1857
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-1.2.1, jbossws-2.0.1
Reporter: Johann Gyger
Attachments: jbossws-src-1.2.1.GA-jaxb-context.patch,
jprobe_service_get_port.txt, StammdatenService.wsdl
service.getPort() may become an expensive operation (i.e., several seconds) when using a
non-trivial WSDL with complex types. We have been able to track down our performance
problems to an incorrect usage of JAXB-RI in JBOSS-JAXWS. According to
https://wsit.dev.java.net/servlets/ReadMsg?list=dev&msgNo=66 creating new instances of
JAXBContext is an expensive operation.
In our WSDL we counted 28 instance creations of JAXBContext. Most of them are created
through the following call hierarchy:
JAXBContext.newInstance(Class[], Map<String,?>) line: 570
JAXBContext.newInstance(Class...) line: 522
JAXBAccessor$1.create(Class) line: 67
JAXBAccessor$1.create(ParameterMetaData) line: 54
ParameterMetaData.eagerInitialize() line: 470
OperationMetaData.eagerInitialize(List<Method>) line: 469
ClientEndpointMetaData(EndpointMetaData).eagerInitializeOperations() line: 516
ClientEndpointMetaData(EndpointMetaData).initializeInternal() line: 502
ClientEndpointMetaData(EndpointMetaData).eagerInitialize() line: 490
JAXWSClientMetaDataBuilder.rebuildEndpointMetaData(EndpointMetaData, Class<?>)
line: 292
ServiceDelegateImpl.getPortInternal(EndpointMetaData, Class<T>) line: 274
ServiceDelegateImpl.getPort(QName, Class<T>) line: 200
A JProbe analysis (see attached file) revealed that actually most of the time (96.4%) of
service.getPort() is spent in JAXBContext.newInstance(). Please see attached JProbe
report.
Compared to JAX-WS RI (Metro) the performance of service.getPort() is extremely bad.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:20 p.m.
New subject: [JBoss JIRA] Updated: (JBWS-1857) JAXBContext created for every wrapper type
[ http://jira.jboss.com/jira/browse/JBWS-1857?page=all ]
Alessio Soldano updated JBWS-1857:
----------------------------------
Fix Version/s: jbossws-native-3.0.3
JAXBContext created for every wrapper type
------------------------------------------
Key: JBWS-1857
URL: http://jira.jboss.com/jira/browse/JBWS-1857
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-1.2.1, jbossws-2.0.1
Reporter: Johann Gyger
Fix For: jbossws-native-3.0.3
Attachments: jbossws-src-1.2.1.GA-jaxb-context.patch,
jprobe_service_get_port.txt, StammdatenService.wsdl
service.getPort() may become an expensive operation (i.e., several seconds) when using a
non-trivial WSDL with complex types. We have been able to track down our performance
problems to an incorrect usage of JAXB-RI in JBOSS-JAXWS. According to
https://wsit.dev.java.net/servlets/ReadMsg?list=dev&msgNo=66 creating new instances of
JAXBContext is an expensive operation.
In our WSDL we counted 28 instance creations of JAXBContext. Most of them are created
through the following call hierarchy:
JAXBContext.newInstance(Class[], Map<String,?>) line: 570
JAXBContext.newInstance(Class...) line: 522
JAXBAccessor$1.create(Class) line: 67
JAXBAccessor$1.create(ParameterMetaData) line: 54
ParameterMetaData.eagerInitialize() line: 470
OperationMetaData.eagerInitialize(List<Method>) line: 469
ClientEndpointMetaData(EndpointMetaData).eagerInitializeOperations() line: 516
ClientEndpointMetaData(EndpointMetaData).initializeInternal() line: 502
ClientEndpointMetaData(EndpointMetaData).eagerInitialize() line: 490
JAXWSClientMetaDataBuilder.rebuildEndpointMetaData(EndpointMetaData, Class<?>)
line: 292
ServiceDelegateImpl.getPortInternal(EndpointMetaData, Class<T>) line: 274
ServiceDelegateImpl.getPort(QName, Class<T>) line: 200
A JProbe analysis (see attached file) revealed that actually most of the time (96.4%) of
service.getPort() is spent in JAXBContext.newInstance(). Please see attached JProbe
report.
Compared to JAX-WS RI (Metro) the performance of service.getPort() is extremely bad.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5797
days inactive
6036
days old
jbossws-issues@lists.jboss.org
15 comments
4 participants
participants (4)
-
Alessio Soldano (JIRA) -
Johann Gyger (JIRA)
-
Richard Opalka (JIRA)
-
Thomas Diesler (JIRA)