July 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-587) Wildfly does not log stack trace of an exception

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-587?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-587: ------------------------------------------------ Jan Martiska <jmartisk(a)redhat.com> changed the Status of [bug 1198186|https://bugzilla.redhat.com/show_bug.cgi?id=1198186] from ON_QA to VERIFIED > Wildfly does not log stack trace of an exception > ------------------------------------------------ > > Key: WFCORE-587 > URL: https://issues.jboss.org/browse/WFCORE-587 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Affects Versions: 1.0.0.Alpha19 > Reporter: Tomas Hofman > Assignee: Tomas Hofman > > Copied from BZ 1198186: > AbstractOperationContext.java line 1159 seems to be "swallowing" exceptions. It's possible to get NullPointerException without a stack trace. This makes it impossible to trace the cause of the NPE. > https://github.com/jbossas/jboss-eap/blob/2292b0a8763683d0fab03efc3de6a29... > 2015-02-27 12:53:26,587 TRACE [|] [org.jboss.modules] (MSC service thread 1-11) Finding class org.jboss.logging.DelegatingBasicLogger from Module "org.picketbox:main" from local module loader @416a8198 (finder: local module finder @376243b5 (roots: /usr/share/jbossas/modules,/usr/share/jbossas/modules/system/layers/base)) > 2015-02-27 12:53:26,586 ERROR [|] [org.jboss.as.controller.client] (ServerService Thread Pool -- 29) JBAS014781: Step handler org.jboss.as.controller.AbstractAddStepHandler$1@1e6a7c88 for operation {"operation" => "add","factory-class" => "org.hornetq.core.remoting.impl.netty.NettyConnectorFactory","param" => [("host" => "tp4.app.paypoint.net"),("port" => "6495"),("use-nio" => "true")],"address" => [("subsystem" => "messaging"),("hornetq-server" => "default"),("connector" => "tp4")],"socket-binding" => undefined} at address [ > ("subsystem" => "messaging"), > ("hornetq-server" => "default"), > ("connector" => "tp4") > ] failed handling operation rollback -- java.lang.NullPointerException > 2015-02-27 12:53:26,587 TRACE [|] [org.jboss.modules] (MSC service thread 1-4) Finding class org.jboss.remoting3.UnlockedReadHashMap$EntryIterator from Module "org.jboss.remoting3:main" from local module loader @416a8198 (finder: local module finder @376243b5 (roots: /usr/share/jbossas/modules,/usr/share/jbossas/modules/system/layers/base)) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-248) Loopback addresses in the range 127.0.0.2 - 127.255.255.255 should be supported

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-248?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-248: ---------------------------------------------- Jan Martiska <jmartisk(a)redhat.com> changed the Status of [bug 1227847|https://bugzilla.redhat.com/show_bug.cgi?id=1227847] from ON_QA to VERIFIED > Loopback addresses in the range 127.0.0.2 - 127.255.255.255 should be supported > ------------------------------------------------------------------------------- > > Key: WFLY-248 > URL: https://issues.jboss.org/browse/WFLY-248 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management > Environment: Linux Fedora 13 > Reporter: Bela Ban > Assignee: Rostislav Svoboda > Fix For: 8.0.0.Alpha3 > > > When starting JBoss like this: "standalone.sh -b 127.0.0.2 -c standalone-ha.xml", the startup fails because 127.0.0.2 cannot be resolved. > However, a loopback address should be recognized even if it doesn't resolve to an interface. The code below works for example: > {code} > InetAddress addr=InetAddress.getByName("127.0.0.5"); > boolean is_loopback=addr.isLoopback(); // should be true > {code} > Loopback addresses are very useful for local testing, ie. starting of multiple JBoss instances on the same box. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5038) Update MutableDetector to include immutable classes introduced in Java 8

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-5038?page=com.atlassian.jira.plugin.... ] Paul Ferraro updated WFLY-5038: ------------------------------- Description: e.g. java.time.* > Update MutableDetector to include immutable classes introduced in Java 8 > ------------------------------------------------------------------------ > > Key: WFLY-5038 > URL: https://issues.jboss.org/browse/WFLY-5038 > Project: WildFly > Issue Type: Enhancement > Components: Clustering > Affects Versions: 10.0.0.Alpha6 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > > e.g. > java.time.* -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5038) Update MutableDetector to include immutable classes introduced in Java 8

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-5038?page=com.atlassian.jira.plugin.... ] Paul Ferraro updated WFLY-5038: ------------------------------- Summary: Update MutableDetector to include immutable classes introduced in Java 8 (was: Update org.wildfly.clustering.web.infinispan.session.MutableDetector to include immutable classes introduced in Java 8) > Update MutableDetector to include immutable classes introduced in Java 8 > ------------------------------------------------------------------------ > > Key: WFLY-5038 > URL: https://issues.jboss.org/browse/WFLY-5038 > Project: WildFly > Issue Type: Enhancement > Components: Clustering > Affects Versions: 10.0.0.Alpha6 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5038) Update org.wildfly.clustering.web.infinispan.session.MutableDetector to include immutable classes introduced in Java 8

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-5038?page=com.atlassian.jira.plugin.... ] Paul Ferraro updated WFLY-5038: ------------------------------- Summary: Update org.wildfly.clustering.web.infinispan.session.MutableDetector to include immutable classes introduced in Java 8 (was: Update org.wildfly.clustering.web.infinispan.session.MutableDetector to include new immutable classes Java 8) > Update org.wildfly.clustering.web.infinispan.session.MutableDetector to include immutable classes introduced in Java 8 > ---------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-5038 > URL: https://issues.jboss.org/browse/WFLY-5038 > Project: WildFly > Issue Type: Enhancement > Components: Clustering > Affects Versions: 10.0.0.Alpha6 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5038) Update org.wildfly.clustering.web.infinispan.session.MutableDetector to include new immutable classes Java 8

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-5038: ---------------------------------- Summary: Update org.wildfly.clustering.web.infinispan.session.MutableDetector to include new immutable classes Java 8 Key: WFLY-5038 URL: https://issues.jboss.org/browse/WFLY-5038 Project: WildFly Issue Type: Enhancement Components: Clustering Affects Versions: 10.0.0.Alpha6 Reporter: Paul Ferraro Assignee: Paul Ferraro -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-846) Some tests throws "Permission check failed" while run with security manager

