[JBoss JIRA] (WFLY-11962) Unable to start wildfly in domain mode when metrics and health extensions are enabled
by Vlasta Ramik (Jira)
[ https://issues.jboss.org/browse/WFLY-11962?page=com.atlassian.jira.plugin... ]
Vlasta Ramik commented on WFLY-11962:
-------------------------------------
note: there is exclusion in domain.xml {noformat}
<host-exclude name="WildFly13.0">
<host-release id="WildFly13.0"/>
<excluded-extensions>
<extension module="org.wildfly.extension.datasources-agroal"/>
<extension module="org.wildfly.extension.microprofile.config-smallrye"/>
<extension module="org.wildfly.extension.microprofile.health-smallrye"/>
<extension module="org.wildfly.extension.microprofile.opentracing-smallrye"/>
<extension module="org.wildfly.extension.microprofile.metrics-smallrye"/>
</excluded-extensions>
</host-exclude>
<host-exclude name="WildFly14.0">
<host-release id="WildFly14.0"/>
<excluded-extensions>
<extension module="org.wildfly.extension.microprofile.metrics-smallrye"/>
</excluded-extensions>
</host-exclude>
{noformat}
> Unable to start wildfly in domain mode when metrics and health extensions are enabled
> -------------------------------------------------------------------------------------
>
> Key: WFLY-11962
> URL: https://issues.jboss.org/browse/WFLY-11962
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 16.0.0.Final
> Reporter: Vlasta Ramik
> Assignee: Brian Stansberry
> Priority: Major
>
> When WF is started in domain mode as described in steps to reproduce there is following in console {noformat}
> [Host Controller] 09:10:13,260 INFO [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0023: Starting server server-one
> 09:10:13,396 INFO [org.jboss.as.process.Server:server-one.status] (ProcessController-threads - 3) WFLYPC0018: Starting process 'Server:server-one'
> [Host Controller] 09:10:14,876 INFO [org.jboss.as.host.controller] (management task-1) WFLYHC0021: Server [Server:server-one] connected using connection [Channel ID 24b9374c (inbound) of Remoting connection 408c47e7 to localhost/127.0.0.1:38776 of endpoint "master:MANAGEMENT" <a16e023>]
> [Host Controller] 09:10:14,906 INFO [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0023: Starting server server-two
> [Host Controller] 09:10:14,921 INFO [org.jboss.as.host.controller] (server-registration-threads - 1) WFLYHC0020: Registering server server-one
> 09:10:15,031 INFO [org.jboss.as.process.Server:server-two.status] (ProcessController-threads - 3) WFLYPC0018: Starting process 'Server:server-two'
> 09:10:16,854 INFO [org.jboss.as.process.Server:server-one.status] (reaper for Server:server-one) WFLYPC0011: Process 'Server:server-one' finished with an exit status of 1
> [Host Controller] 09:10:16,896 INFO [org.jboss.as.host.controller] (ProcessControllerConnection-thread - 2) WFLYHC0027: Unregistering server server-one
> [Host Controller] 09:10:17,172 INFO [org.jboss.as.host.controller] (management task-1) WFLYHC0021: Server [Server:server-two] connected using connection [Channel ID 3d4db366 (inbound) of Remoting connection 382df477 to localhost/127.0.0.1:38794 of endpoint "master:MANAGEMENT" <a16e023>]
> [Host Controller] 09:10:17,207 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0062: Http management interface listening on http://127.0.0.1:9990/management and https://127.0.0.1:-1/management
> [Host Controller] 09:10:17,208 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0053: Admin console listening on http://127.0.0.1:9990 and https://127.0.0.1:-1
> [Host Controller] 09:10:17,212 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 16.0.0.Final (WildFly Core 8.0.0.Final) (Host Controller) started in 6589ms - Started 79 of 81 services (23 services are lazy, passive or on-demand)
> [Host Controller] 09:10:17,232 INFO [org.jboss.as.host.controller] (server-registration-threads - 1) WFLYHC0020: Registering server server-two
> 09:10:18,663 INFO [org.jboss.as.process.Server:server-two.status] (reaper for Server:server-two) WFLYPC0011: Process 'Server:server-two' finished with an exit status of 1
> [Host Controller] 09:10:18,665 INFO [org.jboss.as.host.controller] (ProcessControllerConnection-thread - 2) WFLYHC0027: Unregistering server server-two
> {noformat}
> and there is following in domain/servers/server-one/log/server.log {noformat}2019-04-09 09:04:52,385 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/subsystem=microprofile-health-smallrye' are not available:
> org.wildfly.management.http.extensible; There are no known registration points which can provide this capability.
> 2019-04-09 09:04:52,386 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/subsystem=microprofile-metrics-smallrye' are not available:
> org.wildfly.management.http.extensible; There are no known registration points which can provide this capability.
> 2019-04-09 09:04:52,389 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> 2019-04-09 09:04:52,420 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0050: WildFly Full 16.0.0.Final (WildFly Core 8.0.0.Final) stopped in 18ms{noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (WFLY-11962) Unable to start wildfly in domain mode when metrics and health extensions are enabled
by Vlasta Ramik (Jira)
Vlasta Ramik created WFLY-11962:
-----------------------------------
Summary: Unable to start wildfly in domain mode when metrics and health extensions are enabled
Key: WFLY-11962
URL: https://issues.jboss.org/browse/WFLY-11962
Project: WildFly
Issue Type: Bug
Affects Versions: 16.0.0.Final
Reporter: Vlasta Ramik
Assignee: Brian Stansberry
When WF is started in domain mode as described in steps to reproduce there is following in console {noformat}
[Host Controller] 09:10:13,260 INFO [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0023: Starting server server-one
09:10:13,396 INFO [org.jboss.as.process.Server:server-one.status] (ProcessController-threads - 3) WFLYPC0018: Starting process 'Server:server-one'
[Host Controller] 09:10:14,876 INFO [org.jboss.as.host.controller] (management task-1) WFLYHC0021: Server [Server:server-one] connected using connection [Channel ID 24b9374c (inbound) of Remoting connection 408c47e7 to localhost/127.0.0.1:38776 of endpoint "master:MANAGEMENT" <a16e023>]
[Host Controller] 09:10:14,906 INFO [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0023: Starting server server-two
[Host Controller] 09:10:14,921 INFO [org.jboss.as.host.controller] (server-registration-threads - 1) WFLYHC0020: Registering server server-one
09:10:15,031 INFO [org.jboss.as.process.Server:server-two.status] (ProcessController-threads - 3) WFLYPC0018: Starting process 'Server:server-two'
09:10:16,854 INFO [org.jboss.as.process.Server:server-one.status] (reaper for Server:server-one) WFLYPC0011: Process 'Server:server-one' finished with an exit status of 1
[Host Controller] 09:10:16,896 INFO [org.jboss.as.host.controller] (ProcessControllerConnection-thread - 2) WFLYHC0027: Unregistering server server-one
[Host Controller] 09:10:17,172 INFO [org.jboss.as.host.controller] (management task-1) WFLYHC0021: Server [Server:server-two] connected using connection [Channel ID 3d4db366 (inbound) of Remoting connection 382df477 to localhost/127.0.0.1:38794 of endpoint "master:MANAGEMENT" <a16e023>]
[Host Controller] 09:10:17,207 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0062: Http management interface listening on http://127.0.0.1:9990/management and https://127.0.0.1:-1/management
[Host Controller] 09:10:17,208 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0053: Admin console listening on http://127.0.0.1:9990 and https://127.0.0.1:-1
[Host Controller] 09:10:17,212 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 16.0.0.Final (WildFly Core 8.0.0.Final) (Host Controller) started in 6589ms - Started 79 of 81 services (23 services are lazy, passive or on-demand)
[Host Controller] 09:10:17,232 INFO [org.jboss.as.host.controller] (server-registration-threads - 1) WFLYHC0020: Registering server server-two
09:10:18,663 INFO [org.jboss.as.process.Server:server-two.status] (reaper for Server:server-two) WFLYPC0011: Process 'Server:server-two' finished with an exit status of 1
[Host Controller] 09:10:18,665 INFO [org.jboss.as.host.controller] (ProcessControllerConnection-thread - 2) WFLYHC0027: Unregistering server server-two
{noformat}
and there is following in domain/servers/server-one/log/server.log {noformat}2019-04-09 09:04:52,385 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/subsystem=microprofile-health-smallrye' are not available:
org.wildfly.management.http.extensible; There are no known registration points which can provide this capability.
2019-04-09 09:04:52,386 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/subsystem=microprofile-metrics-smallrye' are not available:
org.wildfly.management.http.extensible; There are no known registration points which can provide this capability.
2019-04-09 09:04:52,389 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
2019-04-09 09:04:52,420 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0050: WildFly Full 16.0.0.Final (WildFly Core 8.0.0.Final) stopped in 18ms{noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (WFLY-11956) @PostConstruct on @ApplicationScoped bean called too late in case @Valid is annotated on a business method
by Martin Kouba (Jira)
[ https://issues.jboss.org/browse/WFLY-11956?page=com.atlassian.jira.plugin... ]
Martin Kouba commented on WFLY-11956:
-------------------------------------
For the record: The first request actually results in 3 {{getHelloGreeting()}} invocations. Only the last one seems to be invoked upon the correct bean instance. It works as expected if the {{@Valid}} annotation is removed.
> @PostConstruct on @ApplicationScoped bean called too late in case @Valid is annotated on a business method
> ----------------------------------------------------------------------------------------------------------
>
> Key: WFLY-11956
> URL: https://issues.jboss.org/browse/WFLY-11956
> Project: WildFly
> Issue Type: Bug
> Components: Bean Validation
> Affects Versions: 16.0.0.Final
> Reporter: Joerg Baesner
> Assignee: Brian Stansberry
> Priority: Major
> Attachments: playground.zip
>
>
> Having a bean class with {{@ApplicationScoped}}, which has a {{@PostConstruct}} and is implementing the following _Interface_:
> {code}
> @Path("/validated")
> public interface ValidatedJaxRsInterface {
>
> @GET
> @Valid
> @Produces(MediaType.APPLICATION_JSON)
> GreetingModel getHelloGreeting();
> }
> {code}
> will result in calling the {{getHelloGreeting}} method of the implementation class twice *_before_* the {{@PostConstruct}} is getting executed.
> This can be reproduced with the attached reproducer application...
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (WFLY-11116) Wildfly 12.0.0 Final Delay in Getting the Value Attributes of the Session Variables (Result in Null Pointer Exception)
by ziad saade (Jira)
[ https://issues.jboss.org/browse/WFLY-11116?page=com.atlassian.jira.plugin... ]
ziad saade commented on WFLY-11116:
-----------------------------------
Hi Paul
I will test on WildFly 16.0.0.Final and provide you my feedback (Hope the issue is resolved).
Best Regards
> Wildfly 12.0.0 Final Delay in Getting the Value Attributes of the Session Variables (Result in Null Pointer Exception)
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-11116
> URL: https://issues.jboss.org/browse/WFLY-11116
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 14.0.1.Final, 12.0.0.Final, 13.0.0.Final, 15.0.0.Final
> Reporter: ziad saade
> Assignee: Paul Ferraro
> Priority: Critical
>
> I have two Servlets Book and BookPreview the attribute is set in Book Servlet as follow:
>
> Book.java
> TestBean testBean=null;
> if(session.getAttribute("testBean")!=null)
> testBean = (TestBean)session.getAttribute("testBean");
> else{
> testBean=new TestBean();
> session.setAttribute("testBean",testBean);
> }
> testBean.setAmount("10");
>
> response.sendRedirect("BookPreview");
>
>
> The session attribute can be retrieved and the page is loaded normally and the Amount value is displayed however when submitting the form (Post Action in BookPreview.java) Null Pointer exception is generated.
>
> BookPreview.java
>
> TestBean testBean = (TestBean)session.getAttribute("testBean");
> String amount = testBean.getAmount; //Null pointer exception when submitting the form
>
> <form method="Post" action="BookPreview">
>
> </form>
>
> TestBean.java
>
> public class TestBean implements java.io.Serializable {
>
> private static final long serialVersionUID = 1L;
> private String amount;
>
> public String getAmount() {
> return amount;
> }
>
> public void setAmount(String amount) {
> this.amount = amount;
> }
> }
>
> Kindly advice how to fix the problem at the level of the server configuration.
> PS: I am not getting the exception when deploying the same application under other J EE application servers (Tomcat....)
>
> Thanks and Best Regards
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (SWSQE-701) Get code coverage for system tests
by Filip Brychta (Jira)
[ https://issues.jboss.org/browse/SWSQE-701?page=com.atlassian.jira.plugin.... ]
Filip Brychta reopened SWSQE-701:
---------------------------------
https://github.com/kiali/kiali/pull/974 introduces operator which requires different approach
> Get code coverage for system tests
> ----------------------------------
>
> Key: SWSQE-701
> URL: https://issues.jboss.org/browse/SWSQE-701
> Project: Kiali QE
> Issue Type: Sub-task
> Reporter: Filip Brychta
> Assignee: Filip Brychta
> Priority: Major
> Labels: infrastructure
>
> # add main go test file which will basically just call main() function to start kiali
> # compile kiali in "code coverage ready" way: go test -c -covermode=count -coverpkg ./...
> # use this binary to create kiali docker image
> # start this docker image with following params: -systemTest
> -test.coverprofile /opt/kiali/console/coverage.cov
> # run tests
> # kill kiali in a graceful way (after this step the coverage report should be generated)
> # get report from docker container
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (WFLY-6918) Unnecessary NoSuchMethodException during JSF app deployment
by Chao Wang (Jira)
[ https://issues.jboss.org/browse/WFLY-6918?page=com.atlassian.jira.plugin.... ]
Chao Wang updated WFLY-6918:
----------------------------
Affects Version/s: 16.0.0.Final
> Unnecessary NoSuchMethodException during JSF app deployment
> ------------------------------------------------------------
>
> Key: WFLY-6918
> URL: https://issues.jboss.org/browse/WFLY-6918
> Project: WildFly
> Issue Type: Bug
> Components: JSF
> Affects Versions: 10.0.0.Final, 10.1.0.CR1, 16.0.0.Final
> Environment: it's same at current master
> Reporter: Tomas Remes
> Assignee: Farah Juma
> Priority: Minor
>
> When you turn on TRACE logging for {{javax.enterprise.resource}} then you can notice following exception during JSF app deployment:
> {noformat}
> [javax.enterprise.resource.webcontainer.jsf.application] (ServerService Thread Pool -- 69) java.lang.NoSuchMethodException: org.jboss.as.jsf.injection.JandexAnnotationProvider.<init>(javax.servlet.ServletContext, com.sun.faces.spi.AnnotationProvider): java.lang.NoSuchMethodException: org.jboss.as.jsf.injection.JandexAnnotationProvider.<init>(javax.servlet.ServletContext, com.sun.faces.spi.AnnotationProvider)
> at java.lang.Class.getConstructor0(Class.java:3082)
> at java.lang.Class.getDeclaredConstructor(Class.java:2178)
> at com.sun.faces.spi.ServiceFactoryUtils.getProviderFromEntry(ServiceFactory.java:83)
> at com.sun.faces.spi.AnnotationProviderFactory.createAnnotationProvider(AnnotationProviderFactory.java:70)
> at com.sun.faces.config.ConfigManager$AnnotationScanTask.<init>(ConfigManager.java:931)
> at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:385)
> at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:227)
> at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:187)
> at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:200)
> at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:171)
> at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:42)
> at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
> at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44)
> at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44)
> at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44)
> at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44)
> at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44)
> at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:234)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:100)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:82)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> {noformat}
> Problem is that {{org.jboss.as.jsf.injection.JandexAnnotationProvider}} doesn't have corresponding constructor (with two params - javax.servlet.ServletContext, com.sun.faces.spi.AnnotationProvider)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month