[JBoss JIRA] (WFLY-10757) ParseError when deploying application with netty dependency
by Jan Kašík (JIRA)
[ https://issues.jboss.org/browse/WFLY-10757?page=com.atlassian.jira.plugin... ]
Jan Kašík updated WFLY-10757:
-----------------------------
Description:
It is not possible to deploy app which has {{org.jboss.netty}} packed as a dependency. During processing of {{jboss-beans.xml}}, the deployment fails because there is an unexpected element: {{\{urn:jboss:bean-deployer:2.0}deployment}}.
{code:title=Part of log including exception|borderStyle=solid}
2018-07-30 05:57:16.701 DEBUG o.w.e.c.c.o.OnlineManagementClient: Executing CLI operation undeploy *metamer*
05:57:20,757 INFO [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location /home/hudson/hudson_workspace/workspace/eap-7.x-jsf-richfaces/6b4879d7/wildfly-14.0.0.Beta2-SNAPSHOT/standalone/data/content/c1/ef588d063c7cd396e765ef8452fbc43c04ce75/content
05:57:20,779 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "metamer.war" (runtime-name: "metamer.war")
05:57:22,206 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.deployment.unit."metamer.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."metamer.war".PARSE: WFLYSRV0153: Failed to process phase PARSE of deployment "metamer.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:151)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1736)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1698)
at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
at java.lang.Thread.run(Thread.java:748)
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYPOJO0038: Exception while parsing POJO descriptor file: "/content/metamer.war/WEB-INF/lib/netty-3.2.10.Final.jar/META-INF/jboss-beans.xml"
at org.jboss.as.pojo.KernelDeploymentParsingProcessor.parseDescriptor(KernelDeploymentParsingProcessor.java:154)
at org.jboss.as.pojo.KernelDeploymentParsingProcessor.parseDescriptors(KernelDeploymentParsingProcessor.java:125)
at org.jboss.as.pojo.KernelDeploymentParsingProcessor.deploy(KernelDeploymentParsingProcessor.java:82)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:144)
... 8 more
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[17,1]
Message: Unexpected element '{urn:jboss:bean-deployer:2.0}deployment'
at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:120)
at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:76)
at org.jboss.as.pojo.KernelDeploymentParsingProcessor.parseDescriptor(KernelDeploymentParsingProcessor.java:145)
... 11 more
05:57:22,210 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "metamer.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"metamer.war\".PARSE" => "WFLYSRV0153: Failed to process phase PARSE of deployment \"metamer.war\"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYPOJO0038: Exception while parsing POJO descriptor file: \"/content/metamer.war/WEB-INF/lib/netty-3.2.10.Final.jar/META-INF/jboss-beans.xml\"
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[17,1]
Message: Unexpected element '{urn:jboss:bean-deployer:2.0}deployment'"}}
05:57:22,217 ERROR [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0021: Deploy of deployment "metamer.war" was rolled back with the following failure message:
{"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"metamer.war\".PARSE" => "WFLYSRV0153: Failed to process phase PARSE of deployment \"metamer.war\"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYPOJO0038: Exception while parsing POJO descriptor file: \"/content/metamer.war/WEB-INF/lib/netty-3.2.10.Final.jar/META-INF/jboss-beans.xml\"
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[17,1]
Message: Unexpected element '{urn:jboss:bean-deployer:2.0}deployment'"}}
05:57:22,266 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment metamer.war (runtime-name: metamer.war) in 47ms
{code}
was:
It is not possible to deploy app which has {{org.jboss.netty}} packed as a dependency. During processing of {{jboss-beans.xml}}, the deployment fails because there is an unexpected element: {{\{urn:jboss:bean-deployer:2.0}deployment}}. This worked with previous CI builds like {{wf-201807240026-5178340}}.
{code:title=Part of log including exception|borderStyle=solid}
2018-07-30 05:57:16.701 DEBUG o.w.e.c.c.o.OnlineManagementClient: Executing CLI operation undeploy *metamer*
05:57:20,757 INFO [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location /home/hudson/hudson_workspace/workspace/eap-7.x-jsf-richfaces/6b4879d7/wildfly-14.0.0.Beta2-SNAPSHOT/standalone/data/content/c1/ef588d063c7cd396e765ef8452fbc43c04ce75/content
05:57:20,779 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "metamer.war" (runtime-name: "metamer.war")
05:57:22,206 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.deployment.unit."metamer.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."metamer.war".PARSE: WFLYSRV0153: Failed to process phase PARSE of deployment "metamer.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:151)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1736)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1698)
at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
at java.lang.Thread.run(Thread.java:748)
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYPOJO0038: Exception while parsing POJO descriptor file: "/content/metamer.war/WEB-INF/lib/netty-3.2.10.Final.jar/META-INF/jboss-beans.xml"
at org.jboss.as.pojo.KernelDeploymentParsingProcessor.parseDescriptor(KernelDeploymentParsingProcessor.java:154)
at org.jboss.as.pojo.KernelDeploymentParsingProcessor.parseDescriptors(KernelDeploymentParsingProcessor.java:125)
at org.jboss.as.pojo.KernelDeploymentParsingProcessor.deploy(KernelDeploymentParsingProcessor.java:82)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:144)
... 8 more
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[17,1]
Message: Unexpected element '{urn:jboss:bean-deployer:2.0}deployment'
at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:120)
at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:76)
at org.jboss.as.pojo.KernelDeploymentParsingProcessor.parseDescriptor(KernelDeploymentParsingProcessor.java:145)
... 11 more
05:57:22,210 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "metamer.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"metamer.war\".PARSE" => "WFLYSRV0153: Failed to process phase PARSE of deployment \"metamer.war\"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYPOJO0038: Exception while parsing POJO descriptor file: \"/content/metamer.war/WEB-INF/lib/netty-3.2.10.Final.jar/META-INF/jboss-beans.xml\"
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[17,1]
Message: Unexpected element '{urn:jboss:bean-deployer:2.0}deployment'"}}
05:57:22,217 ERROR [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0021: Deploy of deployment "metamer.war" was rolled back with the following failure message:
{"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"metamer.war\".PARSE" => "WFLYSRV0153: Failed to process phase PARSE of deployment \"metamer.war\"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYPOJO0038: Exception while parsing POJO descriptor file: \"/content/metamer.war/WEB-INF/lib/netty-3.2.10.Final.jar/META-INF/jboss-beans.xml\"
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[17,1]
Message: Unexpected element '{urn:jboss:bean-deployer:2.0}deployment'"}}
05:57:22,266 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment metamer.war (runtime-name: metamer.war) in 47ms
{code}
> ParseError when deploying application with netty dependency
> ------------------------------------------------------------
>
> Key: WFLY-10757
> URL: https://issues.jboss.org/browse/WFLY-10757
> Project: WildFly
> Issue Type: Bug
> Components: Server, XML Frameworks
> Affects Versions: 14.0.0.CR1
> Reporter: Jan Kašík
> Assignee: Jason Greene
> Priority: Critical
>
> It is not possible to deploy app which has {{org.jboss.netty}} packed as a dependency. During processing of {{jboss-beans.xml}}, the deployment fails because there is an unexpected element: {{\{urn:jboss:bean-deployer:2.0}deployment}}.
> {code:title=Part of log including exception|borderStyle=solid}
> 2018-07-30 05:57:16.701 DEBUG o.w.e.c.c.o.OnlineManagementClient: Executing CLI operation undeploy *metamer*
> 05:57:20,757 INFO [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location /home/hudson/hudson_workspace/workspace/eap-7.x-jsf-richfaces/6b4879d7/wildfly-14.0.0.Beta2-SNAPSHOT/standalone/data/content/c1/ef588d063c7cd396e765ef8452fbc43c04ce75/content
> 05:57:20,779 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "metamer.war" (runtime-name: "metamer.war")
> 05:57:22,206 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.deployment.unit."metamer.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."metamer.war".PARSE: WFLYSRV0153: Failed to process phase PARSE of deployment "metamer.war"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:151)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1736)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1698)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYPOJO0038: Exception while parsing POJO descriptor file: "/content/metamer.war/WEB-INF/lib/netty-3.2.10.Final.jar/META-INF/jboss-beans.xml"
> at org.jboss.as.pojo.KernelDeploymentParsingProcessor.parseDescriptor(KernelDeploymentParsingProcessor.java:154)
> at org.jboss.as.pojo.KernelDeploymentParsingProcessor.parseDescriptors(KernelDeploymentParsingProcessor.java:125)
> at org.jboss.as.pojo.KernelDeploymentParsingProcessor.deploy(KernelDeploymentParsingProcessor.java:82)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:144)
> ... 8 more
> Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[17,1]
> Message: Unexpected element '{urn:jboss:bean-deployer:2.0}deployment'
> at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:120)
> at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:76)
> at org.jboss.as.pojo.KernelDeploymentParsingProcessor.parseDescriptor(KernelDeploymentParsingProcessor.java:145)
> ... 11 more
> 05:57:22,210 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "metamer.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"metamer.war\".PARSE" => "WFLYSRV0153: Failed to process phase PARSE of deployment \"metamer.war\"
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYPOJO0038: Exception while parsing POJO descriptor file: \"/content/metamer.war/WEB-INF/lib/netty-3.2.10.Final.jar/META-INF/jboss-beans.xml\"
> Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[17,1]
> Message: Unexpected element '{urn:jboss:bean-deployer:2.0}deployment'"}}
> 05:57:22,217 ERROR [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0021: Deploy of deployment "metamer.war" was rolled back with the following failure message:
> {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"metamer.war\".PARSE" => "WFLYSRV0153: Failed to process phase PARSE of deployment \"metamer.war\"
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYPOJO0038: Exception while parsing POJO descriptor file: \"/content/metamer.war/WEB-INF/lib/netty-3.2.10.Final.jar/META-INF/jboss-beans.xml\"
> Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[17,1]
> Message: Unexpected element '{urn:jboss:bean-deployer:2.0}deployment'"}}
> 05:57:22,266 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment metamer.war (runtime-name: metamer.war) in 47ms
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (WFLY-10757) ParseError when deploying application with netty dependency
by Jan Kašík (JIRA)
[ https://issues.jboss.org/browse/WFLY-10757?page=com.atlassian.jira.plugin... ]
Jan Kašík updated WFLY-10757:
-----------------------------
Environment: (was: CI build of Wildfly: wf-201807260026-c80c2b1 and later)
> ParseError when deploying application with netty dependency
> ------------------------------------------------------------
>
> Key: WFLY-10757
> URL: https://issues.jboss.org/browse/WFLY-10757
> Project: WildFly
> Issue Type: Bug
> Components: Server, XML Frameworks
> Affects Versions: 14.0.0.CR1
> Reporter: Jan Kašík
> Assignee: Jason Greene
> Priority: Critical
>
> It is not possible to deploy app which has {{org.jboss.netty}} packed as a dependency. During processing of {{jboss-beans.xml}}, the deployment fails because there is an unexpected element: {{\{urn:jboss:bean-deployer:2.0}deployment}}. This worked with previous CI builds like {{wf-201807240026-5178340}}.
> {code:title=Part of log including exception|borderStyle=solid}
> 2018-07-30 05:57:16.701 DEBUG o.w.e.c.c.o.OnlineManagementClient: Executing CLI operation undeploy *metamer*
> 05:57:20,757 INFO [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location /home/hudson/hudson_workspace/workspace/eap-7.x-jsf-richfaces/6b4879d7/wildfly-14.0.0.Beta2-SNAPSHOT/standalone/data/content/c1/ef588d063c7cd396e765ef8452fbc43c04ce75/content
> 05:57:20,779 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "metamer.war" (runtime-name: "metamer.war")
> 05:57:22,206 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.deployment.unit."metamer.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."metamer.war".PARSE: WFLYSRV0153: Failed to process phase PARSE of deployment "metamer.war"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:151)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1736)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1698)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYPOJO0038: Exception while parsing POJO descriptor file: "/content/metamer.war/WEB-INF/lib/netty-3.2.10.Final.jar/META-INF/jboss-beans.xml"
> at org.jboss.as.pojo.KernelDeploymentParsingProcessor.parseDescriptor(KernelDeploymentParsingProcessor.java:154)
> at org.jboss.as.pojo.KernelDeploymentParsingProcessor.parseDescriptors(KernelDeploymentParsingProcessor.java:125)
> at org.jboss.as.pojo.KernelDeploymentParsingProcessor.deploy(KernelDeploymentParsingProcessor.java:82)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:144)
> ... 8 more
> Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[17,1]
> Message: Unexpected element '{urn:jboss:bean-deployer:2.0}deployment'
> at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:120)
> at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:76)
> at org.jboss.as.pojo.KernelDeploymentParsingProcessor.parseDescriptor(KernelDeploymentParsingProcessor.java:145)
> ... 11 more
> 05:57:22,210 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "metamer.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"metamer.war\".PARSE" => "WFLYSRV0153: Failed to process phase PARSE of deployment \"metamer.war\"
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYPOJO0038: Exception while parsing POJO descriptor file: \"/content/metamer.war/WEB-INF/lib/netty-3.2.10.Final.jar/META-INF/jboss-beans.xml\"
> Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[17,1]
> Message: Unexpected element '{urn:jboss:bean-deployer:2.0}deployment'"}}
> 05:57:22,217 ERROR [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0021: Deploy of deployment "metamer.war" was rolled back with the following failure message:
> {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"metamer.war\".PARSE" => "WFLYSRV0153: Failed to process phase PARSE of deployment \"metamer.war\"
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYPOJO0038: Exception while parsing POJO descriptor file: \"/content/metamer.war/WEB-INF/lib/netty-3.2.10.Final.jar/META-INF/jboss-beans.xml\"
> Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[17,1]
> Message: Unexpected element '{urn:jboss:bean-deployer:2.0}deployment'"}}
> 05:57:22,266 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment metamer.war (runtime-name: metamer.war) in 47ms
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (WFLY-10630) HttpSessionListener.sessionDestroyed() not called if session invalidated in another WAR
by Bernhard Kabelka (JIRA)
[ https://issues.jboss.org/browse/WFLY-10630?page=com.atlassian.jira.plugin... ]
Bernhard Kabelka commented on WFLY-10630:
-----------------------------------------
I have used the following security-domain
{code:xml}
<security-domain name="sessionlistener">
<authentication>
<login-module code="org.jboss.security.auth.spi.UsersRolesLoginModule" flag="required">
<module-option name="usersProperties" value="[PATH_TO_users.properties_FILE]"/>
<module-option name="rolesProperties" value="[PATH_TO_roles.properties_FILE]"/>
</login-module>
</authentication>
</security-domain>
{code}
with the user.properties file like
{noformat}
USERNAME=PASSWORD
{noformat}
and the roles.properties file like
{noformat}
USERNAME=WHATEVER
{noformat}
I am not sure which code you are using for testing, and to which URL you are trying to connect when you get the error message you posted. However, if you are using the sample code I provided (see "Steps to Reproduce"), and connect to http://[SERVER]:[PORT]/sessionlistener/test (in your browser, i.e. via HTTP GET) you should get a login page displayed.
> HttpSessionListener.sessionDestroyed() not called if session invalidated in another WAR
> ---------------------------------------------------------------------------------------
>
> Key: WFLY-10630
> URL: https://issues.jboss.org/browse/WFLY-10630
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 10.0.0.Final, 13.0.0.Final
> Environment: Windows 10, Java 1.8.0_131
> Reproducible with both WildFly-10.0.0.Final and Wildfly-13.0.0.Final
> Reporter: Bernhard Kabelka
> Assignee: Bartosz Baranowski
>
> For sessions shared across different WARs in a single EAR, the notification of HttpSessionListener works differently in WildFly 10.0.0.Final (and Wildfly 13.0.0.Final) than it it used to work in WildFly 8.2.0.Final:
> I have an EAR containing two WARs with enabled session sharing across the WARs. Basically, one WAR contains the web UI, and the other WAR contains the REST interfaces for AJAX calls made by the UI. The user authenticates against the UI-WAR. On logout, a REST method in the AJAX-WAR is triggered which calls HttpSession.invalidate() on the user session.
> In WildFly 8.2.0.Final, a HttpSessionListener in the UI-WAR gets notified immediately about session creation and destruction.
> In WildFly 13.0.0.Final, however, a HttpSessionListener in either WAR only gets one of the two notifications:
> * In the UI-WAR, I get a notification about the created session immediately when the login form is loaded. However, I do not receive any notification about the session destruction (unless it times out).
> * In the AJAX-WAR, I do not get any notification about the session creation at all, but I immediately receive a notification about the session destruction.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (WFLY-10630) HttpSessionListener.sessionDestroyed() not called if session invalidated in another WAR
by Bartosz Baranowski (JIRA)
[ https://issues.jboss.org/browse/WFLY-10630?page=com.atlassian.jira.plugin... ]
Bartosz Baranowski commented on WFLY-10630:
-------------------------------------------
[~bkabelka] Yeah, this wont cut it:
{quote}
HTTP ERROR 405
{quote}
{quote}
10:09:28,362 ERROR [org.jboss.resteasy.resteasy_jaxrs.i18n] (default task-1) RESTEASY002010: Failed to execute: javax.ws.rs.NotAllowedException: RESTEASY003650: No resource method found for POST, return 405 with Allow header
at org.jboss.resteasy.core.registry.SegmentNode.match(SegmentNode.java:455)
at org.jboss.resteasy.core.registry.SegmentNode.match(SegmentNode.java:141)
{quote}
Ive set up domain like:
{quote}
<subsystem xmlns="urn:jboss:domain:security:2.0">
<security-domains>
....
<security-domain name="sessionlistener">
<authentication>
<login-module code="UsersRoles" flag="required">
<module-option name="usersProperties" value="file://${jboss.server.config.dir}/application-users.properties"/>
<module-option name="rolesProperties" value="file://${jboss.server.config.dir}/application-roles.properties"/>
</login-module>
</authentication>
</security-domain>
</security-domains>
</subsystem>
{quote}
> HttpSessionListener.sessionDestroyed() not called if session invalidated in another WAR
> ---------------------------------------------------------------------------------------
>
> Key: WFLY-10630
> URL: https://issues.jboss.org/browse/WFLY-10630
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 10.0.0.Final, 13.0.0.Final
> Environment: Windows 10, Java 1.8.0_131
> Reproducible with both WildFly-10.0.0.Final and Wildfly-13.0.0.Final
> Reporter: Bernhard Kabelka
> Assignee: Bartosz Baranowski
>
> For sessions shared across different WARs in a single EAR, the notification of HttpSessionListener works differently in WildFly 10.0.0.Final (and Wildfly 13.0.0.Final) than it it used to work in WildFly 8.2.0.Final:
> I have an EAR containing two WARs with enabled session sharing across the WARs. Basically, one WAR contains the web UI, and the other WAR contains the REST interfaces for AJAX calls made by the UI. The user authenticates against the UI-WAR. On logout, a REST method in the AJAX-WAR is triggered which calls HttpSession.invalidate() on the user session.
> In WildFly 8.2.0.Final, a HttpSessionListener in the UI-WAR gets notified immediately about session creation and destruction.
> In WildFly 13.0.0.Final, however, a HttpSessionListener in either WAR only gets one of the two notifications:
> * In the UI-WAR, I get a notification about the created session immediately when the login form is loaded. However, I do not receive any notification about the session destruction (unless it times out).
> * In the AJAX-WAR, I do not get any notification about the session creation at all, but I immediately receive a notification about the session destruction.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (WFLY-10747) IOException when using JSF in deployment
by Adam Krajcik (JIRA)
[ https://issues.jboss.org/browse/WFLY-10747?page=com.atlassian.jira.plugin... ]
Adam Krajcik commented on WFLY-10747:
-------------------------------------
[~fjuma] Yes, the exception still happens.
> IOException when using JSF in deployment
> ----------------------------------------
>
> Key: WFLY-10747
> URL: https://issues.jboss.org/browse/WFLY-10747
> Project: WildFly
> Issue Type: Bug
> Components: JSF, Web (Undertow)
> Affects Versions: 10.1.0.Final, 11.0.0.Final, 12.0.0.Final, 13.0.0.Final
> Reporter: Adam Krajcik
> Assignee: Farah Juma
> Attachments: deployment.war
>
>
> When using JSF in attached [^deployment.war], I can see the following error. This error happens during the first request. Sever doesn't print this error on further requests.
> {code}
> 14:08:31,401 SEVERE [facelets.compiler] (default task-1) Error Loading Library: jar:file:/tmp/jboss-eap-7.2/modules/system/layers/base/com/sun/jsf-impl/main/jsf-impl-2.2.13.SP5-redhat-1.jar!/META-INF/mojarra_ext.taglib.xml: java.io.IOException: Error parsing [jar:file:/tmp/jboss-eap-7.2/modules/system/layers/base/com/sun/jsf-impl/main/jsf-impl-2.2.13.SP5-redhat-1.jar!/META-INF/mojarra_ext.taglib.xml]:
> at com.sun.facelets.compiler.TagLibraryConfig.create(TagLibraryConfig.java:410)
> at com.sun.facelets.compiler.TagLibraryConfig.loadImplicit(TagLibraryConfig.java:431)
> at com.sun.facelets.compiler.Compiler.initialize(Compiler.java:87)
> at com.sun.facelets.compiler.Compiler.compile(Compiler.java:104)
> at com.sun.facelets.impl.DefaultFaceletFactory.createFacelet(DefaultFaceletFactory.java:218)
> at com.sun.facelets.impl.DefaultFaceletFactory.getFacelet(DefaultFaceletFactory.java:149)
> at com.sun.facelets.impl.DefaultFaceletFactory.getFacelet(DefaultFaceletFactory.java:100)
> at com.sun.facelets.FaceletViewHandler.buildView(FaceletViewHandler.java:519)
> at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:569)
> at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120)
> at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
> at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:219)
> at javax.faces.webapp.FacesServlet.service(FacesServlet.java:659)
> at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:74)
> at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62)
> at io.undertow.servlet.handlers.ServletChain$1.handleRequest(ServletChain.java:68)
> at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36)
> at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:132)
> at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46)
> at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64)
> at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60)
> at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77)
> at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50)
> at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at org.wildfly.extension.undertow.deployment.GlobalRequestControllerHandler.handleRequest(GlobalRequestControllerHandler.java:68)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:292)
> at io.undertow.servlet.handlers.ServletInitialHandler.access$100(ServletInitialHandler.java:81)
> at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:138)
> at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:135)
> at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:48)
> at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
> at org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1514)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1514)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1514)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1514)
> at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:272)
> at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81)
> at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:104)
> at io.undertow.server.Connectors.executeRootHandler(Connectors.java:360)
> at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:830)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1349)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: org.xml.sax.SAXException: Error Handling [jar:file:/tmp/jboss-eap-7.2/modules/system/layers/base/com/sun/jsf-impl/main/jsf-impl-2.2.13.SP5-redhat-1.jar!/META-INF/mojarra_ext.taglib.xml@47,31]
> at com.sun.facelets.compiler.TagLibraryConfig$LibraryHandler.error(TagLibraryConfig.java:376)
> at org.apache.xerces.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:135)
> at org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:394)
> at org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:325)
> at org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:282)
> at org.apache.xerces.impl.dtd.XMLDTDValidator.rootElementSpecified(XMLDTDValidator.java:1644)
> at org.apache.xerces.impl.dtd.XMLDTDValidator.handleStartElement(XMLDTDValidator.java:1922)
> at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(XMLDTDValidator.java:787)
> at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:827)
> at org.apache.xerces.impl.XMLDocumentScannerImpl$ContentDispatcher.scanRootElementHook(XMLDocumentScannerImpl.java:1141)
> at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1754)
> at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:324)
> at org.apache.xerces.parsers.XML11Configuration.parse(XML11Configuration.java:875)
> at org.apache.xerces.parsers.XML11Configuration.parse(XML11Configuration.java:798)
> at org.apache.xerces.parsers.XMLParser.parse(XMLParser.java:108)
> at org.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1198)
> at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:564)
> at org.apache.xerces.jaxp.SAXParserImpl.parse(SAXParserImpl.java:298)
> at javax.xml.parsers.SAXParser.parse(SAXParser.java:195)
> at com.sun.facelets.compiler.TagLibraryConfig.create(TagLibraryConfig.java:407)
> ... 53 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (WFLY-10757) ParseError when deploying application with netty dependency
by Jan Kašík (JIRA)
[ https://issues.jboss.org/browse/WFLY-10757?page=com.atlassian.jira.plugin... ]
Jan Kašík updated WFLY-10757:
-----------------------------
Description:
It is not possible to deploy app which has {{org.jboss.netty}} packed as a dependency. During processing of {{jboss-beans.xml}}, the deployment fails because there is an unexpected element: {{\{urn:jboss:bean-deployer:2.0}deployment}}. This worked with previous CI builds like {{wf-201807240026-5178340}}.
{code:title=Part of log including exception|borderStyle=solid}
2018-07-30 05:57:16.701 DEBUG o.w.e.c.c.o.OnlineManagementClient: Executing CLI operation undeploy *metamer*
05:57:20,757 INFO [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location /home/hudson/hudson_workspace/workspace/eap-7.x-jsf-richfaces/6b4879d7/wildfly-14.0.0.Beta2-SNAPSHOT/standalone/data/content/c1/ef588d063c7cd396e765ef8452fbc43c04ce75/content
05:57:20,779 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "metamer.war" (runtime-name: "metamer.war")
05:57:22,206 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.deployment.unit."metamer.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."metamer.war".PARSE: WFLYSRV0153: Failed to process phase PARSE of deployment "metamer.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:151)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1736)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1698)
at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
at java.lang.Thread.run(Thread.java:748)
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYPOJO0038: Exception while parsing POJO descriptor file: "/content/metamer.war/WEB-INF/lib/netty-3.2.10.Final.jar/META-INF/jboss-beans.xml"
at org.jboss.as.pojo.KernelDeploymentParsingProcessor.parseDescriptor(KernelDeploymentParsingProcessor.java:154)
at org.jboss.as.pojo.KernelDeploymentParsingProcessor.parseDescriptors(KernelDeploymentParsingProcessor.java:125)
at org.jboss.as.pojo.KernelDeploymentParsingProcessor.deploy(KernelDeploymentParsingProcessor.java:82)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:144)
... 8 more
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[17,1]
Message: Unexpected element '{urn:jboss:bean-deployer:2.0}deployment'
at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:120)
at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:76)
at org.jboss.as.pojo.KernelDeploymentParsingProcessor.parseDescriptor(KernelDeploymentParsingProcessor.java:145)
... 11 more
05:57:22,210 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "metamer.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"metamer.war\".PARSE" => "WFLYSRV0153: Failed to process phase PARSE of deployment \"metamer.war\"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYPOJO0038: Exception while parsing POJO descriptor file: \"/content/metamer.war/WEB-INF/lib/netty-3.2.10.Final.jar/META-INF/jboss-beans.xml\"
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[17,1]
Message: Unexpected element '{urn:jboss:bean-deployer:2.0}deployment'"}}
05:57:22,217 ERROR [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0021: Deploy of deployment "metamer.war" was rolled back with the following failure message:
{"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"metamer.war\".PARSE" => "WFLYSRV0153: Failed to process phase PARSE of deployment \"metamer.war\"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYPOJO0038: Exception while parsing POJO descriptor file: \"/content/metamer.war/WEB-INF/lib/netty-3.2.10.Final.jar/META-INF/jboss-beans.xml\"
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[17,1]
Message: Unexpected element '{urn:jboss:bean-deployer:2.0}deployment'"}}
05:57:22,266 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment metamer.war (runtime-name: metamer.war) in 47ms
{code}
was:
It is not possible to deploy app which has {{org.jboss.netty}} packed as a dependency. During processing of {{jboss-beans.xml}}, the deployment fails because there is an unexpected element: {{\{urn:jboss:bean-deployer:2.0}deployment}}.
{code:title=Part of log including exception|borderStyle=solid}
2018-07-30 05:57:16.701 DEBUG o.w.e.c.c.o.OnlineManagementClient: Executing CLI operation undeploy *metamer*
05:57:20,757 INFO [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location /home/hudson/hudson_workspace/workspace/eap-7.x-jsf-richfaces/6b4879d7/wildfly-14.0.0.Beta2-SNAPSHOT/standalone/data/content/c1/ef588d063c7cd396e765ef8452fbc43c04ce75/content
05:57:20,779 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "metamer.war" (runtime-name: "metamer.war")
05:57:22,206 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.deployment.unit."metamer.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."metamer.war".PARSE: WFLYSRV0153: Failed to process phase PARSE of deployment "metamer.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:151)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1736)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1698)
at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
at java.lang.Thread.run(Thread.java:748)
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYPOJO0038: Exception while parsing POJO descriptor file: "/content/metamer.war/WEB-INF/lib/netty-3.2.10.Final.jar/META-INF/jboss-beans.xml"
at org.jboss.as.pojo.KernelDeploymentParsingProcessor.parseDescriptor(KernelDeploymentParsingProcessor.java:154)
at org.jboss.as.pojo.KernelDeploymentParsingProcessor.parseDescriptors(KernelDeploymentParsingProcessor.java:125)
at org.jboss.as.pojo.KernelDeploymentParsingProcessor.deploy(KernelDeploymentParsingProcessor.java:82)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:144)
... 8 more
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[17,1]
Message: Unexpected element '{urn:jboss:bean-deployer:2.0}deployment'
at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:120)
at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:76)
at org.jboss.as.pojo.KernelDeploymentParsingProcessor.parseDescriptor(KernelDeploymentParsingProcessor.java:145)
... 11 more
05:57:22,210 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "metamer.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"metamer.war\".PARSE" => "WFLYSRV0153: Failed to process phase PARSE of deployment \"metamer.war\"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYPOJO0038: Exception while parsing POJO descriptor file: \"/content/metamer.war/WEB-INF/lib/netty-3.2.10.Final.jar/META-INF/jboss-beans.xml\"
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[17,1]
Message: Unexpected element '{urn:jboss:bean-deployer:2.0}deployment'"}}
05:57:22,217 ERROR [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0021: Deploy of deployment "metamer.war" was rolled back with the following failure message:
{"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"metamer.war\".PARSE" => "WFLYSRV0153: Failed to process phase PARSE of deployment \"metamer.war\"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYPOJO0038: Exception while parsing POJO descriptor file: \"/content/metamer.war/WEB-INF/lib/netty-3.2.10.Final.jar/META-INF/jboss-beans.xml\"
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[17,1]
Message: Unexpected element '{urn:jboss:bean-deployer:2.0}deployment'"}}
05:57:22,266 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment metamer.war (runtime-name: metamer.war) in 47ms
{code}
> ParseError when deploying application with netty dependency
> ------------------------------------------------------------
>
> Key: WFLY-10757
> URL: https://issues.jboss.org/browse/WFLY-10757
> Project: WildFly
> Issue Type: Bug
> Components: Server, XML Frameworks
> Affects Versions: 14.0.0.CR1
> Environment: CI build of Wildfly: wf-201807280026-7f1d8dc
> Reporter: Jan Kašík
> Assignee: Jason Greene
> Priority: Critical
>
> It is not possible to deploy app which has {{org.jboss.netty}} packed as a dependency. During processing of {{jboss-beans.xml}}, the deployment fails because there is an unexpected element: {{\{urn:jboss:bean-deployer:2.0}deployment}}. This worked with previous CI builds like {{wf-201807240026-5178340}}.
> {code:title=Part of log including exception|borderStyle=solid}
> 2018-07-30 05:57:16.701 DEBUG o.w.e.c.c.o.OnlineManagementClient: Executing CLI operation undeploy *metamer*
> 05:57:20,757 INFO [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location /home/hudson/hudson_workspace/workspace/eap-7.x-jsf-richfaces/6b4879d7/wildfly-14.0.0.Beta2-SNAPSHOT/standalone/data/content/c1/ef588d063c7cd396e765ef8452fbc43c04ce75/content
> 05:57:20,779 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "metamer.war" (runtime-name: "metamer.war")
> 05:57:22,206 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.deployment.unit."metamer.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."metamer.war".PARSE: WFLYSRV0153: Failed to process phase PARSE of deployment "metamer.war"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:151)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1736)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1698)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYPOJO0038: Exception while parsing POJO descriptor file: "/content/metamer.war/WEB-INF/lib/netty-3.2.10.Final.jar/META-INF/jboss-beans.xml"
> at org.jboss.as.pojo.KernelDeploymentParsingProcessor.parseDescriptor(KernelDeploymentParsingProcessor.java:154)
> at org.jboss.as.pojo.KernelDeploymentParsingProcessor.parseDescriptors(KernelDeploymentParsingProcessor.java:125)
> at org.jboss.as.pojo.KernelDeploymentParsingProcessor.deploy(KernelDeploymentParsingProcessor.java:82)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:144)
> ... 8 more
> Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[17,1]
> Message: Unexpected element '{urn:jboss:bean-deployer:2.0}deployment'
> at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:120)
> at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:76)
> at org.jboss.as.pojo.KernelDeploymentParsingProcessor.parseDescriptor(KernelDeploymentParsingProcessor.java:145)
> ... 11 more
> 05:57:22,210 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "metamer.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"metamer.war\".PARSE" => "WFLYSRV0153: Failed to process phase PARSE of deployment \"metamer.war\"
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYPOJO0038: Exception while parsing POJO descriptor file: \"/content/metamer.war/WEB-INF/lib/netty-3.2.10.Final.jar/META-INF/jboss-beans.xml\"
> Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[17,1]
> Message: Unexpected element '{urn:jboss:bean-deployer:2.0}deployment'"}}
> 05:57:22,217 ERROR [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0021: Deploy of deployment "metamer.war" was rolled back with the following failure message:
> {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"metamer.war\".PARSE" => "WFLYSRV0153: Failed to process phase PARSE of deployment \"metamer.war\"
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYPOJO0038: Exception while parsing POJO descriptor file: \"/content/metamer.war/WEB-INF/lib/netty-3.2.10.Final.jar/META-INF/jboss-beans.xml\"
> Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[17,1]
> Message: Unexpected element '{urn:jboss:bean-deployer:2.0}deployment'"}}
> 05:57:22,266 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment metamer.war (runtime-name: metamer.war) in 47ms
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (WFLY-10757) ParseError when deploying application with netty dependency
by Jan Kašík (JIRA)
[ https://issues.jboss.org/browse/WFLY-10757?page=com.atlassian.jira.plugin... ]
Jan Kašík updated WFLY-10757:
-----------------------------
Environment: CI build of Wildfly: wf-201807260026-c80c2b1 and later (was: CI build of Wildfly: wf-201807280026-7f1d8dc)
> ParseError when deploying application with netty dependency
> ------------------------------------------------------------
>
> Key: WFLY-10757
> URL: https://issues.jboss.org/browse/WFLY-10757
> Project: WildFly
> Issue Type: Bug
> Components: Server, XML Frameworks
> Affects Versions: 14.0.0.CR1
> Environment: CI build of Wildfly: wf-201807260026-c80c2b1 and later
> Reporter: Jan Kašík
> Assignee: Jason Greene
> Priority: Critical
>
> It is not possible to deploy app which has {{org.jboss.netty}} packed as a dependency. During processing of {{jboss-beans.xml}}, the deployment fails because there is an unexpected element: {{\{urn:jboss:bean-deployer:2.0}deployment}}. This worked with previous CI builds like {{wf-201807240026-5178340}}.
> {code:title=Part of log including exception|borderStyle=solid}
> 2018-07-30 05:57:16.701 DEBUG o.w.e.c.c.o.OnlineManagementClient: Executing CLI operation undeploy *metamer*
> 05:57:20,757 INFO [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location /home/hudson/hudson_workspace/workspace/eap-7.x-jsf-richfaces/6b4879d7/wildfly-14.0.0.Beta2-SNAPSHOT/standalone/data/content/c1/ef588d063c7cd396e765ef8452fbc43c04ce75/content
> 05:57:20,779 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "metamer.war" (runtime-name: "metamer.war")
> 05:57:22,206 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.deployment.unit."metamer.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."metamer.war".PARSE: WFLYSRV0153: Failed to process phase PARSE of deployment "metamer.war"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:151)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1736)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1698)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYPOJO0038: Exception while parsing POJO descriptor file: "/content/metamer.war/WEB-INF/lib/netty-3.2.10.Final.jar/META-INF/jboss-beans.xml"
> at org.jboss.as.pojo.KernelDeploymentParsingProcessor.parseDescriptor(KernelDeploymentParsingProcessor.java:154)
> at org.jboss.as.pojo.KernelDeploymentParsingProcessor.parseDescriptors(KernelDeploymentParsingProcessor.java:125)
> at org.jboss.as.pojo.KernelDeploymentParsingProcessor.deploy(KernelDeploymentParsingProcessor.java:82)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:144)
> ... 8 more
> Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[17,1]
> Message: Unexpected element '{urn:jboss:bean-deployer:2.0}deployment'
> at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:120)
> at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:76)
> at org.jboss.as.pojo.KernelDeploymentParsingProcessor.parseDescriptor(KernelDeploymentParsingProcessor.java:145)
> ... 11 more
> 05:57:22,210 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "metamer.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"metamer.war\".PARSE" => "WFLYSRV0153: Failed to process phase PARSE of deployment \"metamer.war\"
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYPOJO0038: Exception while parsing POJO descriptor file: \"/content/metamer.war/WEB-INF/lib/netty-3.2.10.Final.jar/META-INF/jboss-beans.xml\"
> Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[17,1]
> Message: Unexpected element '{urn:jboss:bean-deployer:2.0}deployment'"}}
> 05:57:22,217 ERROR [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0021: Deploy of deployment "metamer.war" was rolled back with the following failure message:
> {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"metamer.war\".PARSE" => "WFLYSRV0153: Failed to process phase PARSE of deployment \"metamer.war\"
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYPOJO0038: Exception while parsing POJO descriptor file: \"/content/metamer.war/WEB-INF/lib/netty-3.2.10.Final.jar/META-INF/jboss-beans.xml\"
> Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[17,1]
> Message: Unexpected element '{urn:jboss:bean-deployer:2.0}deployment'"}}
> 05:57:22,266 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment metamer.war (runtime-name: metamer.war) in 47ms
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (WFLY-10757) ParseError when deploying application with netty dependency
by Jan Kašík (JIRA)
Jan Kašík created WFLY-10757:
--------------------------------
Summary: ParseError when deploying application with netty dependency
Key: WFLY-10757
URL: https://issues.jboss.org/browse/WFLY-10757
Project: WildFly
Issue Type: Bug
Components: Server, XML Frameworks
Affects Versions: 14.0.0.CR1
Environment: CI build of Wildfly: wf-201807280026-7f1d8dc
Reporter: Jan Kašík
Assignee: Jason Greene
Priority: Critical
It is not possible to deploy app which has {{org.jboss.netty}} packed as a dependency. During processing of {{jboss-beans.xml}}, the deployment fails because there is an unexpected element: {{\{urn:jboss:bean-deployer:2.0}deployment}}.
{code:title=Part of log including exception|borderStyle=solid}
2018-07-30 05:57:16.701 DEBUG o.w.e.c.c.o.OnlineManagementClient: Executing CLI operation undeploy *metamer*
05:57:20,757 INFO [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location /home/hudson/hudson_workspace/workspace/eap-7.x-jsf-richfaces/6b4879d7/wildfly-14.0.0.Beta2-SNAPSHOT/standalone/data/content/c1/ef588d063c7cd396e765ef8452fbc43c04ce75/content
05:57:20,779 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "metamer.war" (runtime-name: "metamer.war")
05:57:22,206 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.deployment.unit."metamer.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."metamer.war".PARSE: WFLYSRV0153: Failed to process phase PARSE of deployment "metamer.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:151)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1736)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1698)
at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
at java.lang.Thread.run(Thread.java:748)
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYPOJO0038: Exception while parsing POJO descriptor file: "/content/metamer.war/WEB-INF/lib/netty-3.2.10.Final.jar/META-INF/jboss-beans.xml"
at org.jboss.as.pojo.KernelDeploymentParsingProcessor.parseDescriptor(KernelDeploymentParsingProcessor.java:154)
at org.jboss.as.pojo.KernelDeploymentParsingProcessor.parseDescriptors(KernelDeploymentParsingProcessor.java:125)
at org.jboss.as.pojo.KernelDeploymentParsingProcessor.deploy(KernelDeploymentParsingProcessor.java:82)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:144)
... 8 more
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[17,1]
Message: Unexpected element '{urn:jboss:bean-deployer:2.0}deployment'
at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:120)
at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:76)
at org.jboss.as.pojo.KernelDeploymentParsingProcessor.parseDescriptor(KernelDeploymentParsingProcessor.java:145)
... 11 more
05:57:22,210 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "metamer.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"metamer.war\".PARSE" => "WFLYSRV0153: Failed to process phase PARSE of deployment \"metamer.war\"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYPOJO0038: Exception while parsing POJO descriptor file: \"/content/metamer.war/WEB-INF/lib/netty-3.2.10.Final.jar/META-INF/jboss-beans.xml\"
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[17,1]
Message: Unexpected element '{urn:jboss:bean-deployer:2.0}deployment'"}}
05:57:22,217 ERROR [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0021: Deploy of deployment "metamer.war" was rolled back with the following failure message:
{"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"metamer.war\".PARSE" => "WFLYSRV0153: Failed to process phase PARSE of deployment \"metamer.war\"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYPOJO0038: Exception while parsing POJO descriptor file: \"/content/metamer.war/WEB-INF/lib/netty-3.2.10.Final.jar/META-INF/jboss-beans.xml\"
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[17,1]
Message: Unexpected element '{urn:jboss:bean-deployer:2.0}deployment'"}}
05:57:22,266 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment metamer.war (runtime-name: metamer.war) in 47ms
{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months