February 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-2281) Add wildfly-elytron.tool.jar to bin

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-2281: ---------------------------------------- Summary: Add wildfly-elytron.tool.jar to bin Key: WFCORE-2281 URL: https://issues.jboss.org/browse/WFCORE-2281 Project: WildFly Core Issue Type: Feature Request Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 3.0.0.Alpha25 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8065) Upgrade IronJacamar to 1.4.2 from 1.4.1

by Stefano Maestri (JIRA)

[ https://issues.jboss.org/browse/WFLY-8065?page=com.atlassian.jira.plugin.... ] Stefano Maestri moved JBEAP-8753 to WFLY-8065: ---------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-8065 (was: JBEAP-8753) Issue Type: Task (was: Component Upgrade) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: JCA (was: JCA) Target Release: (was: 7.1.0.GA) > Upgrade IronJacamar to 1.4.2 from 1.4.1 > --------------------------------------- > > Key: WFLY-8065 > URL: https://issues.jboss.org/browse/WFLY-8065 > Project: WildFly > Issue Type: Task > Components: JCA > Reporter: Stefano Maestri > Assignee: Stefano Maestri > > This is needed to adjust the SPI needed for the Elytron integration for the three JCA subsystems -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1418) Binding of List stored in Map doesn't work in special case

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1418?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-1418: -------------------------------- Labels: dtable_testday_preparation qe-test-day reported-by-qe (was: dtable_testday_preparation reported-by-qe) > Binding of List stored in Map doesn't work in special case > ---------------------------------------------------------- > > Key: DROOLS-1418 > URL: https://issues.jboss.org/browse/DROOLS-1418 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.0.0.Beta5 > Reporter: Jozef Marko > Assignee: Mario Fusco > Labels: dtable_testday_preparation, qe-test-day, reported-by-qe > Fix For: 7.0.0.CR1 > > Attachments: reproducer.zip > > > User has possibility to bind a List stored as item of a Map in his rule. However this dosn't work in one special case. For more details see the steps to reproduce. > This issue was discussed with [~tari_manga] and he also provided the workaround used in reproducer. Thanks. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1789) PreparedResponseTestCase from wf-core-eap fails intermittently

