[JBoss JIRA] (JBWS-3956) Random webservice deployment failure on windows
by Alessio Soldano (JIRA)
[ https://issues.jboss.org/browse/JBWS-3956?page=com.atlassian.jira.plugin.... ]
Alessio Soldano updated JBWS-3956:
----------------------------------
Assignee: Jim Ma (was: Alessio Soldano)
> Random webservice deployment failure on windows
> -----------------------------------------------
>
> Key: JBWS-3956
> URL: https://issues.jboss.org/browse/JBWS-3956
> Project: JBoss Web Services
> Issue Type: Bug
> Components: jbossws-cxf
> Reporter: Jan Blizňák
> Assignee: Jim Ma
> Attachments: jaxws-samples-wsrm-store.war
>
>
> When you try to deploy deployment with webservices and with -ds.xml (not sure if it is relevant) it from time to time cause a failure like this:
> {code:java}
> 14:42:05,312 WARN [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.jaxws-samples-wsrm-store.war" is using a private module ("org.apache.cxf.impl:main") which may be changed or removed in future versions without notice.
> 14:42:05,347 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-4) JBWS024061: Adding service endpoint metadata: id=SimpleService
> address=http://[::1]:8080/jaxws-samples-wsrm-store
> implementor=org.jboss.test.ws.jaxws.samples.wsrm.store.EndpointImpl
> serviceName={http://www.jboss.org/jbossws/ws-extensions/wsrm}RMService
> portName={http://www.jboss.org/jbossws/ws-extensions/wsrm}RMEndpointPort
> annotationWsdlLocation=null
> wsdlLocationOverride=null
> mtomEnabled=false
> 14:42:05,355 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-4) Creating Service {http://www.jboss.org/jbossws/ws-extensions/wsrm}RMService from class org.jboss.test.ws.jaxws.samples.wsrm.store.Endpoint
> 14:42:05,371 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-4) Setting the server's publish address to be http://[::1]:8080/jaxws-samples-wsrm-store
> 14:42:05,381 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."jaxws-samples-wsrm-store.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."jaxws-samples-wsrm-store.war".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of deployment "jaxws-samples-wsrm-store.war"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.NoClassDefFoundError: org/jboss/ws/common/Loggers
> at org.jboss.test.ws.jaxws.samples.wsrm.store.RMStoreFeature.initializeProvider(RMStoreFeature.java:85)
> at org.apache.cxf.feature.AbstractFeature.initialize(AbstractFeature.java:45)
> at org.apache.cxf.frontend.ServerFactoryBean.applyFeatures(ServerFactoryBean.java:249)
> at org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.java:211)
> at org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(JaxWsServerFactoryBean.java:211)
> at org.apache.cxf.jaxws.EndpointImpl.getServer(EndpointImpl.java:460)
> at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:338)
> at org.jboss.wsf.stack.cxf.deployment.EndpointImpl.doPublish(EndpointImpl.java:79)
> at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:255)
> at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:543)
> at org.jboss.wsf.stack.cxf.configuration.BusHolder.configure(BusHolder.java:231)
> at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.startDeploymentBus(BusDeploymentAspect.java:97)
> at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.start(BusDeploymentAspect.java:59)
> at org.jboss.as.webservices.deployers.AspectDeploymentProcessor.deploy(AspectDeploymentProcessor.java:73)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
> ... 5 more
> Caused by: java.lang.ClassNotFoundException: org.jboss.ws.common.Loggers from [Module "deployment.jaxws-samples-wsrm-store.war:main" from Service Module Loader]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:205)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:455)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:404)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:385)
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:130)
> ... 20 more
> 14:42:05,402 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0001: Bound data source [java:jboss/datasources/rmclientdb]
> 14:42:05,403 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:jboss/datasources/rmdb]
> 14:42:05,403 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 5) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "jaxws-samples-wsrm-store.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"jaxws-samples-wsrm-store.war\".INSTALL" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"jaxws-samples-wsrm-store.war\".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of deployment \"jaxws-samples-wsrm-store.war\"
> Caused by: java.lang.NoClassDefFoundError: org/jboss/ws/common/Loggers
> Caused by: java.lang.ClassNotFoundException: org.jboss.ws.common.Loggers from [Module \"deployment.jaxws-samples-wsrm-store.war:main\" from Service Module Loader]"}}
> 14:42:05,404 ERROR [org.jboss.as.server] (management-handler-thread - 5) WFLYSRV0021: Deploy of deployment "jaxws-samples-wsrm-store.war" was rolled back with the following failure message:
> {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"jaxws-samples-wsrm-store.war\".INSTALL" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"jaxws-samples-wsrm-store.war\".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of deployment \"jaxws-samples-wsrm-store.war\"
> Caused by: java.lang.NoClassDefFoundError: org/jboss/ws/common/Loggers
> Caused by: java.lang.ClassNotFoundException: org.jboss.ws.common.Loggers from [Module \"deployment.jaxws-samples-wsrm-store.war:main\" from Service Module Loader]"}}
> 14:42:05,423 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0010: Unbound data source [java:jboss/datasources/rmdb]
> 14:42:05,423 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0010: Unbound data source [java:jboss/datasources/rmclientdb]
> 14:42:05,427 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0028: Stopped deployment jaxws-samples-wsrm-store.war (runtime-name: jaxws-samples-wsrm-store.war) in 23ms
> 14:42:05,427 INFO [org.jboss.as.controller] (management-handler-thread - 5) WFLYCTL0183: Service status report
> WFLYCTL0186: Services which failed to start: service jboss.deployment.unit."jaxws-samples-wsrm-store.war".INSTALL
> {code}
> It might be cause by some sort of race condition because its intermittent nature, I was not able to narrow it down so far.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month
[JBoss JIRA] (JBWS-3957) publishWsdlImports writes WSDL-XML files with wrong characterset under Windows
by Alessio Soldano (JIRA)
[ https://issues.jboss.org/browse/JBWS-3957?page=com.atlassian.jira.plugin.... ]
Alessio Soldano updated JBWS-3957:
----------------------------------
Assignee: Jim Ma (was: Alessio Soldano)
> publishWsdlImports writes WSDL-XML files with wrong characterset under Windows
> ------------------------------------------------------------------------------
>
> Key: JBWS-3957
> URL: https://issues.jboss.org/browse/JBWS-3957
> Project: JBoss Web Services
> Issue Type: Bug
> Environment: WildFly 9, Windows 7 with default Java file.encoding Cp1252.
> Reporter: Martin Both
> Assignee: Jim Ma
> Fix For: jbossws-cxf-5.2.0.Final
>
>
> I would like to deploy a WebService but I get an exception. The WSDL XSD file contains an german character 'ä'. See:
> Here is the part of the XSD:
> <xs:simpleType name="Teilnehmerart">
> <xs:restriction base="xs:string">
> <xs:enumeration value="Privat"></xs:enumeration>
> <xs:enumeration value="Geschäftlich"></xs:enumeration>
> </xs:restriction>
> </xs:simpleType>
> The JBoss class org.jboss.ws.common.utils.AbstractWSDLFilePublisher
> writes the imported WSDL file using a FileWriter at line 166 + 167.
> FileWriter fw = new FileWriter(targetFile);
> wsdlWriter.writeWSDL(subdef, fw);
> In a next step this file is read again and results in an exception:
> Invalid byte 2 of 3-byte UTF-8 sequence.
> This is because the file is written in Cp1252 enconding together with an XML prolog
> UTF-8 encoding. That is crazy and cannot work.
> A workaround would be to set the Java file.encoding to UTF-8 but that is not what I want.
> There are two solutions:
> I think it is better to create a binary OutputStream instead of creating a FileWriter.
> The wsdlWriter offers two methods! The method with OutputStream argument would always write XML files using a UTF-8 encoding.
> An other way to fix that would be a bug fix to WSDL4J 1.6.3.
> The WSDL4J method com.ibm.wsdl.xml.WSDLWriterImpl.writeWSDL(Definition wsdlDef, Writer sink) does map default Java file.encoding to "UTF-8". That is sometimes wrong.
> The class com.ibm.wsdl.util.xml.DOM2Writer should have an XmlEncodingMapping from "Cp1252" to "Windows-1252". That would fix the problem also. But I think it would be better to use always UTF-8 with the OutputStream method.
> Best regards
> Martin Both
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month
[JBoss JIRA] (JBWS-3957) publishWsdlImports writes WSDL-XML files with wrong characterset under Windows
by Alessio Soldano (JIRA)
[ https://issues.jboss.org/browse/JBWS-3957?page=com.atlassian.jira.plugin.... ]
Alessio Soldano updated JBWS-3957:
----------------------------------
Assignee: Alessio Soldano
> publishWsdlImports writes WSDL-XML files with wrong characterset under Windows
> ------------------------------------------------------------------------------
>
> Key: JBWS-3957
> URL: https://issues.jboss.org/browse/JBWS-3957
> Project: JBoss Web Services
> Issue Type: Bug
> Environment: WildFly 9, Windows 7 with default Java file.encoding Cp1252.
> Reporter: Martin Both
> Assignee: Alessio Soldano
> Fix For: jbossws-cxf-5.2.0.Final
>
>
> I would like to deploy a WebService but I get an exception. The WSDL XSD file contains an german character 'ä'. See:
> Here is the part of the XSD:
> <xs:simpleType name="Teilnehmerart">
> <xs:restriction base="xs:string">
> <xs:enumeration value="Privat"></xs:enumeration>
> <xs:enumeration value="Geschäftlich"></xs:enumeration>
> </xs:restriction>
> </xs:simpleType>
> The JBoss class org.jboss.ws.common.utils.AbstractWSDLFilePublisher
> writes the imported WSDL file using a FileWriter at line 166 + 167.
> FileWriter fw = new FileWriter(targetFile);
> wsdlWriter.writeWSDL(subdef, fw);
> In a next step this file is read again and results in an exception:
> Invalid byte 2 of 3-byte UTF-8 sequence.
> This is because the file is written in Cp1252 enconding together with an XML prolog
> UTF-8 encoding. That is crazy and cannot work.
> A workaround would be to set the Java file.encoding to UTF-8 but that is not what I want.
> There are two solutions:
> I think it is better to create a binary OutputStream instead of creating a FileWriter.
> The wsdlWriter offers two methods! The method with OutputStream argument would always write XML files using a UTF-8 encoding.
> An other way to fix that would be a bug fix to WSDL4J 1.6.3.
> The WSDL4J method com.ibm.wsdl.xml.WSDLWriterImpl.writeWSDL(Definition wsdlDef, Writer sink) does map default Java file.encoding to "UTF-8". That is sometimes wrong.
> The class com.ibm.wsdl.util.xml.DOM2Writer should have an XmlEncodingMapping from "Cp1252" to "Windows-1252". That would fix the problem also. But I think it would be better to use always UTF-8 with the OutputStream method.
> Best regards
> Martin Both
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month
[JBoss JIRA] (JBWS-3957) publishWsdlImports writes WSDL-XML files with wrong characterset under Windows
by Alessio Soldano (JIRA)
[ https://issues.jboss.org/browse/JBWS-3957?page=com.atlassian.jira.plugin.... ]
Alessio Soldano updated JBWS-3957:
----------------------------------
Fix Version/s: jbossws-cxf-5.2.0.Final
> publishWsdlImports writes WSDL-XML files with wrong characterset under Windows
> ------------------------------------------------------------------------------
>
> Key: JBWS-3957
> URL: https://issues.jboss.org/browse/JBWS-3957
> Project: JBoss Web Services
> Issue Type: Bug
> Environment: WildFly 9, Windows 7 with default Java file.encoding Cp1252.
> Reporter: Martin Both
> Fix For: jbossws-cxf-5.2.0.Final
>
>
> I would like to deploy a WebService but I get an exception. The WSDL XSD file contains an german character 'ä'. See:
> Here is the part of the XSD:
> <xs:simpleType name="Teilnehmerart">
> <xs:restriction base="xs:string">
> <xs:enumeration value="Privat"></xs:enumeration>
> <xs:enumeration value="Geschäftlich"></xs:enumeration>
> </xs:restriction>
> </xs:simpleType>
> The JBoss class org.jboss.ws.common.utils.AbstractWSDLFilePublisher
> writes the imported WSDL file using a FileWriter at line 166 + 167.
> FileWriter fw = new FileWriter(targetFile);
> wsdlWriter.writeWSDL(subdef, fw);
> In a next step this file is read again and results in an exception:
> Invalid byte 2 of 3-byte UTF-8 sequence.
> This is because the file is written in Cp1252 enconding together with an XML prolog
> UTF-8 encoding. That is crazy and cannot work.
> A workaround would be to set the Java file.encoding to UTF-8 but that is not what I want.
> There are two solutions:
> I think it is better to create a binary OutputStream instead of creating a FileWriter.
> The wsdlWriter offers two methods! The method with OutputStream argument would always write XML files using a UTF-8 encoding.
> An other way to fix that would be a bug fix to WSDL4J 1.6.3.
> The WSDL4J method com.ibm.wsdl.xml.WSDLWriterImpl.writeWSDL(Definition wsdlDef, Writer sink) does map default Java file.encoding to "UTF-8". That is sometimes wrong.
> The class com.ibm.wsdl.util.xml.DOM2Writer should have an XmlEncodingMapping from "Cp1252" to "Windows-1252". That would fix the problem also. But I think it would be better to use always UTF-8 with the OutputStream method.
> Best regards
> Martin Both
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month
[JBoss JIRA] (JBWS-3957) publishWsdlImports writes WSDL-XML files with wrong characterset under Windows
by Martin Both (JIRA)
Martin Both created JBWS-3957:
---------------------------------
Summary: publishWsdlImports writes WSDL-XML files with wrong characterset under Windows
Key: JBWS-3957
URL: https://issues.jboss.org/browse/JBWS-3957
Project: JBoss Web Services
Issue Type: Bug
Environment: WildFly 9, Windows 7 with default Java file.encoding Cp1252.
Reporter: Martin Both
I would like to deploy a WebService but I get an exception. The WSDL XSD file contains an german character 'ä'. See:
Here is the part of the XSD:
<xs:simpleType name="Teilnehmerart">
<xs:restriction base="xs:string">
<xs:enumeration value="Privat"></xs:enumeration>
<xs:enumeration value="Geschäftlich"></xs:enumeration>
</xs:restriction>
</xs:simpleType>
The JBoss class org.jboss.ws.common.utils.AbstractWSDLFilePublisher
writes the imported WSDL file using a FileWriter at line 166 + 167.
FileWriter fw = new FileWriter(targetFile);
wsdlWriter.writeWSDL(subdef, fw);
In a next step this file is read again and results in an exception:
Invalid byte 2 of 3-byte UTF-8 sequence.
This is because the file is written in Cp1252 enconding together with an XML prolog
UTF-8 encoding. That is crazy and cannot work.
A workaround would be to set the Java file.encoding to UTF-8 but that is not what I want.
There are two solutions:
I think it is better to create a binary OutputStream instead of creating a FileWriter.
The wsdlWriter offers two methods! The method with OutputStream argument would always write XML files using a UTF-8 encoding.
An other way to fix that would be a bug fix to WSDL4J 1.6.3.
The WSDL4J method com.ibm.wsdl.xml.WSDLWriterImpl.writeWSDL(Definition wsdlDef, Writer sink) does map default Java file.encoding to "UTF-8". That is sometimes wrong.
The class com.ibm.wsdl.util.xml.DOM2Writer should have an XmlEncodingMapping from "Cp1252" to "Windows-1252". That would fix the problem also. But I think it would be better to use always UTF-8 with the OutputStream method.
Best regards
Martin Both
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month
[JBoss JIRA] (JBWS-3956) Random webservice deployment failure on windows
by Jan Blizňák (JIRA)
[ https://issues.jboss.org/browse/JBWS-3956?page=com.atlassian.jira.plugin.... ]
Jan Blizňák commented on JBWS-3956:
-----------------------------------
[~asoldano],I have assigned this to you as this was hit during webservices testing, but given the stacktrace I am not quite sure if it is the right component to blame...
> Random webservice deployment failure on windows
> -----------------------------------------------
>
> Key: JBWS-3956
> URL: https://issues.jboss.org/browse/JBWS-3956
> Project: JBoss Web Services
> Issue Type: Bug
> Components: jbossws-cxf
> Reporter: Jan Blizňák
> Assignee: Alessio Soldano
> Attachments: jaxws-samples-wsrm-store.war
>
>
> When you try to deploy deployment with webservices and with -ds.xml (not sure if it is relevant) it from time to time cause a failure like this:
> {code:java}
> 14:42:05,312 WARN [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.jaxws-samples-wsrm-store.war" is using a private module ("org.apache.cxf.impl:main") which may be changed or removed in future versions without notice.
> 14:42:05,347 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-4) JBWS024061: Adding service endpoint metadata: id=SimpleService
> address=http://[::1]:8080/jaxws-samples-wsrm-store
> implementor=org.jboss.test.ws.jaxws.samples.wsrm.store.EndpointImpl
> serviceName={http://www.jboss.org/jbossws/ws-extensions/wsrm}RMService
> portName={http://www.jboss.org/jbossws/ws-extensions/wsrm}RMEndpointPort
> annotationWsdlLocation=null
> wsdlLocationOverride=null
> mtomEnabled=false
> 14:42:05,355 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-4) Creating Service {http://www.jboss.org/jbossws/ws-extensions/wsrm}RMService from class org.jboss.test.ws.jaxws.samples.wsrm.store.Endpoint
> 14:42:05,371 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-4) Setting the server's publish address to be http://[::1]:8080/jaxws-samples-wsrm-store
> 14:42:05,381 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."jaxws-samples-wsrm-store.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."jaxws-samples-wsrm-store.war".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of deployment "jaxws-samples-wsrm-store.war"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.NoClassDefFoundError: org/jboss/ws/common/Loggers
> at org.jboss.test.ws.jaxws.samples.wsrm.store.RMStoreFeature.initializeProvider(RMStoreFeature.java:85)
> at org.apache.cxf.feature.AbstractFeature.initialize(AbstractFeature.java:45)
> at org.apache.cxf.frontend.ServerFactoryBean.applyFeatures(ServerFactoryBean.java:249)
> at org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.java:211)
> at org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(JaxWsServerFactoryBean.java:211)
> at org.apache.cxf.jaxws.EndpointImpl.getServer(EndpointImpl.java:460)
> at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:338)
> at org.jboss.wsf.stack.cxf.deployment.EndpointImpl.doPublish(EndpointImpl.java:79)
> at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:255)
> at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:543)
> at org.jboss.wsf.stack.cxf.configuration.BusHolder.configure(BusHolder.java:231)
> at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.startDeploymentBus(BusDeploymentAspect.java:97)
> at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.start(BusDeploymentAspect.java:59)
> at org.jboss.as.webservices.deployers.AspectDeploymentProcessor.deploy(AspectDeploymentProcessor.java:73)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
> ... 5 more
> Caused by: java.lang.ClassNotFoundException: org.jboss.ws.common.Loggers from [Module "deployment.jaxws-samples-wsrm-store.war:main" from Service Module Loader]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:205)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:455)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:404)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:385)
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:130)
> ... 20 more
> 14:42:05,402 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0001: Bound data source [java:jboss/datasources/rmclientdb]
> 14:42:05,403 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:jboss/datasources/rmdb]
> 14:42:05,403 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 5) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "jaxws-samples-wsrm-store.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"jaxws-samples-wsrm-store.war\".INSTALL" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"jaxws-samples-wsrm-store.war\".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of deployment \"jaxws-samples-wsrm-store.war\"
> Caused by: java.lang.NoClassDefFoundError: org/jboss/ws/common/Loggers
> Caused by: java.lang.ClassNotFoundException: org.jboss.ws.common.Loggers from [Module \"deployment.jaxws-samples-wsrm-store.war:main\" from Service Module Loader]"}}
> 14:42:05,404 ERROR [org.jboss.as.server] (management-handler-thread - 5) WFLYSRV0021: Deploy of deployment "jaxws-samples-wsrm-store.war" was rolled back with the following failure message:
> {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"jaxws-samples-wsrm-store.war\".INSTALL" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"jaxws-samples-wsrm-store.war\".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of deployment \"jaxws-samples-wsrm-store.war\"
> Caused by: java.lang.NoClassDefFoundError: org/jboss/ws/common/Loggers
> Caused by: java.lang.ClassNotFoundException: org.jboss.ws.common.Loggers from [Module \"deployment.jaxws-samples-wsrm-store.war:main\" from Service Module Loader]"}}
> 14:42:05,423 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0010: Unbound data source [java:jboss/datasources/rmdb]
> 14:42:05,423 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0010: Unbound data source [java:jboss/datasources/rmclientdb]
> 14:42:05,427 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0028: Stopped deployment jaxws-samples-wsrm-store.war (runtime-name: jaxws-samples-wsrm-store.war) in 23ms
> 14:42:05,427 INFO [org.jboss.as.controller] (management-handler-thread - 5) WFLYCTL0183: Service status report
> WFLYCTL0186: Services which failed to start: service jboss.deployment.unit."jaxws-samples-wsrm-store.war".INSTALL
> {code}
> It might be cause by some sort of race condition because its intermittent nature, I was not able to narrow it down so far.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month
[JBoss JIRA] (JBWS-3956) Random webservice deployment failure on windows
by Jan Blizňák (JIRA)
[ https://issues.jboss.org/browse/JBWS-3956?page=com.atlassian.jira.plugin.... ]
Jan Blizňák updated JBWS-3956:
------------------------------
Project: JBoss Web Services (was: JBoss Enterprise Application Platform)
Key: JBWS-3956 (was: JBEAP-1433)
Workflow: classic default workflow (was: CDW v1)
Status: Open (was: New)
Component/s: jbossws-cxf
(was: Web Services)
Target Release: (was: 7.0.0.GA)
Affects Version/s: (was: 7.0.0.DR11)
> Random webservice deployment failure on windows
> -----------------------------------------------
>
> Key: JBWS-3956
> URL: https://issues.jboss.org/browse/JBWS-3956
> Project: JBoss Web Services
> Issue Type: Bug
> Components: jbossws-cxf
> Reporter: Jan Blizňák
> Assignee: Alessio Soldano
> Attachments: jaxws-samples-wsrm-store.war
>
>
> When you try to deploy deployment with webservices and with -ds.xml (not sure if it is relevant) it from time to time cause a failure like this:
> {code:java}
> 14:42:05,312 WARN [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.jaxws-samples-wsrm-store.war" is using a private module ("org.apache.cxf.impl:main") which may be changed or removed in future versions without notice.
> 14:42:05,347 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-4) JBWS024061: Adding service endpoint metadata: id=SimpleService
> address=http://[::1]:8080/jaxws-samples-wsrm-store
> implementor=org.jboss.test.ws.jaxws.samples.wsrm.store.EndpointImpl
> serviceName={http://www.jboss.org/jbossws/ws-extensions/wsrm}RMService
> portName={http://www.jboss.org/jbossws/ws-extensions/wsrm}RMEndpointPort
> annotationWsdlLocation=null
> wsdlLocationOverride=null
> mtomEnabled=false
> 14:42:05,355 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-4) Creating Service {http://www.jboss.org/jbossws/ws-extensions/wsrm}RMService from class org.jboss.test.ws.jaxws.samples.wsrm.store.Endpoint
> 14:42:05,371 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-4) Setting the server's publish address to be http://[::1]:8080/jaxws-samples-wsrm-store
> 14:42:05,381 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."jaxws-samples-wsrm-store.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."jaxws-samples-wsrm-store.war".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of deployment "jaxws-samples-wsrm-store.war"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.NoClassDefFoundError: org/jboss/ws/common/Loggers
> at org.jboss.test.ws.jaxws.samples.wsrm.store.RMStoreFeature.initializeProvider(RMStoreFeature.java:85)
> at org.apache.cxf.feature.AbstractFeature.initialize(AbstractFeature.java:45)
> at org.apache.cxf.frontend.ServerFactoryBean.applyFeatures(ServerFactoryBean.java:249)
> at org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.java:211)
> at org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(JaxWsServerFactoryBean.java:211)
> at org.apache.cxf.jaxws.EndpointImpl.getServer(EndpointImpl.java:460)
> at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:338)
> at org.jboss.wsf.stack.cxf.deployment.EndpointImpl.doPublish(EndpointImpl.java:79)
> at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:255)
> at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:543)
> at org.jboss.wsf.stack.cxf.configuration.BusHolder.configure(BusHolder.java:231)
> at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.startDeploymentBus(BusDeploymentAspect.java:97)
> at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.start(BusDeploymentAspect.java:59)
> at org.jboss.as.webservices.deployers.AspectDeploymentProcessor.deploy(AspectDeploymentProcessor.java:73)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
> ... 5 more
> Caused by: java.lang.ClassNotFoundException: org.jboss.ws.common.Loggers from [Module "deployment.jaxws-samples-wsrm-store.war:main" from Service Module Loader]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:205)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:455)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:404)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:385)
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:130)
> ... 20 more
> 14:42:05,402 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0001: Bound data source [java:jboss/datasources/rmclientdb]
> 14:42:05,403 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:jboss/datasources/rmdb]
> 14:42:05,403 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 5) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "jaxws-samples-wsrm-store.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"jaxws-samples-wsrm-store.war\".INSTALL" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"jaxws-samples-wsrm-store.war\".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of deployment \"jaxws-samples-wsrm-store.war\"
> Caused by: java.lang.NoClassDefFoundError: org/jboss/ws/common/Loggers
> Caused by: java.lang.ClassNotFoundException: org.jboss.ws.common.Loggers from [Module \"deployment.jaxws-samples-wsrm-store.war:main\" from Service Module Loader]"}}
> 14:42:05,404 ERROR [org.jboss.as.server] (management-handler-thread - 5) WFLYSRV0021: Deploy of deployment "jaxws-samples-wsrm-store.war" was rolled back with the following failure message:
> {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"jaxws-samples-wsrm-store.war\".INSTALL" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"jaxws-samples-wsrm-store.war\".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of deployment \"jaxws-samples-wsrm-store.war\"
> Caused by: java.lang.NoClassDefFoundError: org/jboss/ws/common/Loggers
> Caused by: java.lang.ClassNotFoundException: org.jboss.ws.common.Loggers from [Module \"deployment.jaxws-samples-wsrm-store.war:main\" from Service Module Loader]"}}
> 14:42:05,423 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0010: Unbound data source [java:jboss/datasources/rmdb]
> 14:42:05,423 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0010: Unbound data source [java:jboss/datasources/rmclientdb]
> 14:42:05,427 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0028: Stopped deployment jaxws-samples-wsrm-store.war (runtime-name: jaxws-samples-wsrm-store.war) in 23ms
> 14:42:05,427 INFO [org.jboss.as.controller] (management-handler-thread - 5) WFLYCTL0183: Service status report
> WFLYCTL0186: Services which failed to start: service jboss.deployment.unit."jaxws-samples-wsrm-store.war".INSTALL
> {code}
> It might be cause by some sort of race condition because its intermittent nature, I was not able to narrow it down so far.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month
[JBoss JIRA] (JBWS-3955) JBossWS testsuite failure on Windows - CreateProcess error=206, The filename or extension is too long
by Jan Blizňák (JIRA)
[ https://issues.jboss.org/browse/JBWS-3955?page=com.atlassian.jira.plugin.... ]
Jan Blizňák updated JBWS-3955:
------------------------------
Workaround Description: Run the testsuite as close to filesystem root as possible, eg. from /tmp, but it is not reliable and definitely a proper solution (was: Run the testsuite as close to filesystem root as possible, eg. from /tmp)
> JBossWS testsuite failure on Windows - CreateProcess error=206, The filename or extension is too long
> -----------------------------------------------------------------------------------------------------
>
> Key: JBWS-3955
> URL: https://issues.jboss.org/browse/JBWS-3955
> Project: JBoss Web Services
> Issue Type: Bug
> Components: jbossws-cxf
> Environment: Windows
> Reporter: Jan Blizňák
> Assignee: Alessio Soldano
>
> When running whole jbossws-cxf testsuite on windows node, it fails on executing ant task because of long classpath.
> {code:java}
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.7:run (wsconsume) on project jbossws-cxf-shared-tests: An Ant BuildException has occured: The following error occurred while executing this line:
> [ERROR] W:\workspace\eap-7x-jbossws-testsuite-windows\59544db6\build\stack-cxf\modules\testsuite\shared-tests\scripts\antrun-wsconsume.xml:41: The following error occurred while executing this line:
> [ERROR] W:\workspace\eap-7x-jbossws-testsuite-windows\59544db6\build\stack-cxf\modules\testsuite\shared-tests\scripts\antrun-wsconsume.xml:72: java.io.IOException: Cannot run program "W:\workspace\eap-7x-jbossws-testsuite-windows\59544db6\jdk1.8.0.unlimited.BC\jre\bin\java.exe": CreateProcess error=206, The filename or extension is too long
> [ERROR] around Ant part ...<ant antfile="scripts/antrun-wsconsume.xml" target="wsconsume"/>... @ 10:67 in W:\workspace\eap-7x-jbossws-testsuite-windows\59544db6\build\stack-cxf\modules\testsuite\shared-tests\target\antrun\build-main.xml
> [ERROR] -> [Help 1]
> {code}
> Incorporating this [task|https://ant.apache.org/manual/Tasks/manifestclasspath.html] in ant script might be a way how to workaround this issue.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month
[JBoss JIRA] (JBWS-3955) JBossWS testsuite failure on Windows - CreateProcess error=206, The filename or extension is too long
by Jan Blizňák (JIRA)
[ https://issues.jboss.org/browse/JBWS-3955?page=com.atlassian.jira.plugin.... ]
Jan Blizňák updated JBWS-3955:
------------------------------
Project: JBoss Web Services (was: JBoss Enterprise Application Platform)
Key: JBWS-3955 (was: JBEAP-1429)
Workflow: classic default workflow (was: CDW v1)
Status: Open (was: New)
Component/s: jbossws-cxf
(was: Web Services)
Target Release: (was: 7.0.0.GA)
Affects Version/s: (was: 7.0.0.DR11)
> JBossWS testsuite failure on Windows - CreateProcess error=206, The filename or extension is too long
> -----------------------------------------------------------------------------------------------------
>
> Key: JBWS-3955
> URL: https://issues.jboss.org/browse/JBWS-3955
> Project: JBoss Web Services
> Issue Type: Bug
> Components: jbossws-cxf
> Environment: Windows
> Reporter: Jan Blizňák
> Assignee: Alessio Soldano
>
> When running whole jbossws-cxf testsuite on windows node, it fails on executing ant task because of long classpath.
> {code:java}
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.7:run (wsconsume) on project jbossws-cxf-shared-tests: An Ant BuildException has occured: The following error occurred while executing this line:
> [ERROR] W:\workspace\eap-7x-jbossws-testsuite-windows\59544db6\build\stack-cxf\modules\testsuite\shared-tests\scripts\antrun-wsconsume.xml:41: The following error occurred while executing this line:
> [ERROR] W:\workspace\eap-7x-jbossws-testsuite-windows\59544db6\build\stack-cxf\modules\testsuite\shared-tests\scripts\antrun-wsconsume.xml:72: java.io.IOException: Cannot run program "W:\workspace\eap-7x-jbossws-testsuite-windows\59544db6\jdk1.8.0.unlimited.BC\jre\bin\java.exe": CreateProcess error=206, The filename or extension is too long
> [ERROR] around Ant part ...<ant antfile="scripts/antrun-wsconsume.xml" target="wsconsume"/>... @ 10:67 in W:\workspace\eap-7x-jbossws-testsuite-windows\59544db6\build\stack-cxf\modules\testsuite\shared-tests\target\antrun\build-main.xml
> [ERROR] -> [Help 1]
> {code}
> Incorporating this [task|https://ant.apache.org/manual/Tasks/manifestclasspath.html] in ant script might be a way how to workaround this issue.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month
[JBoss JIRA] (JBWS-3954) Upgrade to Apache CXF 3.1.4
by Alessio Soldano (JIRA)
Alessio Soldano created JBWS-3954:
-------------------------------------
Summary: Upgrade to Apache CXF 3.1.4
Key: JBWS-3954
URL: https://issues.jboss.org/browse/JBWS-3954
Project: JBoss Web Services
Issue Type: Feature Request
Components: jbossws-cxf
Reporter: Alessio Soldano
Assignee: Alessio Soldano
Fix For: jbossws-cxf-5.2.0.Final
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month