by Hynek Mlnařík (JIRA)

[ https://issues.jboss.org/browse/WFCORE-846?page=com.atlassian.jira.plugin... ] Hynek Mlnařík reassigned WFCORE-846: ------------------------------------ Assignee: Jan Tymel (was: Josef Cacek) > Some tests throws "Permission check failed" while run with security manager > --------------------------------------------------------------------------- > > Key: WFCORE-846 > URL: https://issues.jboss.org/browse/WFCORE-846 > Project: WildFly Core > Issue Type: Bug > Components: Test Suite > Affects Versions: 2.0.0.Alpha11 > Reporter: Petr Kremensky > Assignee: Jan Tymel > > Some tests are failing to deploy an archive when testsuite run with security manager enabled. > {noformat} > 08:03:07,171 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service test.deployment.trivial: org.jboss.msc.service.StartException in service test.deployment.trivial: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) > 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) > Caused by: java.security.AccessControlException: WFSM000001: Permission check failed (permission "("java.util.PropertyPermission" "test.deployment.trivial.prop" "write")" in code source "(vfs:/content/test-http-deployment.sar <no signer certificates>)" of "null") > at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:274) > at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:176) > at java.lang.System.setProperty(System.java:792) > at org.jboss.as.test.deployment.trivial.ServiceActivatorDeployment.start(ServiceActivatorDeployment.java:80) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) > ... 3 more > 08:03:07,173 ERROR [org.jboss.as.controller.management-operation] (XNIO-1 task-5) WFLYCTL0013: Operation ("add") failed - address: ([{"deployment" => "test-http-deployment.sar"}]) - failure description: {"WFLYCTL0080: Failed services" => {"test.deployment.trivial" => "org.jboss.msc.service.StartException in service test.deployment.trivial: Failed to start service > Caused by: java.security.AccessControlException: WFSM000001: Permission check failed (permission \"(\"java.util.PropertyPermission\" \"test.deployment.trivial.prop\" \"write\")\" in code source \"(vfs:/content/test-http-deployment.sar <no signer certificates>)\" of \"null\")"}} > 08:03:07,174 ERROR [org.jboss.as.server] (XNIO-1 task-5) WFLYSRV0021: Deploy of deployment "test-http-deployment.sar" was rolled back with the following failure message: > {"WFLYCTL0080: Failed services" => {"test.deployment.trivial" => "org.jboss.msc.service.StartException in service test.deployment.trivial: Failed to start service > Caused by: java.security.AccessControlException: WFSM000001: Permission check failed (permission \"(\"java.util.PropertyPermission\" \"test.deployment.trivial.prop\" \"write\")\" in code source \"(vfs:/content/test-http-deployment.sar <no signer certificates>)\" of \"null\")"}} > {noformat} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4464) JDBC driver module-slot is not persisted in domain mode

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4464?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4464: ----------------------------------------------- Jan Martiska <jmartisk(a)redhat.com> changed the Status of [bug 1213642|https://bugzilla.redhat.com/show_bug.cgi?id=1213642] from ON_QA to VERIFIED > JDBC driver module-slot is not persisted in domain mode > ------------------------------------------------------- > > Key: WFLY-4464 > URL: https://issues.jboss.org/browse/WFLY-4464 > Project: WildFly > Issue Type: Bug > Components: Domain Management, JCA > Affects Versions: 8.2.0.Final > Reporter: Lin Gao > Assignee: Lin Gao > Fix For: 9.0.0.CR1 > > > The module-slot of jdbc-driver is NOT persisted in domain mode, but it is persisted in standalone mode. > After debugging, I found that the performRuntime() method of JdbcDriverAdd.java is not called in domain mode, but is called in standalone mode. > For more information about the issue, please refer to the thread: https://developer.jboss.org/thread/253654 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-775) domain mode - server fails to start intermittently

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-775?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-775: ------------------------------------------------ Jan Martiska <jmartisk(a)redhat.com> changed the Status of [bug 1245751|https://bugzilla.redhat.com/show_bug.cgi?id=1245751] from ON_QA to VERIFIED > domain mode - server fails to start intermittently > -------------------------------------------------- > > Key: WFCORE-775 > URL: https://issues.jboss.org/browse/WFCORE-775 > Project: WildFly Core > Issue Type: Bug > Environment: EAP 6.4.0 > Reporter: Ken Wills > Assignee: Ken Wills > Fix For: 2.0.0.Alpha11 > > > Server instances occasionally fail in domain mode using EAP 6.4.0. It appears to be due to the hashes being exchanged between the server instance and host controller. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-865) ClearAgendaGroup should materialize all activations and then cancel them

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-865: ---------------------------------- Summary: ClearAgendaGroup should materialize all activations and then cancel them Key: DROOLS-865 URL: https://issues.jboss.org/browse/DROOLS-865 Project: Drools Issue Type: Enhancement Reporter: Mario Fusco Assignee: Mario Fusco ClearAgendaGroup has to flush the propagation queue in a blocking way, This will materialize all rule matches so that they can be all cancelled. Once this will be implemented also this PR https://github.com/droolsjbpm/drools/pull/464 needs to be merged. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2015