by Michal Jurc (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1789?page=com.atlassian.jira.plugi... ] Michal Jurc commented on WFCORE-1789: ------------------------------------- PR submitted: https://github.com/wildfly/wildfly-core/pull/2165 > PreparedResponseTestCase from wf-core-eap fails intermittently > -------------------------------------------------------------- > > Key: WFCORE-1789 > URL: https://issues.jboss.org/browse/WFCORE-1789 > Project: WildFly Core > Issue Type: Bug > Components: Test Suite > Affects Versions: 3.0.0.Alpha7 > Reporter: ehsavoie Hugonnet > Assignee: ehsavoie Hugonnet > Fix For: 3.0.0.Alpha9 > > Attachments: firefox.desktop > > > *Description of problem:* > PreparedResponseTestCase from wf-core-eap fails intermittently with two different stack-trace > *How reproducible:* > 2% > *Actual results: (1. issue)* > Stack Trace: > {noformat} > java.lang.AssertionError: null > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertTrue(Assert.java:52) > at org.wildfly.core.test.standalone.mgmt.PreparedResponseTestCase.reloadServer(PreparedResponseTestCase.java:113) > {noformat} > Standard Output: > {noformat} > &amp#27;[0m01:34:22,658 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0028: Stopped deployment slow-stop.jar (runtime-name: slow-stop.jar) in 3025ms > &amp#27;[0m&amp#27;[0m01:34:22,701 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0050: WildFly Core 3.0.0.Alpha4-redhat-1 "Kenny" stopped in 3071ms > &amp#27;[0m&amp#27;[0m01:34:22,710 INFO [org.jboss.as] (MSC service thread 1-5) WFLYSRV0049: WildFly Core 3.0.0.Alpha4-redhat-1 "Kenny" starting > &amp#27;[0m&amp#27;[0m01:34:23,243 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http) > &amp#27;[0m&amp#27;[0m01:34:23,331 INFO [org.jboss.as.patching] (MSC service thread 1-4) WFLYPAT0050: WildFly cumulative patch ID is: base, one-off patches include: none > &amp#27;[0m&amp#27;[33m01:34:23,361 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-3) WFLYDM0111: Keystore /mnt/hudson_workspace/workspace/eap-7x-as-testsuite-test-core-rhel/19de6045/testsuite/manualmode/target/wildfly-core/standalone/configuration/application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost > &amp#27;[0m&amp#27;[33m01:34:23,355 WARN [org.jboss.as.domain.http.api.undertow] (MSC service thread 1-1) WFLYDMHTTP0003: Unable to load console module for slot main, disabling console > &amp#27;[0m&amp#27;[0m01:34:23,367 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "slow-stop.jar" (runtime-name: "slow-stop.jar") > &amp#27;[0m&amp#27;[33m01:34:23,449 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) WFLYSRV0018: Deployment "deployment.slow-stop.jar" is using a private module ("org.jboss.as.controller:main") which may be changed or removed in future versions without notice. > &amp#27;[0m&amp#27;[33m01:34:23,450 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) WFLYSRV0018: Deployment "deployment.slow-stop.jar" is using a private module ("org.jboss.as.server:main") which may be changed or removed in future versions without notice. > &amp#27;[0m&amp#27;[33m01:34:23,452 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) WFLYSRV0018: Deployment "deployment.slow-stop.jar" is using a private module ("org.wildfly.extension.request-controller:main") which may be changed or removed in future versions without notice. > &amp#27;[0m&amp#27;[33m01:34:23,453 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) WFLYSRV0018: Deployment "deployment.slow-stop.jar" is using a private module ("org.jboss.as.network:main") which may be changed or removed in future versions without notice. > &amp#27;[0m&amp#27;[0m01:34:23,479 INFO [org.wildfly.test.shutdown.SlowStopService] (MSC service thread 1-7) Started with a stop duration of 3000 ms > &amp#27;[0m&amp#27;[0m01:34:23,528 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Deployed "slow-stop.jar" (runtime-name : "slow-stop.jar") > &amp#27;[0m > {noformat} > *Actual results: (2. issue)* > Stack Trace: > {noformat} > java.lang.RuntimeException: java.io.IOException: java.util.concurrent.CancellationException: Operation was cancelled > at org.jboss.threads.AsyncFutureTask.operationCancelled(AsyncFutureTask.java:70) > at org.jboss.threads.AsyncFutureTask.get(AsyncFutureTask.java:267) > at org.jboss.as.controller.client.impl.AbstractDelegatingAsyncFuture.get(AbstractDelegatingAsyncFuture.java:57) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:147) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:75) > at org.wildfly.core.testrunner.ManagementClient.executeForResult(ManagementClient.java:234) > at org.wildfly.core.test.standalone.mgmt.PreparedResponseTestCase.reloadServer(PreparedResponseTestCase.java:102) > {noformat} > Standard Output: > {noformat} > 11:03:28,015 WARN [org.jboss.as.protocol.connection] (Remoting "management-client" task-5) WFLYPRT0018: No such request (1) associated with channel Channel ID a37ddd63 (outbound) of Remoting connection 68823cff to /10.16.180.146:9990 of endpoint "management-client" <6645cf9f> > {noformat} > *Expected results:* > No errors > *Additional info:* > Links to jenkins results: > * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP7/view/EAP7-AS-T... > * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-as-testsuite-... > * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-as-testsuite-... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2280) Legacy security realms need to reference the client cert mechanism with an underscore

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-2280: ---------------------------------------- Summary: Legacy security realms need to reference the client cert mechanism with an underscore Key: WFCORE-2280 URL: https://issues.jboss.org/browse/WFCORE-2280 Project: WildFly Core Issue Type: Bug Components: Domain Management, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 3.0.0.Alpha25 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8064) Dependecy Injection not working

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-8064?page=com.atlassian.jira.plugin.... ] Tomaz Cerar commented on WFLY-8064: ----------------------------------- reproducer? > Dependecy Injection not working > ------------------------------- > > Key: WFLY-8064 > URL: https://issues.jboss.org/browse/WFLY-8064 > Project: WildFly > Issue Type: Release > Components: CDI / Weld > Affects Versions: 10.0.0.Final > Environment: Windows 2012 R2 > Reporter: Pradeep Ganapathy > Assignee: Stuart Douglas > > All injected parameters after post construct are null. Jboss cant able to detect inject paramaters. Both dao and testDescription parameters are null. As a result null pointer exception > RestEasy versions(All) ----> 3.0.14.Final. > ApplicationScoped > public class TestImpl implements ITest > { > > @Inject > private ITestDAO dao; > public TestImpl setTestDAO(ITestDAO dao) > { > this.dao = dao; > return this; > } > @Inject > private TestDescription testDescription; > public TestImpl setTestDescription(TestDescription testDescription) > { > this.testDescription = testDescription; > return this; > } > } > Error Logs: > 2017-02-09 13:11:22,256 ERROR [io.undertow.request] (default task-128) UT005023: Exception handling request to( My EndPoint): org.jboss.resteasy.spi.UnhandledException: java.lang.NullPointerException > Caused by: java.lang.NullPointerException > at ServiceRegistryImpl.lookup(ServiceRegistryImpl.java:142) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:139) > at org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:295) > at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:249) > at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:236) > at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:395) > ... 35 more -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2272) Ctrl-C sent on command taking long time doesn't cancel the current operation

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2272?page=com.atlassian.jira.plugi... ] Jean-Francois Denise commented on WFCORE-2272: ---------------------------------------------- Whatever the timeout being set or not, DMR requests are asynchronous. The running task is kept, ready to be canceled if Interrupt occurs. > Ctrl-C sent on command taking long time doesn't cancel the current operation > ---------------------------------------------------------------------------- > > Key: WFCORE-2272 > URL: https://issues.jboss.org/browse/WFCORE-2272 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > > For example, during a deploy that takes time, a user types Ctrl-C, this does unlock the prompt and the command "seems" to have been interrupted. Actually the command thread has been interrupted but not the remoting task that is in progress. So although the user can think its command has been aborted, it is silently processing in background. > When interruption occurs in a command thread, current remoting task should be canceled. This is what we are doing today when a timeout is set on a command. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2272) Ctrl-C sent on command taking long time doesn't cancel the current operation

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2272?page=com.atlassian.jira.plugi... ] Jean-Francois Denise commented on WFCORE-2272: ---------------------------------------------- Implementation in private branch: https://github.com/jfdenise/wildfly-core/commit/396713ed65c51fb1fc9b46da4... > Ctrl-C sent on command taking long time doesn't cancel the current operation > ---------------------------------------------------------------------------- > > Key: WFCORE-2272 > URL: https://issues.jboss.org/browse/WFCORE-2272 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > > For example, during a deploy that takes time, a user types Ctrl-C, this does unlock the prompt and the command "seems" to have been interrupted. Actually the command thread has been interrupted but not the remoting task that is in progress. So although the user can think its command has been aborted, it is silently processing in background. > When interruption occurs in a command thread, current remoting task should be canceled. This is what we are doing today when a timeout is set on a command. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2271) CLI should use Endpoint executor

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2271?page=com.atlassian.jira.plugi... ] Jean-Francois Denise commented on WFCORE-2271: ---------------------------------------------- Implementation in private branch: https://github.com/jfdenise/wildfly-core/commit/82343adc9d07b5f2b5054a1ab... > CLI should use Endpoint executor > -------------------------------- > > Key: WFCORE-2271 > URL: https://issues.jboss.org/browse/WFCORE-2271 > Project: WildFly Core > Issue Type: Enhancement > Components: CLI > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > > Today the 16 threads (default value) of the ThreadPool attached to the Endpoint are started and never used (except during connection of Controller client). > CLI, instead of instantiating and managing its own Executor, it should re-use the XNIO one and configure its size the way the CLI custom one does. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8064) Dependecy Injection not working

