[JBoss JIRA] (WFLY-4198) NullPointerException in LogDiagnosticContextRecoveryInterceptor when calling an asynchronous EJB
by Sergiy Barlabanov (JIRA)
[ https://issues.jboss.org/browse/WFLY-4198?page=com.atlassian.jira.plugin.... ]
Sergiy Barlabanov updated WFLY-4198:
------------------------------------
Summary: NullPointerException in LogDiagnosticContextRecoveryInterceptor when calling an asynchronous EJB (was: NullPointerException when trying to access MDC map with SLF4j+Logback logging)
> NullPointerException in LogDiagnosticContextRecoveryInterceptor when calling an asynchronous EJB
> ------------------------------------------------------------------------------------------------
>
> Key: WFLY-4198
> URL: https://issues.jboss.org/browse/WFLY-4198
> Project: WildFly
> Issue Type: Feature Request
> Components: EJB
> Affects Versions: 8.2.0.Final
> Reporter: Sergiy Barlabanov
> Assignee: David Lloyd
>
> When trying to call an asynchronous EJB in a Web application using slf4j (1.7.5+) & logback(1.0.13+) for logging the following NullPointerException occurs (see below).
> The problem is in the line 67 of LogDiagnosticContextRecoveryInterceptor class, when it tries to access MDC map, which is null. According to SLF4J API the copy of MDC map may be null: see the javadoc of org.slf4j.MDC#getCopyOfContextMap.
> So LogDiagnosticContextRecoveryInterceptor or org.jboss.logging.Slf4jLoggerProvider have to check the map for null.
> Currently there is no workaround for that :(.
> Caused by: java.lang.NullPointerException
> at org.jboss.as.ejb3.component.interceptors.LogDiagnosticContextRecoveryInterceptor.processInvocation(LogDiagnosticContextRecoveryInterceptor.java:67)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
> at org.jboss.as.ejb3.component.interceptors.AsyncFutureInterceptorFactory$1$2.runInvocation(AsyncFutureInterceptorFactory.java:97)
> at org.jboss.as.ejb3.component.interceptors.AsyncInvocationTask.run(AsyncInvocationTask.java:73)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:744)
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 5 months
[JBoss JIRA] (WFLY-4200) WAR MDB cannot obtain superclass on module classpath
by John Mazzitelli (JIRA)
[ https://issues.jboss.org/browse/WFLY-4200?page=com.atlassian.jira.plugin.... ]
John Mazzitelli updated WFLY-4200:
----------------------------------
Attachment: mdb-test.zip
I'm attaching the zip file with the replication code here (its the same as that which was attached to the associated forum thread).
To replicate the problem:
1) take this zip file, and unzip it in the root install dir of your wildfly 8.2 distro (this zip file will overlay a war and a module deployment inside your wildfly)
2) run wildfly's standalone.sh.
See the error logs and notice the MDB fails to deploy.
Source code is in the attached .zip file but see the forum thread post where I show the relevant source.
> WAR MDB cannot obtain superclass on module classpath
> ----------------------------------------------------
>
> Key: WFLY-4200
> URL: https://issues.jboss.org/browse/WFLY-4200
> Project: WildFly
> Issue Type: Bug
> Components: Class Loading, EJB
> Affects Versions: 8.2.0.Final
> Reporter: John Mazzitelli
> Assignee: David Lloyd
> Priority: Minor
> Attachments: mdb-test.zip
>
>
> see the forum post for details:
> https://developer.jboss.org/message/914355
> but suffice it to say this is similar to https://issues.jboss.org/browse/AS7-2638 which appears to have come back again.
> In my WAR, I have an MDB which extends a class (in which that superclass implements MessageListener) and that superclass is in a module that my WAR depends on; the MDB fails to deploy. I have to explicitly add an annotation attribute to workaround the problem.
> Again, see the forum for the very easy steps to replicate with a small zip file that contains the replication code.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 5 months
[JBoss JIRA] (WFLY-4200) WAR MDB cannot obtain superclass on module classpath
by John Mazzitelli (JIRA)
John Mazzitelli created WFLY-4200:
-------------------------------------
Summary: WAR MDB cannot obtain superclass on module classpath
Key: WFLY-4200
URL: https://issues.jboss.org/browse/WFLY-4200
Project: WildFly
Issue Type: Bug
Components: Class Loading, EJB
Affects Versions: 8.2.0.Final
Reporter: John Mazzitelli
Assignee: David Lloyd
Priority: Minor
see the forum post for details:
https://developer.jboss.org/message/914355
but suffice it to say this is similar to https://issues.jboss.org/browse/AS7-2638 which appears to have come back again.
In my WAR, I have an MDB which extends a class (in which that superclass implements MessageListener) and that superclass is in a module that my WAR depends on; the MDB fails to deploy. I have to explicitly add an annotation attribute to workaround the problem.
Again, see the forum for the very easy steps to replicate with a small zip file that contains the replication code.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 5 months
[JBoss JIRA] (WFLY-4185) Using annotated servlet listeners from modules
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-4185?page=com.atlassian.jira.plugin.... ]
Stuart Douglas commented on WFLY-4185:
--------------------------------------
I just tested this against EAP upstream and it seems to be picking up the listener from modules (I just cherry picked your test case into EAP).
> Using annotated servlet listeners from modules
> ----------------------------------------------
>
> Key: WFLY-4185
> URL: https://issues.jboss.org/browse/WFLY-4185
> Project: WildFly
> Issue Type: Bug
> Components: EE
> Affects Versions: 9.0.0.Alpha1
> Reporter: Pedro Igor
> Assignee: Stuart Douglas
>
> PicketLink provides support for Http Security. Basically, it consists of an API to define security policies to the paths or resources of an application and a security filter (servlet filter) that is responsible to enforce those policies for every single request.
> The security filter is installed from a specific ServletContextListener (org.picketlink.http.internal.PicketLinkServletContextListener) that checks if the application has defined any security policy in order to decide if the filter must be installed or not.
> PicketLink also defines a ServletRequestListener (org.picketlink.http.internal.HttpServletRequestListener) that is used to produce a decorated HttpServletRequest instance. This decorated instance provides full integration between PL and the HttpServletRequest security methods plus some other goodies for PL users such as URL rewriting, etc.
> Both listeners (servletcontext and request) are CDI beans with injection points and/or producer methods.
> When using PL from modules, the producer method of org.picketlink.http.internal.HttpServletRequestListener#produce is not being recognized. And that makes impossible to use PL from modules.
> The same code works if you use PL jars inside the deployment.
> Another interesting behavior is that EAP and WildFly are behaving differently. In EAP (latest build), the ServletContextListener is only recognized as a CDI bean if you define it in the web.xml. While in WildFly this is not necessary.
> Also, in EAP the producer method of HttpServletRequestListener is properly recognized and everything works fine.
> I've created a branch [1] to test this issue. The test case is {code}org.wildfly.test.integration.security.picketlink.core.http.ServletListenerFromModuleTestCase{code}.
> [1] https://github.com/pedroigor/wildfly/tree/WFLY-4185
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 5 months
[JBoss JIRA] (WFLY-4196) HTTP protocol violation
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-4196?page=com.atlassian.jira.plugin.... ]
Stuart Douglas edited comment on WFLY-4196 at 12/22/14 8:04 PM:
----------------------------------------------------------------
The call that is used to set the length is response.setContentLengthLong(contentLength)
With regard to clearing the header it should be possible to call setHeader("Content-Length", null);
In order to activate the built in handler you also need to attach it to a host (note that the predicate part is used to determine which requests have the filter applied):
/subsystem=undertow/server=default-server/host=default-host/filter-ref=gzipfilter:add(predicate="path-suffix[.css, .js]")
I will have a bit more of a think about how to best handle situations like this. In particular there are a few issues:
- If the default servlet does not set the content-length header then chunked encoding will be used, which is less efficient, and means that a browser can't display a progress bar when downloading files.
- It is not really possible for compression filters to set a content length unless they are prepared to buffer the whole resource, as the content length can't be determined until the whole response has been compressed. If the filter is buffering the whole resource then it should just set a content length
- We can't wait till the filter is done to set the content length, this is done by the default servlet that knows how big the file it is serving is. On possibility would be to just not set the content length header if it detects that the output stream has been wrapped. Another possibility would be to automatically clear the content-length if a transfer or content encoding header is set, although both of these could potentially cause problems.
was (Author: swd847):
The call that is used to set the length is response.setContentLengthLong(contentLength)
With regard to clearing the header it should be possible to call setHeader("Content-Length", null);
In order to activate the built in handler you also need to attach it to a host (note that the predicate part is used to determine which requests have the filter applied):
/subsystem=undertow/server=default-server/host=default-host/filter-ref=gzipfilter:add(predicate="path-suffix[.css] or path-suffix[.js]")
I will have a bit more of a think about how to best handle situations like this. In particular there are a few issues:
- If the default servlet does not set the content-length header then chunked encoding will be used, which is less efficient, and means that a browser can't display a progress bar when downloading files.
- It is not really possible for compression filters to set a content length unless they are prepared to buffer the whole resource, as the content length can't be determined until the whole response has been compressed. If the filter is buffering the whole resource then it should just set a content length
- We can't wait till the filter is done to set the content length, this is done by the default servlet that knows how big the file it is serving is. On possibility would be to just not set the content length header if it detects that the output stream has been wrapped. Another possibility would be to automatically clear the content-length if a transfer or content encoding header is set, although both of these could potentially cause problems.
> HTTP protocol violation
> -----------------------
>
> Key: WFLY-4196
> URL: https://issues.jboss.org/browse/WFLY-4196
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 8.1.0.Final, 8.2.0.Final
> Reporter: Nicolas Cazottes
> Assignee: Stuart Douglas
> Priority: Blocker
> Attachments: bug-wildfly-gzip-war-1.0.0-SNAPSHOT.war, fiddler_protocol_violation.jpg
>
>
> If you deploy the given war in wildfly and open this url http://localhost:8080/bug/images/download.png : it seems to work correctly but if you run it with fiddler2 active, fiddler reports a protocol violation on the Content-Length header value.
> Actually, If the content is some js or css, the browser does not correctly reads it and the web page is corrupted.
> The explanation is that the web application uses a filter to compress the content in gzip format.
> For information, this application works correctly with jboss as 7 or before (that embed tomcat). I discovered the problem while trying to upgrade my application.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 5 months
[JBoss JIRA] (WFLY-4196) HTTP protocol violation
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-4196?page=com.atlassian.jira.plugin.... ]
Stuart Douglas commented on WFLY-4196:
--------------------------------------
The call that is used to set the length is response.setContentLengthLong(contentLength)
With regard to clearing the header it should be possible to call setHeader("Content-Length", null);
In order to activate the built in handler you also need to attach it to a host (note that the predicate part is used to determine which requests have the filter applied):
/subsystem=undertow/server=default-server/host=default-host/filter-ref=gzipfilter:add(predicate="path-suffix[.css] or path-suffix[.js]")
I will have a bit more of a think about how to best handle situations like this. In particular there are a few issues:
- If the default servlet does not set the content-length header then chunked encoding will be used, which is less efficient, and means that a browser can't display a progress bar when downloading files.
- It is not really possible for compression filters to set a content length unless they are prepared to buffer the whole resource, as the content length can't be determined until the whole response has been compressed. If the filter is buffering the whole resource then it should just set a content length
- We can't wait till the filter is done to set the content length, this is done by the default servlet that knows how big the file it is serving is. On possibility would be to just not set the content length header if it detects that the output stream has been wrapped. Another possibility would be to automatically clear the content-length if a transfer or content encoding header is set, although both of these could potentially cause problems.
> HTTP protocol violation
> -----------------------
>
> Key: WFLY-4196
> URL: https://issues.jboss.org/browse/WFLY-4196
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 8.1.0.Final, 8.2.0.Final
> Reporter: Nicolas Cazottes
> Assignee: Stuart Douglas
> Priority: Blocker
> Attachments: bug-wildfly-gzip-war-1.0.0-SNAPSHOT.war, fiddler_protocol_violation.jpg
>
>
> If you deploy the given war in wildfly and open this url http://localhost:8080/bug/images/download.png : it seems to work correctly but if you run it with fiddler2 active, fiddler reports a protocol violation on the Content-Length header value.
> Actually, If the content is some js or css, the browser does not correctly reads it and the web page is corrupted.
> The explanation is that the web application uses a filter to compress the content in gzip format.
> For information, this application works correctly with jboss as 7 or before (that embed tomcat). I discovered the problem while trying to upgrade my application.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 5 months
[JBoss JIRA] (WFLY-4199) App redeploy exceptions
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-4199?page=com.atlassian.jira.plugin.... ]
Stuart Douglas commented on WFLY-4199:
--------------------------------------
I can't reproduce this, although it looks like it may be some kind of VFS or other deployment issue, as it appears the deployment root is not being set up correctly.
Are you using Windows by any chance?
> App redeploy exceptions
> -----------------------
>
> Key: WFLY-4199
> URL: https://issues.jboss.org/browse/WFLY-4199
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow), Web Services
> Reporter: Eduardo Martins
> Assignee: Stuart Douglas
>
> I'm noticing intermittent occurrences of exceptions when redeploying quickstarts, and unfortunately the chance seems quite high. The exceptions,a at least on my end, may be reproduced by using app "thread-racing" of the following branches of my quickstarts fork:
> Web Services) https://github.com/emmartins/quickstart/tree/redeploy-exceptions , where the following exception occur at an alarming 8 out of 10 redeploys:
> {code}
> 19:41:38,502 INFO [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location /Users/emmartins/wildfly/git/wildfly/dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/standalone/data/content/b5/1306d722adbe53ba6b7445f1b2d72facd66201/content
> 19:41:38,504 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0022: Unregistered web context: /wildfly-thread-racing
> 19:41:38,519 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0010: Stopping weld service for deployment wildfly-thread-racing.war
> 19:41:38,527 INFO [org.jboss.as.server.deployment] (MSC service thread 1-12) WFLYSRV0028: Stopped deployment wildfly-thread-racing.war (runtime-name: wildfly-thread-racing.war) in 24ms
> 19:41:38,528 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "wildfly-thread-racing.war" (runtime-name: "wildfly-thread-racing.war")
> 19:41:38,556 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-14) MSC000001: Failed to start service jboss.deployment.unit."wildfly-thread-racing.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."wildfly-thread-racing.war".PARSE: WFLYSRV0153: Failed to process phase PARSE of deployment "wildfly-thread-racing.war"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:163)
> 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:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.NullPointerException
> at org.jboss.as.webservices.deployers.WebservicesDescriptorDeploymentProcessor.getWebServicesDescriptorURL(WebservicesDescriptorDeploymentProcessor.java:70)
> at org.jboss.as.webservices.deployers.WebservicesDescriptorDeploymentProcessor.deploy(WebservicesDescriptorDeploymentProcessor.java:52)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:156)
> ... 5 more
> 19:41:38,559 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0028: Stopped deployment wildfly-thread-racing.war (runtime-name: wildfly-thread-racing.war) in 30ms
> 19:41:38,560 INFO [org.jboss.as.server.deployment] (MSC service thread 1-12) WFLYSRV0027: Starting deployment of "wildfly-thread-racing.war" (runtime-name: "wildfly-thread-racing.war")
> 19:41:38,593 WARN [org.jboss.weld.deployer] (MSC service thread 1-13) WFLYWELD0012: Warning while parsing vfs:/content/wildfly-thread-racing.war/WEB-INF/beans.xml:22 cvc-complex-type.4: Attribute 'bean-discovery-mode' must appear on element 'beans'.
> 19:41:38,609 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0003: Processing weld deployment wildfly-thread-racing.war
> 19:41:38,633 INFO [org.jboss.as.messaging] (MSC service thread 1-2) WFLYMSG0002: Bound messaging object to jndi name java:global/threadRacing/stages/jms/requestQueue
> 19:41:38,637 INFO [org.jboss.weld.deployer] (MSC service thread 1-9) WFLYWELD0006: Starting Services for CDI deployment: wildfly-thread-racing.war
> 19:41:38,641 INFO [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0009: Starting weld service for deployment wildfly-thread-racing.war
> 19:41:38,643 INFO [org.jboss.as.ejb3] (MSC service thread 1-10) WFLYEJB0042: Started message driven bean 'JMSRaceStageMessageListener' with 'hornetq-ra.rar' resource adapter
> 19:41:38,753 INFO [io.undertow.websockets.jsr] (MSC service thread 1-7) UT026003: Adding annotated server endpoint class org.jboss.as.quickstarts.threadracing.stage.websocket.ServerEndpoint for path /ws
> 19:41:38,754 INFO [io.undertow.websockets.jsr] (MSC service thread 1-7) UT026004: Adding annotated client endpoint class org.jboss.as.quickstarts.threadracing.stage.websocket.ClientEndpoint
> 19:41:38,758 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0021: Registered web context: /wildfly-thread-racing
> 19:41:38,770 INFO [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0013: Redeployed "wildfly-thread-racing.war"
> 19:41:38,770 INFO [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0016: Replaced deployment "wildfly-thread-racing.war" with deployment "wildfly-thread-racing.war"
> 19:41:38,771 INFO [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0002: Content removed from location /Users/emmartins/wildfly/git/wildfly/dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/standalone/data/content/98/04cfcd3addc74805031f222ee036ff47b62f5d/content
> {code}
> Web) https://github.com/emmartins/quickstart/tree/redeploy-exceptions2 , where the following exception occur about half of redeploys:
> {code}
> 20:27:05,715 INFO [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location /Users/emmartins/wildfly/git/wildfly/dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/standalone/data/content/c4/abc434ff307278c10061fb9dbbd3fcd0aff116/content
> 20:27:05,717 INFO [org.wildfly.extension.undertow] (MSC service thread 1-13) WFLYUT0022: Unregistered web context: /wildfly-thread-racing
> 20:27:05,734 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 77) WFLYJPA0011: Stopping Persistence Unit (phase 2 of 2) Service 'wildfly-thread-racing.war#RacePU'
> 20:27:05,735 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0010: Stopping weld service for deployment wildfly-thread-racing.war
> 20:27:05,735 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 77) WFLYJPA0011: Stopping Persistence Unit (phase 1 of 2) Service 'wildfly-thread-racing.war#RacePU'
> 20:27:05,745 INFO [org.jboss.as.server.deployment] (MSC service thread 1-9) WFLYSRV0028: Stopped deployment wildfly-thread-racing.war (runtime-name: wildfly-thread-racing.war) in 28ms
> 20:27:05,746 INFO [org.jboss.as.server.deployment] (MSC service thread 1-14) WFLYSRV0027: Starting deployment of "wildfly-thread-racing.war" (runtime-name: "wildfly-thread-racing.war")
> 20:27:05,775 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.deployment.unit."wildfly-thread-racing.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."wildfly-thread-racing.war".PARSE: WFLYSRV0153: Failed to process phase PARSE of deployment "wildfly-thread-racing.war"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:163)
> 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:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.NullPointerException
> at org.wildfly.extension.undertow.deployment.JBossWebParsingDeploymentProcessor.deploy(JBossWebParsingDeploymentProcessor.java:61)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:156)
> ... 5 more
> 20:27:05,780 INFO [org.jboss.as.server.deployment] (MSC service thread 1-15) WFLYSRV0028: Stopped deployment wildfly-thread-racing.war (runtime-name: wildfly-thread-racing.war) in 33ms
> 20:27:05,782 INFO [org.jboss.as.server.deployment] (MSC service thread 1-11) WFLYSRV0027: Starting deployment of "wildfly-thread-racing.war" (runtime-name: "wildfly-thread-racing.war")
> 20:27:05,819 INFO [org.jboss.as.jpa] (MSC service thread 1-10) WFLYJPA0002: Read persistence.xml for RacePU
> 20:27:05,833 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 77) WFLYJPA0010: Starting Persistence Unit (phase 1 of 2) Service 'wildfly-thread-racing.war#RacePU'
> 20:27:05,833 INFO [org.hibernate.jpa.internal.util.LogHelper] (ServerService Thread Pool -- 77) HHH000204: Processing PersistenceUnitInfo [
> name: RacePU
> ...]
> 20:27:05,838 INFO [org.jboss.weld.deployer] (MSC service thread 1-12) WFLYWELD0003: Processing weld deployment wildfly-thread-racing.war
> 20:27:05,841 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-12) JNDI bindings for session bean named RaceResults in deployment unit deployment "wildfly-thread-racing.war" are as follows:
> java:global/wildfly-thread-racing/RaceResults!org.jboss.as.quickstarts.threadracing.results.RaceResults
> java:app/wildfly-thread-racing/RaceResults!org.jboss.as.quickstarts.threadracing.results.RaceResults
> java:module/RaceResults!org.jboss.as.quickstarts.threadracing.results.RaceResults
> java:global/wildfly-thread-racing/RaceResults
> java:app/wildfly-thread-racing/RaceResults
> java:module/RaceResults
> 20:27:05,872 INFO [org.jboss.as.messaging] (MSC service thread 1-12) WFLYMSG0002: Bound messaging object to jndi name java:global/threadRacing/stages/jms/requestQueue
> 20:27:05,878 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0006: Starting Services for CDI deployment: wildfly-thread-racing.war
> 20:27:05,883 INFO [org.jboss.weld.deployer] (MSC service thread 1-12) WFLYWELD0009: Starting weld service for deployment wildfly-thread-racing.war
> 20:27:05,885 INFO [org.jboss.as.ejb3] (MSC service thread 1-13) WFLYEJB0042: Started message driven bean 'JMSRaceStageMessageListener' with 'hornetq-ra.rar' resource adapter
> 20:27:05,887 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 77) WFLYJPA0010: Starting Persistence Unit (phase 2 of 2) Service 'wildfly-thread-racing.war#RacePU'
> 20:27:05,893 INFO [org.hibernate.dialect.Dialect] (ServerService Thread Pool -- 77) HHH000400: Using dialect: org.hibernate.dialect.H2Dialect
> 20:27:05,893 WARN [org.hibernate.dialect.H2Dialect] (ServerService Thread Pool -- 77) HHH000431: Unable to determine H2 database version, certain features may not work
> 20:27:05,899 INFO [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (ServerService Thread Pool -- 77) HHH000397: Using ASTQueryTranslatorFactory
> 20:27:05,921 INFO [org.hibernate.dialect.Dialect] (ServerService Thread Pool -- 77) HHH000400: Using dialect: org.hibernate.dialect.H2Dialect
> 20:27:05,922 WARN [org.hibernate.dialect.H2Dialect] (ServerService Thread Pool -- 77) HHH000431: Unable to determine H2 database version, certain features may not work
> 20:27:06,057 INFO [io.undertow.websockets.jsr] (MSC service thread 1-15) UT026003: Adding annotated server endpoint class org.jboss.as.quickstarts.threadracing.WebSocketRace for path /race
> 20:27:06,085 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Deploying javax.ws.rs.core.Application: class org.jboss.as.quickstarts.threadracing.stage.jaxrs.BoxApplication$Proxy$_$$_WeldClientProxy
> 20:27:06,086 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding class resource org.jboss.as.quickstarts.threadracing.stage.jaxrs.BoxService from Application class org.jboss.as.quickstarts.threadracing.stage.jaxrs.BoxApplication$Proxy$_$$_WeldClientProxy
> 20:27:06,088 INFO [org.wildfly.extension.undertow] (MSC service thread 1-15) WFLYUT0021: Registered web context: /wildfly-thread-racing
> 20:27:06,102 INFO [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0013: Redeployed "wildfly-thread-racing.war"
> 20:27:06,102 INFO [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0016: Replaced deployment "wildfly-thread-racing.war" with deployment "wildfly-thread-racing.war"
> 20:27:06,103 INFO [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0002: Content removed from location /Users/emmartins/wildfly/git/wildfly/dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/standalone/data/content/fe/8d3392468fc3e5e8b15d722d003fe3e0f851af/content
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 5 months
[JBoss JIRA] (WFLY-4196) HTTP protocol violation
by Nicolas Cazottes (JIRA)
[ https://issues.jboss.org/browse/WFLY-4196?page=com.atlassian.jira.plugin.... ]
Nicolas Cazottes commented on WFLY-4196:
----------------------------------------
I did some search in the source code and in debug mode and there is no call to the HttpServletResponse.setHeader or HttpServletResponse.addHeader methods for the Content-Length header.
Another point is that the server returns a value for the Content-Length of 3854 bytes where as the real (compressed size is smaller and is of 3760 bytes).
So I think that undertow determines the size of the Content-Length before the filter applies and should instead wait the end of the filter to set the value of the Content-Length header.
What do you mean by clearing the Content-Length header ? I do not see any API to remove an HTTP Header in HttpServletResponse.
For the test of the gzip subsystem configured in undertow, if I activate it via the command /subsystem=undertow/configuration=filter/gzip=gzipfilter/:add, fiddler does not detect any compression on the wire at all. Is it the correct way of activating it ?
> HTTP protocol violation
> -----------------------
>
> Key: WFLY-4196
> URL: https://issues.jboss.org/browse/WFLY-4196
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 8.1.0.Final, 8.2.0.Final
> Reporter: Nicolas Cazottes
> Assignee: Stuart Douglas
> Priority: Blocker
> Attachments: bug-wildfly-gzip-war-1.0.0-SNAPSHOT.war, fiddler_protocol_violation.jpg
>
>
> If you deploy the given war in wildfly and open this url http://localhost:8080/bug/images/download.png : it seems to work correctly but if you run it with fiddler2 active, fiddler reports a protocol violation on the Content-Length header value.
> Actually, If the content is some js or css, the browser does not correctly reads it and the web page is corrupted.
> The explanation is that the web application uses a filter to compress the content in gzip format.
> For information, this application works correctly with jboss as 7 or before (that embed tomcat). I discovered the problem while trying to upgrade my application.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 5 months
[JBoss JIRA] (WFLY-4199) App redeploy exceptions
by Eduardo Martins (JIRA)
[ https://issues.jboss.org/browse/WFLY-4199?page=com.atlassian.jira.plugin.... ]
Eduardo Martins commented on WFLY-4199:
---------------------------------------
Start WildFly with full config and use mvn wilfly:deploy
> App redeploy exceptions
> -----------------------
>
> Key: WFLY-4199
> URL: https://issues.jboss.org/browse/WFLY-4199
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow), Web Services
> Reporter: Eduardo Martins
> Assignee: Stuart Douglas
>
> I'm noticing intermittent occurrences of exceptions when redeploying quickstarts, and unfortunately the chance seems quite high. The exceptions,a at least on my end, may be reproduced by using app "thread-racing" of the following branches of my quickstarts fork:
> Web Services) https://github.com/emmartins/quickstart/tree/redeploy-exceptions , where the following exception occur at an alarming 8 out of 10 redeploys:
> {code}
> 19:41:38,502 INFO [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location /Users/emmartins/wildfly/git/wildfly/dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/standalone/data/content/b5/1306d722adbe53ba6b7445f1b2d72facd66201/content
> 19:41:38,504 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0022: Unregistered web context: /wildfly-thread-racing
> 19:41:38,519 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0010: Stopping weld service for deployment wildfly-thread-racing.war
> 19:41:38,527 INFO [org.jboss.as.server.deployment] (MSC service thread 1-12) WFLYSRV0028: Stopped deployment wildfly-thread-racing.war (runtime-name: wildfly-thread-racing.war) in 24ms
> 19:41:38,528 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "wildfly-thread-racing.war" (runtime-name: "wildfly-thread-racing.war")
> 19:41:38,556 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-14) MSC000001: Failed to start service jboss.deployment.unit."wildfly-thread-racing.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."wildfly-thread-racing.war".PARSE: WFLYSRV0153: Failed to process phase PARSE of deployment "wildfly-thread-racing.war"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:163)
> 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:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.NullPointerException
> at org.jboss.as.webservices.deployers.WebservicesDescriptorDeploymentProcessor.getWebServicesDescriptorURL(WebservicesDescriptorDeploymentProcessor.java:70)
> at org.jboss.as.webservices.deployers.WebservicesDescriptorDeploymentProcessor.deploy(WebservicesDescriptorDeploymentProcessor.java:52)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:156)
> ... 5 more
> 19:41:38,559 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0028: Stopped deployment wildfly-thread-racing.war (runtime-name: wildfly-thread-racing.war) in 30ms
> 19:41:38,560 INFO [org.jboss.as.server.deployment] (MSC service thread 1-12) WFLYSRV0027: Starting deployment of "wildfly-thread-racing.war" (runtime-name: "wildfly-thread-racing.war")
> 19:41:38,593 WARN [org.jboss.weld.deployer] (MSC service thread 1-13) WFLYWELD0012: Warning while parsing vfs:/content/wildfly-thread-racing.war/WEB-INF/beans.xml:22 cvc-complex-type.4: Attribute 'bean-discovery-mode' must appear on element 'beans'.
> 19:41:38,609 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0003: Processing weld deployment wildfly-thread-racing.war
> 19:41:38,633 INFO [org.jboss.as.messaging] (MSC service thread 1-2) WFLYMSG0002: Bound messaging object to jndi name java:global/threadRacing/stages/jms/requestQueue
> 19:41:38,637 INFO [org.jboss.weld.deployer] (MSC service thread 1-9) WFLYWELD0006: Starting Services for CDI deployment: wildfly-thread-racing.war
> 19:41:38,641 INFO [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0009: Starting weld service for deployment wildfly-thread-racing.war
> 19:41:38,643 INFO [org.jboss.as.ejb3] (MSC service thread 1-10) WFLYEJB0042: Started message driven bean 'JMSRaceStageMessageListener' with 'hornetq-ra.rar' resource adapter
> 19:41:38,753 INFO [io.undertow.websockets.jsr] (MSC service thread 1-7) UT026003: Adding annotated server endpoint class org.jboss.as.quickstarts.threadracing.stage.websocket.ServerEndpoint for path /ws
> 19:41:38,754 INFO [io.undertow.websockets.jsr] (MSC service thread 1-7) UT026004: Adding annotated client endpoint class org.jboss.as.quickstarts.threadracing.stage.websocket.ClientEndpoint
> 19:41:38,758 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0021: Registered web context: /wildfly-thread-racing
> 19:41:38,770 INFO [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0013: Redeployed "wildfly-thread-racing.war"
> 19:41:38,770 INFO [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0016: Replaced deployment "wildfly-thread-racing.war" with deployment "wildfly-thread-racing.war"
> 19:41:38,771 INFO [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0002: Content removed from location /Users/emmartins/wildfly/git/wildfly/dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/standalone/data/content/98/04cfcd3addc74805031f222ee036ff47b62f5d/content
> {code}
> Web) https://github.com/emmartins/quickstart/tree/redeploy-exceptions2 , where the following exception occur about half of redeploys:
> {code}
> 20:27:05,715 INFO [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location /Users/emmartins/wildfly/git/wildfly/dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/standalone/data/content/c4/abc434ff307278c10061fb9dbbd3fcd0aff116/content
> 20:27:05,717 INFO [org.wildfly.extension.undertow] (MSC service thread 1-13) WFLYUT0022: Unregistered web context: /wildfly-thread-racing
> 20:27:05,734 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 77) WFLYJPA0011: Stopping Persistence Unit (phase 2 of 2) Service 'wildfly-thread-racing.war#RacePU'
> 20:27:05,735 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0010: Stopping weld service for deployment wildfly-thread-racing.war
> 20:27:05,735 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 77) WFLYJPA0011: Stopping Persistence Unit (phase 1 of 2) Service 'wildfly-thread-racing.war#RacePU'
> 20:27:05,745 INFO [org.jboss.as.server.deployment] (MSC service thread 1-9) WFLYSRV0028: Stopped deployment wildfly-thread-racing.war (runtime-name: wildfly-thread-racing.war) in 28ms
> 20:27:05,746 INFO [org.jboss.as.server.deployment] (MSC service thread 1-14) WFLYSRV0027: Starting deployment of "wildfly-thread-racing.war" (runtime-name: "wildfly-thread-racing.war")
> 20:27:05,775 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.deployment.unit."wildfly-thread-racing.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."wildfly-thread-racing.war".PARSE: WFLYSRV0153: Failed to process phase PARSE of deployment "wildfly-thread-racing.war"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:163)
> 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:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.NullPointerException
> at org.wildfly.extension.undertow.deployment.JBossWebParsingDeploymentProcessor.deploy(JBossWebParsingDeploymentProcessor.java:61)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:156)
> ... 5 more
> 20:27:05,780 INFO [org.jboss.as.server.deployment] (MSC service thread 1-15) WFLYSRV0028: Stopped deployment wildfly-thread-racing.war (runtime-name: wildfly-thread-racing.war) in 33ms
> 20:27:05,782 INFO [org.jboss.as.server.deployment] (MSC service thread 1-11) WFLYSRV0027: Starting deployment of "wildfly-thread-racing.war" (runtime-name: "wildfly-thread-racing.war")
> 20:27:05,819 INFO [org.jboss.as.jpa] (MSC service thread 1-10) WFLYJPA0002: Read persistence.xml for RacePU
> 20:27:05,833 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 77) WFLYJPA0010: Starting Persistence Unit (phase 1 of 2) Service 'wildfly-thread-racing.war#RacePU'
> 20:27:05,833 INFO [org.hibernate.jpa.internal.util.LogHelper] (ServerService Thread Pool -- 77) HHH000204: Processing PersistenceUnitInfo [
> name: RacePU
> ...]
> 20:27:05,838 INFO [org.jboss.weld.deployer] (MSC service thread 1-12) WFLYWELD0003: Processing weld deployment wildfly-thread-racing.war
> 20:27:05,841 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-12) JNDI bindings for session bean named RaceResults in deployment unit deployment "wildfly-thread-racing.war" are as follows:
> java:global/wildfly-thread-racing/RaceResults!org.jboss.as.quickstarts.threadracing.results.RaceResults
> java:app/wildfly-thread-racing/RaceResults!org.jboss.as.quickstarts.threadracing.results.RaceResults
> java:module/RaceResults!org.jboss.as.quickstarts.threadracing.results.RaceResults
> java:global/wildfly-thread-racing/RaceResults
> java:app/wildfly-thread-racing/RaceResults
> java:module/RaceResults
> 20:27:05,872 INFO [org.jboss.as.messaging] (MSC service thread 1-12) WFLYMSG0002: Bound messaging object to jndi name java:global/threadRacing/stages/jms/requestQueue
> 20:27:05,878 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0006: Starting Services for CDI deployment: wildfly-thread-racing.war
> 20:27:05,883 INFO [org.jboss.weld.deployer] (MSC service thread 1-12) WFLYWELD0009: Starting weld service for deployment wildfly-thread-racing.war
> 20:27:05,885 INFO [org.jboss.as.ejb3] (MSC service thread 1-13) WFLYEJB0042: Started message driven bean 'JMSRaceStageMessageListener' with 'hornetq-ra.rar' resource adapter
> 20:27:05,887 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 77) WFLYJPA0010: Starting Persistence Unit (phase 2 of 2) Service 'wildfly-thread-racing.war#RacePU'
> 20:27:05,893 INFO [org.hibernate.dialect.Dialect] (ServerService Thread Pool -- 77) HHH000400: Using dialect: org.hibernate.dialect.H2Dialect
> 20:27:05,893 WARN [org.hibernate.dialect.H2Dialect] (ServerService Thread Pool -- 77) HHH000431: Unable to determine H2 database version, certain features may not work
> 20:27:05,899 INFO [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (ServerService Thread Pool -- 77) HHH000397: Using ASTQueryTranslatorFactory
> 20:27:05,921 INFO [org.hibernate.dialect.Dialect] (ServerService Thread Pool -- 77) HHH000400: Using dialect: org.hibernate.dialect.H2Dialect
> 20:27:05,922 WARN [org.hibernate.dialect.H2Dialect] (ServerService Thread Pool -- 77) HHH000431: Unable to determine H2 database version, certain features may not work
> 20:27:06,057 INFO [io.undertow.websockets.jsr] (MSC service thread 1-15) UT026003: Adding annotated server endpoint class org.jboss.as.quickstarts.threadracing.WebSocketRace for path /race
> 20:27:06,085 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Deploying javax.ws.rs.core.Application: class org.jboss.as.quickstarts.threadracing.stage.jaxrs.BoxApplication$Proxy$_$$_WeldClientProxy
> 20:27:06,086 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding class resource org.jboss.as.quickstarts.threadracing.stage.jaxrs.BoxService from Application class org.jboss.as.quickstarts.threadracing.stage.jaxrs.BoxApplication$Proxy$_$$_WeldClientProxy
> 20:27:06,088 INFO [org.wildfly.extension.undertow] (MSC service thread 1-15) WFLYUT0021: Registered web context: /wildfly-thread-racing
> 20:27:06,102 INFO [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0013: Redeployed "wildfly-thread-racing.war"
> 20:27:06,102 INFO [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0016: Replaced deployment "wildfly-thread-racing.war" with deployment "wildfly-thread-racing.war"
> 20:27:06,103 INFO [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0002: Content removed from location /Users/emmartins/wildfly/git/wildfly/dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/standalone/data/content/fe/8d3392468fc3e5e8b15d722d003fe3e0f851af/content
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 5 months
[JBoss JIRA] (WFLY-4199) App redeploy exceptions
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-4199?page=com.atlassian.jira.plugin.... ]
Stuart Douglas commented on WFLY-4199:
--------------------------------------
How are you redeploying? (Management API, deployment scanner etc)
> App redeploy exceptions
> -----------------------
>
> Key: WFLY-4199
> URL: https://issues.jboss.org/browse/WFLY-4199
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow), Web Services
> Reporter: Eduardo Martins
> Assignee: Stuart Douglas
>
> I'm noticing intermittent occurrences of exceptions when redeploying quickstarts, and unfortunately the chance seems quite high. The exceptions,a at least on my end, may be reproduced by using app "thread-racing" of the following branches of my quickstarts fork:
> Web Services) https://github.com/emmartins/quickstart/tree/redeploy-exceptions , where the following exception occur at an alarming 8 out of 10 redeploys:
> {code}
> 19:41:38,502 INFO [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location /Users/emmartins/wildfly/git/wildfly/dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/standalone/data/content/b5/1306d722adbe53ba6b7445f1b2d72facd66201/content
> 19:41:38,504 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0022: Unregistered web context: /wildfly-thread-racing
> 19:41:38,519 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0010: Stopping weld service for deployment wildfly-thread-racing.war
> 19:41:38,527 INFO [org.jboss.as.server.deployment] (MSC service thread 1-12) WFLYSRV0028: Stopped deployment wildfly-thread-racing.war (runtime-name: wildfly-thread-racing.war) in 24ms
> 19:41:38,528 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "wildfly-thread-racing.war" (runtime-name: "wildfly-thread-racing.war")
> 19:41:38,556 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-14) MSC000001: Failed to start service jboss.deployment.unit."wildfly-thread-racing.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."wildfly-thread-racing.war".PARSE: WFLYSRV0153: Failed to process phase PARSE of deployment "wildfly-thread-racing.war"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:163)
> 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:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.NullPointerException
> at org.jboss.as.webservices.deployers.WebservicesDescriptorDeploymentProcessor.getWebServicesDescriptorURL(WebservicesDescriptorDeploymentProcessor.java:70)
> at org.jboss.as.webservices.deployers.WebservicesDescriptorDeploymentProcessor.deploy(WebservicesDescriptorDeploymentProcessor.java:52)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:156)
> ... 5 more
> 19:41:38,559 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0028: Stopped deployment wildfly-thread-racing.war (runtime-name: wildfly-thread-racing.war) in 30ms
> 19:41:38,560 INFO [org.jboss.as.server.deployment] (MSC service thread 1-12) WFLYSRV0027: Starting deployment of "wildfly-thread-racing.war" (runtime-name: "wildfly-thread-racing.war")
> 19:41:38,593 WARN [org.jboss.weld.deployer] (MSC service thread 1-13) WFLYWELD0012: Warning while parsing vfs:/content/wildfly-thread-racing.war/WEB-INF/beans.xml:22 cvc-complex-type.4: Attribute 'bean-discovery-mode' must appear on element 'beans'.
> 19:41:38,609 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0003: Processing weld deployment wildfly-thread-racing.war
> 19:41:38,633 INFO [org.jboss.as.messaging] (MSC service thread 1-2) WFLYMSG0002: Bound messaging object to jndi name java:global/threadRacing/stages/jms/requestQueue
> 19:41:38,637 INFO [org.jboss.weld.deployer] (MSC service thread 1-9) WFLYWELD0006: Starting Services for CDI deployment: wildfly-thread-racing.war
> 19:41:38,641 INFO [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0009: Starting weld service for deployment wildfly-thread-racing.war
> 19:41:38,643 INFO [org.jboss.as.ejb3] (MSC service thread 1-10) WFLYEJB0042: Started message driven bean 'JMSRaceStageMessageListener' with 'hornetq-ra.rar' resource adapter
> 19:41:38,753 INFO [io.undertow.websockets.jsr] (MSC service thread 1-7) UT026003: Adding annotated server endpoint class org.jboss.as.quickstarts.threadracing.stage.websocket.ServerEndpoint for path /ws
> 19:41:38,754 INFO [io.undertow.websockets.jsr] (MSC service thread 1-7) UT026004: Adding annotated client endpoint class org.jboss.as.quickstarts.threadracing.stage.websocket.ClientEndpoint
> 19:41:38,758 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0021: Registered web context: /wildfly-thread-racing
> 19:41:38,770 INFO [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0013: Redeployed "wildfly-thread-racing.war"
> 19:41:38,770 INFO [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0016: Replaced deployment "wildfly-thread-racing.war" with deployment "wildfly-thread-racing.war"
> 19:41:38,771 INFO [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0002: Content removed from location /Users/emmartins/wildfly/git/wildfly/dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/standalone/data/content/98/04cfcd3addc74805031f222ee036ff47b62f5d/content
> {code}
> Web) https://github.com/emmartins/quickstart/tree/redeploy-exceptions2 , where the following exception occur about half of redeploys:
> {code}
> 20:27:05,715 INFO [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location /Users/emmartins/wildfly/git/wildfly/dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/standalone/data/content/c4/abc434ff307278c10061fb9dbbd3fcd0aff116/content
> 20:27:05,717 INFO [org.wildfly.extension.undertow] (MSC service thread 1-13) WFLYUT0022: Unregistered web context: /wildfly-thread-racing
> 20:27:05,734 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 77) WFLYJPA0011: Stopping Persistence Unit (phase 2 of 2) Service 'wildfly-thread-racing.war#RacePU'
> 20:27:05,735 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0010: Stopping weld service for deployment wildfly-thread-racing.war
> 20:27:05,735 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 77) WFLYJPA0011: Stopping Persistence Unit (phase 1 of 2) Service 'wildfly-thread-racing.war#RacePU'
> 20:27:05,745 INFO [org.jboss.as.server.deployment] (MSC service thread 1-9) WFLYSRV0028: Stopped deployment wildfly-thread-racing.war (runtime-name: wildfly-thread-racing.war) in 28ms
> 20:27:05,746 INFO [org.jboss.as.server.deployment] (MSC service thread 1-14) WFLYSRV0027: Starting deployment of "wildfly-thread-racing.war" (runtime-name: "wildfly-thread-racing.war")
> 20:27:05,775 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.deployment.unit."wildfly-thread-racing.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."wildfly-thread-racing.war".PARSE: WFLYSRV0153: Failed to process phase PARSE of deployment "wildfly-thread-racing.war"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:163)
> 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:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.NullPointerException
> at org.wildfly.extension.undertow.deployment.JBossWebParsingDeploymentProcessor.deploy(JBossWebParsingDeploymentProcessor.java:61)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:156)
> ... 5 more
> 20:27:05,780 INFO [org.jboss.as.server.deployment] (MSC service thread 1-15) WFLYSRV0028: Stopped deployment wildfly-thread-racing.war (runtime-name: wildfly-thread-racing.war) in 33ms
> 20:27:05,782 INFO [org.jboss.as.server.deployment] (MSC service thread 1-11) WFLYSRV0027: Starting deployment of "wildfly-thread-racing.war" (runtime-name: "wildfly-thread-racing.war")
> 20:27:05,819 INFO [org.jboss.as.jpa] (MSC service thread 1-10) WFLYJPA0002: Read persistence.xml for RacePU
> 20:27:05,833 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 77) WFLYJPA0010: Starting Persistence Unit (phase 1 of 2) Service 'wildfly-thread-racing.war#RacePU'
> 20:27:05,833 INFO [org.hibernate.jpa.internal.util.LogHelper] (ServerService Thread Pool -- 77) HHH000204: Processing PersistenceUnitInfo [
> name: RacePU
> ...]
> 20:27:05,838 INFO [org.jboss.weld.deployer] (MSC service thread 1-12) WFLYWELD0003: Processing weld deployment wildfly-thread-racing.war
> 20:27:05,841 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-12) JNDI bindings for session bean named RaceResults in deployment unit deployment "wildfly-thread-racing.war" are as follows:
> java:global/wildfly-thread-racing/RaceResults!org.jboss.as.quickstarts.threadracing.results.RaceResults
> java:app/wildfly-thread-racing/RaceResults!org.jboss.as.quickstarts.threadracing.results.RaceResults
> java:module/RaceResults!org.jboss.as.quickstarts.threadracing.results.RaceResults
> java:global/wildfly-thread-racing/RaceResults
> java:app/wildfly-thread-racing/RaceResults
> java:module/RaceResults
> 20:27:05,872 INFO [org.jboss.as.messaging] (MSC service thread 1-12) WFLYMSG0002: Bound messaging object to jndi name java:global/threadRacing/stages/jms/requestQueue
> 20:27:05,878 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0006: Starting Services for CDI deployment: wildfly-thread-racing.war
> 20:27:05,883 INFO [org.jboss.weld.deployer] (MSC service thread 1-12) WFLYWELD0009: Starting weld service for deployment wildfly-thread-racing.war
> 20:27:05,885 INFO [org.jboss.as.ejb3] (MSC service thread 1-13) WFLYEJB0042: Started message driven bean 'JMSRaceStageMessageListener' with 'hornetq-ra.rar' resource adapter
> 20:27:05,887 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 77) WFLYJPA0010: Starting Persistence Unit (phase 2 of 2) Service 'wildfly-thread-racing.war#RacePU'
> 20:27:05,893 INFO [org.hibernate.dialect.Dialect] (ServerService Thread Pool -- 77) HHH000400: Using dialect: org.hibernate.dialect.H2Dialect
> 20:27:05,893 WARN [org.hibernate.dialect.H2Dialect] (ServerService Thread Pool -- 77) HHH000431: Unable to determine H2 database version, certain features may not work
> 20:27:05,899 INFO [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (ServerService Thread Pool -- 77) HHH000397: Using ASTQueryTranslatorFactory
> 20:27:05,921 INFO [org.hibernate.dialect.Dialect] (ServerService Thread Pool -- 77) HHH000400: Using dialect: org.hibernate.dialect.H2Dialect
> 20:27:05,922 WARN [org.hibernate.dialect.H2Dialect] (ServerService Thread Pool -- 77) HHH000431: Unable to determine H2 database version, certain features may not work
> 20:27:06,057 INFO [io.undertow.websockets.jsr] (MSC service thread 1-15) UT026003: Adding annotated server endpoint class org.jboss.as.quickstarts.threadracing.WebSocketRace for path /race
> 20:27:06,085 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Deploying javax.ws.rs.core.Application: class org.jboss.as.quickstarts.threadracing.stage.jaxrs.BoxApplication$Proxy$_$$_WeldClientProxy
> 20:27:06,086 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-15) Adding class resource org.jboss.as.quickstarts.threadracing.stage.jaxrs.BoxService from Application class org.jboss.as.quickstarts.threadracing.stage.jaxrs.BoxApplication$Proxy$_$$_WeldClientProxy
> 20:27:06,088 INFO [org.wildfly.extension.undertow] (MSC service thread 1-15) WFLYUT0021: Registered web context: /wildfly-thread-racing
> 20:27:06,102 INFO [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0013: Redeployed "wildfly-thread-racing.war"
> 20:27:06,102 INFO [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0016: Replaced deployment "wildfly-thread-racing.war" with deployment "wildfly-thread-racing.war"
> 20:27:06,103 INFO [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0002: Content removed from location /Users/emmartins/wildfly/git/wildfly/dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/standalone/data/content/fe/8d3392468fc3e5e8b15d722d003fe3e0f851af/content
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 5 months
