March 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: ------------------------------------------------ Tomas Hofman <thofman(a)redhat.com> changed the Status of [bug 1198186|https://bugzilla.redhat.com/show_bug.cgi?id=1198186] from ASSIGNED to POST > 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.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ELY-166) Add a RemoveGlobalSecurityProvider action.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-166?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse resolved ELY-166. ---------------------------------- Fix Version/s: (was: 1.0.0.Alpha1) Resolution: Deferred Deferring for now, my situation involves calling the actions in a loop so it makes more sense for the action to be slightly higher up and make all calls in a single action. > Add a RemoveGlobalSecurityProvider action. > ------------------------------------------ > > Key: ELY-166 > URL: https://issues.jboss.org/browse/ELY-166 > Project: WildFly Elytron > Issue Type: Feature Request > Components: Security Manager > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-553) ModelControllerClientOperationHandler doesn't manage the clientRequestExecutor properly

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-553?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-553: ------------------------------------------------ baranowb <bbaranow(a)redhat.com> changed the Status of [bug 1199319|https://bugzilla.redhat.com/show_bug.cgi?id=1199319] from NEW to ASSIGNED > ModelControllerClientOperationHandler doesn't manage the clientRequestExecutor properly > ---------------------------------------------------------------------------------------- > > Key: WFCORE-553 > URL: https://issues.jboss.org/browse/WFCORE-553 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 1.0.0.Alpha1, 1.0.0.Alpha18 > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 1.0.0.Beta1 > > > ModelControllerClientOperationHandler's constructor creates a ThreadPoolExecutor for handling client requests and then the class doesn't clean it up. > In addition, an instance of ModelControllerClientOperationHandler is created per channel, not one per ModelControllerClientOperationHandlerFactoryService. I know I at least thought of the thread pool as being per remote management interface, not per channel. > Making it be per ModelControllerClientOperationHandlerFactoryService and cleaning it up in that service's stop would be the easiest fix, but the pool settings may not be appropriate if we do that, so tread carefully. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4133) Hanging EJB threads because of a persistent timer and failed deployment

by Enrique González Martínez (JIRA)

[ https://issues.jboss.org/browse/WFLY-4133?page=com.atlassian.jira.plugin.... ] Enrique González Martínez updated WFLY-4133: -------------------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/7006, https://github.com/jbossas/jboss-eap/pull/2351 (was: https://github.com/wildfly/wildfly/pull/7006) > Hanging EJB threads because of a persistent timer and failed deployment > ------------------------------------------------------------------------ > > Key: WFLY-4133 > URL: https://issues.jboss.org/browse/WFLY-4133 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 9.0.0.Alpha1 > Reporter: Enrique González Martínez > Assignee: Enrique González Martínez > Fix For: 9.0.0.Beta1 > > > When there is a time service with pending timeouts a bad redeploy can hang worker threads in the server. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3316) Multi threaded ejb invocations via remote-naming produce EJBCLIENT000025 if the Context is closed

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3316?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3316: ----------------------------------------------- Enrique Gonzalez Martinez <egonzale(a)redhat.com> changed the Status of [bug 1094380|https://bugzilla.redhat.com/show_bug.cgi?id=1094380] from POST to MODIFIED > Multi threaded ejb invocations via remote-naming produce EJBCLIENT000025 if the Context is closed > ------------------------------------------------------------------------------------------------- > > Key: WFLY-3316 > URL: https://issues.jboss.org/browse/WFLY-3316 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 8.0.0.Final > Reporter: Wolf-Dieter Fink > Assignee: Enrique González Martínez > Labels: ejb, naming, remote-clients, remote-ejb-connection > Attachments: reproducer.zip > > > If a client run multi threads and each Thread use it's own InitialContext the behaviour is unexpected. > The behaviour is as followed: > if each invocation create it's own IC and lookup the EJB there is sometimes a EJBCLIENT000025 because one of the one thread has closed the IC until another thread try to invoke an EJB. > If the IC is reused the failure might happen only if the first Thread has finished the invocations and close the IC during other Threads are still running. > It looks that the underlying remote connection will be closed if the first IC is closed without respect that there are different IC's created and still in use. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-581) CLI accepts operation requests with addresses ending on resource types

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-581?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-581: ------------------------------------------------ baranowb <bbaranow(a)redhat.com> changed the Status of [bug 1169342|https://bugzilla.redhat.com/show_bug.cgi?id=1169342] from ASSIGNED to POST > CLI accepts operation requests with addresses ending on resource types > ---------------------------------------------------------------------- > > Key: WFCORE-581 > URL: https://issues.jboss.org/browse/WFCORE-581 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 1.0.0.Alpha19 > Reporter: Alexey Loubyansky > Assignee: Alexey Loubyansky > Fix For: 1.0.0.Beta1 > > > It doesn't concern the tab-completion. But if the address is entered manually and ends on a resource type, the generated operation request will target the parent resource. > [standalone@localhost:9999 /] echo-dmr /subsystem=logging/file-handler=:remove > { > "address" => [("subsystem" => "logging")], > "operation" => "remove" > } -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4415) RemotingContext should be copied for async EJB calls

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4415?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4415: ----------------------------------------------- baranowb <bbaranow(a)redhat.com> changed the Status of [bug 1201439|https://bugzilla.redhat.com/show_bug.cgi?id=1201439] from NEW to POST > RemotingContext should be copied for async EJB calls > ---------------------------------------------------- > > Key: WFLY-4415 > URL: https://issues.jboss.org/browse/WFLY-4415 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 9.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4303) Allow expressions in jboss-ejb-client.xml if configuration jboss-descriptor-property-replacement=true

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4303?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4303: ----------------------------------------------- baranowb <bbaranow(a)redhat.com> changed the Status of [bug 1194381|https://bugzilla.redhat.com/show_bug.cgi?id=1194381] from NEW to ASSIGNED > Allow expressions in jboss-ejb-client.xml if configuration jboss-descriptor-property-replacement=true > ----------------------------------------------------------------------------------------------------- > > Key: WFLY-4303 > URL: https://issues.jboss.org/browse/WFLY-4303 > Project: WildFly > Issue Type: Feature Request > Components: EJB > Reporter: Wolf-Dieter Fink > Assignee: Tomasz Adamski > > Applications need to have a jboss-ejb-client.xml configuration to use connections to other WildFly servers. > The remote-outbound-connection allow expressions, i.e. for user-name. > But if a cluster come into play the related <cluster> element inside the jboss-ejb-client.xml must have the same username and this can be only hardcoded. > So the jboss-ejb-client.xml parsing should allow expressions for > outbound-connection-ref, username, security-realm etc. > See https://github.com/wildfly/quickstart/blob/master/ejb-multi-server/app-ma... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-581) CLI accepts operation requests with addresses ending on resource types

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-581?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-581: ------------------------------------------------ baranowb <bbaranow(a)redhat.com> changed the Status of [bug 1169342|https://bugzilla.redhat.com/show_bug.cgi?id=1169342] from NEW to ASSIGNED > CLI accepts operation requests with addresses ending on resource types > ---------------------------------------------------------------------- > > Key: WFCORE-581 > URL: https://issues.jboss.org/browse/WFCORE-581 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 1.0.0.Alpha19 > Reporter: Alexey Loubyansky > Assignee: Alexey Loubyansky > Fix For: 1.0.0.Beta1 > > > It doesn't concern the tab-completion. But if the address is entered manually and ends on a resource type, the generated operation request will target the parent resource. > [standalone@localhost:9999 /] echo-dmr /subsystem=logging/file-handler=:remove > { > "address" => [("subsystem" => "logging")], > "operation" => "remove" > } -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4321) restart of http connector without restarting whole web container

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-4321?page=com.atlassian.jira.plugin.... ] Stuart Douglas reassigned WFLY-4321: ------------------------------------ Fix Version/s: Awaiting Volunteers Assignee: (was: Stuart Douglas) > restart of http connector without restarting whole web container > ---------------------------------------------------------------- > > Key: WFLY-4321 > URL: https://issues.jboss.org/browse/WFLY-4321 > Project: WildFly > Issue Type: Feature Request > Components: Web (Undertow) > Affects Versions: 8.2.0.Final > Reporter: Davide Gesino > Priority: Minor > Labels: connector,, mbeans, ssl, > Fix For: Awaiting Volunteers > > > It would be great if Undertow provided a feature Tomcat has, namely the possibility to stop the http connector without restarting the whole container. > It's useful for example in case when certificates for SSL communication change while the container is up and running. > Tomcat has this feature setting the property "org.apache.tomcat.util.ENABLE_MODELER" to true: this turn on the MBeans management for Tomcat. > Through these beans it's possible to start and stop the connectors. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 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 March 2015