by Pradeep Ganapathy (JIRA)

Pradeep Ganapathy created WFLY-8064: --------------------------------------- Summary: Dependecy Injection not working Key: WFLY-8064 URL: https://issues.jboss.org/browse/WFLY-8064 Project: WildFly Issue Type: Release Components: CDI / Weld Affects Versions: 10.0.0.Final Environment: Windows 2012 R2 Reporter: Pradeep Ganapathy Assignee: Stuart Douglas All injected parameters after post construct are null. Jboss cant able to detect inject paramaters. Both dao and testDescription parameters are null. As a result null pointer exception RestEasy versions(All) ----> 3.0.14.Final. ApplicationScoped public class TestImpl implements ITest { @Inject private ITestDAO dao; public TestImpl setTestDAO(ITestDAO dao) { this.dao = dao; return this; } @Inject private TestDescription testDescription; public TestImpl setTestDescription(TestDescription testDescription) { this.testDescription = testDescription; return this; } } Error Logs: 2017-02-09 13:11:22,256 ERROR [io.undertow.request] (default task-128) UT005023: Exception handling request to( My EndPoint): org.jboss.resteasy.spi.UnhandledException: java.lang.NullPointerException Caused by: java.lang.NullPointerException at ServiceRegistryImpl.lookup(ServiceRegistryImpl.java:142) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:139) at org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:295) at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:249) at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:236) at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:395) ... 35 more -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2017