[JBoss JIRA] (WFLY-11715) The layers testsuite should use thin servers
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-11715?page=com.atlassian.jira.plugin... ]
Brian Stansberry reassigned WFLY-11715:
---------------------------------------
Assignee: Jean-Francois Denise (was: Brian Stansberry)
> The layers testsuite should use thin servers
> --------------------------------------------
>
> Key: WFLY-11715
> URL: https://issues.jboss.org/browse/WFLY-11715
> Project: WildFly
> Issue Type: Enhancement
> Components: Test Suite
> Reporter: Brian Stansberry
> Assignee: Jean-Francois Denise
> Priority: Major
>
> The layers testsuite is provisioning a bunch of different servers. It should use thin servers (i.e. jars in the maven repo, not in the modules dirs) as it's not validating anything that differs between a thin and fat server. This will reduce the disk io and peak FS space requirements on the CI servers.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-11718) MicroProfileMetricsHistogramMultipleInvocationsTestCase fails intermittently
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-11718?page=com.atlassian.jira.plugin... ]
Brian Stansberry updated WFLY-11718:
------------------------------------
Summary: MicroProfileMetricsHistogramMultipleInvocationsTestCase fails intermittently (was: Ignore MicroProfileMetricsHistogramMultipleInvocationsTestCase)
> MicroProfileMetricsHistogramMultipleInvocationsTestCase fails intermittently
> ----------------------------------------------------------------------------
>
> Key: WFLY-11718
> URL: https://issues.jboss.org/browse/WFLY-11718
> Project: WildFly
> Issue Type: Bug
> Components: MP Metrics
> Affects Versions: 16.0.0.Beta1
> Reporter: Jeff Mesnil
> Assignee: Jeff Mesnil
> Priority: Major
>
> Test org.wildfly.test.integration.microprofile.metrics.metadata.MicroProfileMetricsHistogramMultipleInvocationsTestCase.testMultipleInvocationsOfEndpoint is failing intermittently.
> @Ignore-it until it is fix to consistently pass.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-11716) Deployment Fails with @Transactional in Passivating Scope Bean
by Cody Lerum (Jira)
[ https://issues.jboss.org/browse/WFLY-11716?page=com.atlassian.jira.plugin... ]
Cody Lerum commented on WFLY-11716:
-----------------------------------
The attached project will fail to deploy as a war on 16.0.0.Beta1
> Deployment Fails with @Transactional in Passivating Scope Bean
> --------------------------------------------------------------
>
> Key: WFLY-11716
> URL: https://issues.jboss.org/browse/WFLY-11716
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 16.0.0.Beta1
> Environment: Java 8, Ubuntu Xenial
> Reporter: Cody Lerum
> Assignee: Brian Stansberry
> Priority: Major
> Attachments: jsf-npe.zip
>
>
> On Wildfly 16.0.0.Beta1 deployment fails
> {code}
> org.jboss.weld.exceptions.UnserializableDependencyException: WELD-001477: The bean Managed Bean [class co.cfly.oss.lerg.rateCenter.inventoryRequest.InventoryRequestView] with qualifiers [@Default @Any @Named] declares a passivating scope but has a(n) Interceptor [class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorRequired intercepts @Transactional] with a non-passivation-capable dependency com.arjuna.ats.jta.cdi.JNDIBean@12e2cb9f
> at org.jboss.weld.bootstrap.Validator.validateInterceptorDecoratorInjectionPointPassivationCapable(Validator.java:480)
> at org.jboss.weld.bootstrap.Validator.validateInterceptors(Validator.java:225)
> at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:175)
> at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:526)
> at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:64)
> at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:62)
> at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:62)
> at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:55)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:485)
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-11716) Deployment Fails with @Transactional in Passivating Scope Bean
by Cody Lerum (Jira)
[ https://issues.jboss.org/browse/WFLY-11716?page=com.atlassian.jira.plugin... ]
Cody Lerum updated WFLY-11716:
------------------------------
Attachment: jsf-npe.zip
> Deployment Fails with @Transactional in Passivating Scope Bean
> --------------------------------------------------------------
>
> Key: WFLY-11716
> URL: https://issues.jboss.org/browse/WFLY-11716
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 16.0.0.Beta1
> Environment: Java 8, Ubuntu Xenial
> Reporter: Cody Lerum
> Assignee: Brian Stansberry
> Priority: Major
> Attachments: jsf-npe.zip
>
>
> On Wildfly 16.0.0.Beta1 deployment fails
> {code}
> org.jboss.weld.exceptions.UnserializableDependencyException: WELD-001477: The bean Managed Bean [class co.cfly.oss.lerg.rateCenter.inventoryRequest.InventoryRequestView] with qualifiers [@Default @Any @Named] declares a passivating scope but has a(n) Interceptor [class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorRequired intercepts @Transactional] with a non-passivation-capable dependency com.arjuna.ats.jta.cdi.JNDIBean@12e2cb9f
> at org.jboss.weld.bootstrap.Validator.validateInterceptorDecoratorInjectionPointPassivationCapable(Validator.java:480)
> at org.jboss.weld.bootstrap.Validator.validateInterceptors(Validator.java:225)
> at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:175)
> at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:526)
> at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:64)
> at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:62)
> at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:62)
> at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:55)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:485)
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-11720) Cannot invoke EJB over HTTP on JDK 11
by David Lloyd (Jira)
[ https://issues.jboss.org/browse/WFLY-11720?page=com.atlassian.jira.plugin... ]
David Lloyd commented on WFLY-11720:
------------------------------------
As I always say: I never have a plan to release anything, but if anyone ever wants a tag for any reason, give me a ping a day or two in advance (more if there are PRs to consider).
> Cannot invoke EJB over HTTP on JDK 11
> -------------------------------------
>
> Key: WFLY-11720
> URL: https://issues.jboss.org/browse/WFLY-11720
> Project: WildFly
> Issue Type: Bug
> Components: EJB, Remoting
> Affects Versions: 16.0.0.Beta1
> Environment: JDK 11
> Reporter: Jan Kašík
> Priority: Major
>
> Run of client app calling EJB over HTTP fails on JDK 11 with following log:
> {noformat}
> Feb 14, 2019 12:49:30 PM org.wildfly.naming.client.Version <clinit>
> INFO: WildFly Naming version 1.0.6.Final
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by org.wildfly.security.manager.GetAccessibleDeclaredFieldAction (file:/home/hudson/hudson_workspace/mod_cluster/client/wildfly-elytron-1.1.3.Final.jar) to field java.security.AccessControlContext.context
> WARNING: Please consider reporting this to the maintainers of org.wildfly.security.manager.GetAccessibleDeclaredFieldAction
> WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> Feb 14, 2019 12:49:30 PM org.wildfly.security.Version <clinit>
> INFO: ELY00001: WildFly Elytron version 1.1.3.Final
> Feb 14, 2019 12:49:30 PM org.jboss.ejb.client.EJBClient <clinit>
> INFO: JBoss EJB Client version 4.0.2.Final
> Feb 14, 2019 12:49:30 PM org.xnio.Xnio <clinit>
> INFO: XNIO version 3.6.5.Final
> Feb 14, 2019 12:49:30 PM org.xnio.nio.NioXnio <clinit>
> INFO: XNIO NIO Implementation Version 3.6.5.Final
> Feb 14, 2019 12:49:30 PM org.jboss.threads.Version <clinit>
> INFO: JBoss Threads version 2.3.0.Beta2
> Feb 14, 2019 12:49:30 PM org.jboss.remoting3.EndpointImpl <clinit>
> INFO: JBoss Remoting version 5.0.0.Final
> Feb 14, 2019 12:49:30 PM org.jboss.threads.LoggingUncaughtExceptionHandler uncaughtException
> ERROR: Thread Thread[XNIO-1 task-1,5,main] threw an uncaught exception
> java.lang.ExceptionInInitializerError
> at org.jboss.marshalling.river.RiverMarshaller.<clinit>(RiverMarshaller.java:1335)
> at org.jboss.marshalling.river.RiverMarshallerFactory.createMarshaller(RiverMarshallerFactory.java:54)
> at org.wildfly.httpclient.common.HttpTargetContext.createMarshaller(HttpTargetContext.java:132)
> at org.wildfly.httpclient.ejb.HttpEJBReceiver.marshalEJBRequest(HttpEJBReceiver.java:367)
> at org.wildfly.httpclient.ejb.HttpEJBReceiver.lambda$processInvocation$1(HttpEJBReceiver.java:185)
> at org.wildfly.httpclient.common.HttpTargetContext$1.lambda$completed$0(HttpTargetContext.java:338)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1871)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1400)
> at java.base/java.lang.Thread.run(Thread.java:834)
> Caused by: java.lang.IllegalStateException: No standard field found for reverse order comparator!
> at org.jboss.marshalling.river.Protocol.<clinit>(Protocol.java:287)
> ... 9 more
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-11724) Add 'allowed' and 'unit' data to the wildscribe output
by Brian Stansberry (Jira)
Brian Stansberry created WFLY-11724:
---------------------------------------
Summary: Add 'allowed' and 'unit' data to the wildscribe output
Key: WFLY-11724
URL: https://issues.jboss.org/browse/WFLY-11724
Project: WildFly
Issue Type: Enhancement
Components: Documentation, Management
Reporter: Brian Stansberry
Assignee: James Perkins
Input from [~ahoffer] is it would be good to add the 'allowed' and 'unit' management attribute/operation parameter descriptors to the wildscribe output.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-11275) JSF ViewMap Regression
by Cody Lerum (Jira)
[ https://issues.jboss.org/browse/WFLY-11275?page=com.atlassian.jira.plugin... ]
Cody Lerum commented on WFLY-11275:
-----------------------------------
I can confirm this is fixed in WF 16.0.0.Beta1
> JSF ViewMap Regression
> ----------------------
>
> Key: WFLY-11275
> URL: https://issues.jboss.org/browse/WFLY-11275
> Project: WildFly
> Issue Type: Bug
> Components: JSF
> Affects Versions: 14.0.1.Final, 15.0.0.Final, 15.0.1.Final
> Environment: Java 8
> Wildfly 14.0.1
> Reporter: Cody Lerum
> Assignee: Dmitrii Tikhomirov
> Priority: Major
> Fix For: 16.0.0.Beta1
>
>
> I'm been running into an occasional NPE in production with JSF after migrating from Wildfly 11 to Wildfly 14.0.1 ( Mojarra 2.2.13.SP4 -> 2.3.5.SP2 ) and I believe I've tracked down a small demo project that duplicates the issue. I've set the project to JSF 2.2 so it will deploy on both WF 11 and WF 14.
> The basic problem is that when two pages with the same view id are loaded in separate tabs. From there is one of the tabs is posted and the result navigates to a different view id all references to that view id are removed from the view map. If the post does not navigate to a different view id then all works normally.
> My assumption is that when the post navigates away to a new view id any reference to any page with the same view id is removed from the view map. This did not occur in Wildfly 11.
> Additional clue is that even though the viewmap reference is removed the view scoped beans referencing it are not destroyed.
> Demo project at https://github.com/codylerum/demos/tree/ee7/jsf-npe
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-11720) Cannot invoke EJB over HTTP on JDK 11
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-11720?page=com.atlassian.jira.plugin... ]
Brian Stansberry commented on WFLY-11720:
-----------------------------------------
[~tomekadamski] [~cfang] or [~flavia.rainone] could one of you take this? I don't know if [~dmlloyd] or anyone has any plan to release a JBoss Marshalling 2.1.0 in time for WF 16 Final. It looks like the issues assigned to it are all resolved except for 1 which has a PR.
> Cannot invoke EJB over HTTP on JDK 11
> -------------------------------------
>
> Key: WFLY-11720
> URL: https://issues.jboss.org/browse/WFLY-11720
> Project: WildFly
> Issue Type: Bug
> Components: EJB, Remoting
> Affects Versions: 16.0.0.Beta1
> Environment: JDK 11
> Reporter: Jan Kašík
> Priority: Major
>
> Run of client app calling EJB over HTTP fails on JDK 11 with following log:
> {noformat}
> Feb 14, 2019 12:49:30 PM org.wildfly.naming.client.Version <clinit>
> INFO: WildFly Naming version 1.0.6.Final
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by org.wildfly.security.manager.GetAccessibleDeclaredFieldAction (file:/home/hudson/hudson_workspace/mod_cluster/client/wildfly-elytron-1.1.3.Final.jar) to field java.security.AccessControlContext.context
> WARNING: Please consider reporting this to the maintainers of org.wildfly.security.manager.GetAccessibleDeclaredFieldAction
> WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> Feb 14, 2019 12:49:30 PM org.wildfly.security.Version <clinit>
> INFO: ELY00001: WildFly Elytron version 1.1.3.Final
> Feb 14, 2019 12:49:30 PM org.jboss.ejb.client.EJBClient <clinit>
> INFO: JBoss EJB Client version 4.0.2.Final
> Feb 14, 2019 12:49:30 PM org.xnio.Xnio <clinit>
> INFO: XNIO version 3.6.5.Final
> Feb 14, 2019 12:49:30 PM org.xnio.nio.NioXnio <clinit>
> INFO: XNIO NIO Implementation Version 3.6.5.Final
> Feb 14, 2019 12:49:30 PM org.jboss.threads.Version <clinit>
> INFO: JBoss Threads version 2.3.0.Beta2
> Feb 14, 2019 12:49:30 PM org.jboss.remoting3.EndpointImpl <clinit>
> INFO: JBoss Remoting version 5.0.0.Final
> Feb 14, 2019 12:49:30 PM org.jboss.threads.LoggingUncaughtExceptionHandler uncaughtException
> ERROR: Thread Thread[XNIO-1 task-1,5,main] threw an uncaught exception
> java.lang.ExceptionInInitializerError
> at org.jboss.marshalling.river.RiverMarshaller.<clinit>(RiverMarshaller.java:1335)
> at org.jboss.marshalling.river.RiverMarshallerFactory.createMarshaller(RiverMarshallerFactory.java:54)
> at org.wildfly.httpclient.common.HttpTargetContext.createMarshaller(HttpTargetContext.java:132)
> at org.wildfly.httpclient.ejb.HttpEJBReceiver.marshalEJBRequest(HttpEJBReceiver.java:367)
> at org.wildfly.httpclient.ejb.HttpEJBReceiver.lambda$processInvocation$1(HttpEJBReceiver.java:185)
> at org.wildfly.httpclient.common.HttpTargetContext$1.lambda$completed$0(HttpTargetContext.java:338)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1871)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1400)
> at java.base/java.lang.Thread.run(Thread.java:834)
> Caused by: java.lang.IllegalStateException: No standard field found for reverse order comparator!
> at org.jboss.marshalling.river.Protocol.<clinit>(Protocol.java:287)
> ... 9 more
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months