October 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2181) TempFileProviderService creates a static, non-daemon thread pool

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2181?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2181: ----------------------------------------------- Petr Kremensky <pkremens(a)redhat.com> made a comment on [bug 1012968|https://bugzilla.redhat.com/show_bug.cgi?id=1012968] Verified on EAP 6.2.0.ER4 > TempFileProviderService creates a static, non-daemon thread pool > ---------------------------------------------------------------- > > Key: WFLY-2181 > URL: https://issues.jboss.org/browse/WFLY-2181 > Project: WildFly > Issue Type: Bug > Components: Server > Affects Versions: 8.0.0.Alpha4 > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 8.0.0.Beta1 > > > This can prevent the server from shutting down -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2181) TempFileProviderService creates a static, non-daemon thread pool

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2181?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2181: ----------------------------------------------- Petr Kremensky <pkremens(a)redhat.com> changed the Status of [bug 1012968|https://bugzilla.redhat.com/show_bug.cgi?id=1012968] from ON_QA to VERIFIED > TempFileProviderService creates a static, non-daemon thread pool > ---------------------------------------------------------------- > > Key: WFLY-2181 > URL: https://issues.jboss.org/browse/WFLY-2181 > Project: WildFly > Issue Type: Bug > Components: Server > Affects Versions: 8.0.0.Alpha4 > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 8.0.0.Beta1 > > > This can prevent the server from shutting down -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-327) Remote JNDI is not working with a HornetQ-only JMS bridge

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-327?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-327: ---------------------------------------------- Martin Svehla <msvehla(a)redhat.com> made a comment on [bug 912653|https://bugzilla.redhat.com/show_bug.cgi?id=912653] No NotSerializableExceptions anymore. Good job. > Remote JNDI is not working with a HornetQ-only JMS bridge > --------------------------------------------------------- > > Key: WFLY-327 > URL: https://issues.jboss.org/browse/WFLY-327 > Project: WildFly > Issue Type: Feature Request > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 8.0.0.Alpha1 > > > The jms-bridge can be used to bridge a hornetq server to another and should work by specifying to use the org.hornetq.module to load the JMS implementation classes. > However, this fails because this module does not have access to the JBoss remote-naming module that is required to connect to remote JBoss JNDI server. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-327) Remote JNDI is not working with a HornetQ-only JMS bridge

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-327?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-327: ---------------------------------------------- Martin Svehla <msvehla(a)redhat.com> changed the Status of [bug 912653|https://bugzilla.redhat.com/show_bug.cgi?id=912653] from ON_QA to VERIFIED > Remote JNDI is not working with a HornetQ-only JMS bridge > --------------------------------------------------------- > > Key: WFLY-327 > URL: https://issues.jboss.org/browse/WFLY-327 > Project: WildFly > Issue Type: Feature Request > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 8.0.0.Alpha1 > > > The jms-bridge can be used to bridge a hornetq server to another and should work by specifying to use the org.hornetq.module to load the JMS implementation classes. > However, this fails because this module does not have access to the JBoss remote-naming module that is required to connect to remote JBoss JNDI server. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2139) ProxyStepHandler/Controller need to check access before attempting to read information

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2139?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2139: ----------------------------------------------- Jakub Cechacek <jcechace(a)redhat.com> changed the Status of [bug 1011994|https://bugzilla.redhat.com/show_bug.cgi?id=1011994] from ON_QA to VERIFIED > ProxyStepHandler/Controller need to check access before attempting to read information > -------------------------------------------------------------------------------------- > > Key: WFLY-2139 > URL: https://issues.jboss.org/browse/WFLY-2139 > Project: WildFly > Issue Type: Sub-task > Components: Domain Management, Security > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 8.0.0.Beta1 > > > This affects things like recursive :read-resource(-description) :read-children-resources and so on. The problem as it stands is that if you have, say, a host scoped role scoped to host=master, and there is also a slave host controller, and you try to :read-resource(recursive=true,proxies=true), the master will list the slave host controller in its list of child addresses. It will then execute /host=slave:read-resource(recursive=true,proxies=true), which will fail and roll back the tx since the master host scoped role does not have access to that resource. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2139) ProxyStepHandler/Controller need to check access before attempting to read information

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2139?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2139: ----------------------------------------------- Jakub Cechacek <jcechace(a)redhat.com> made a comment on [bug 1011994|https://bugzilla.redhat.com/show_bug.cgi?id=1011994] Verified for 6.2.0.ER4 Tests previously failing due to this issue passed. After looking at threads through visual vm I consider this fixed. > ProxyStepHandler/Controller need to check access before attempting to read information > -------------------------------------------------------------------------------------- > > Key: WFLY-2139 > URL: https://issues.jboss.org/browse/WFLY-2139 > Project: WildFly > Issue Type: Sub-task > Components: Domain Management, Security > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 8.0.0.Beta1 > > > This affects things like recursive :read-resource(-description) :read-children-resources and so on. The problem as it stands is that if you have, say, a host scoped role scoped to host=master, and there is also a slave host controller, and you try to :read-resource(recursive=true,proxies=true), the master will list the slave host controller in its list of child addresses. It will then execute /host=slave:read-resource(recursive=true,proxies=true), which will fail and roll back the tx since the master host scoped role does not have access to that resource. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-1913) CLI 'module add' command fail if a drive letter is specified in its resource path

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1913?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1913: ----------------------------------------------- Ivo Studensky <istudens(a)redhat.com> changed the Status of [bug 1014921|https://bugzilla.redhat.com/show_bug.cgi?id=1014921] from ASSIGNED to POST > CLI 'module add' command fail if a drive letter is specified in its resource path > --------------------------------------------------------------------------------- > > Key: WFLY-1913 > URL: https://issues.jboss.org/browse/WFLY-1913 > Project: WildFly > Issue Type: Bug > Components: CLI > Affects Versions: 8.0.0.Alpha4 > Reporter: Ivo Studensky > Assignee: Ivo Studensky > Fix For: 8.0.0.Beta1 > > Attachments: install-mojarra-2.0.0.cli > > > If a drive letter is specified in the resource path the module add command fails on MS Windows. It cannot locate such a resource because of doubled drive letter in the translated path. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-1913) CLI 'module add' command fail if a drive letter is specified in its resource path

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1913?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1913: ----------------------------------------------- Ivo Studensky <istudens(a)redhat.com> made a comment on [bug 1014921|https://bugzilla.redhat.com/show_bug.cgi?id=1014921] Relevant PR: https://github.com/jbossas/jboss-eap/pull/509 > CLI 'module add' command fail if a drive letter is specified in its resource path > --------------------------------------------------------------------------------- > > Key: WFLY-1913 > URL: https://issues.jboss.org/browse/WFLY-1913 > Project: WildFly > Issue Type: Bug > Components: CLI > Affects Versions: 8.0.0.Alpha4 > Reporter: Ivo Studensky > Assignee: Ivo Studensky > Fix For: 8.0.0.Beta1 > > Attachments: install-mojarra-2.0.0.cli > > > If a drive letter is specified in the resource path the module add command fails on MS Windows. It cannot locate such a resource because of doubled drive letter in the translated path. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-281) no reevaluation of 'from collect' is performed

by Richard Bourner (JIRA)

[ https://issues.jboss.org/browse/DROOLS-281?page=com.atlassian.jira.plugin... ] Richard Bourner commented on DROOLS-281: ---------------------------------------- Additional information: it seems like the problem starts occuring for Beta3. > no reevaluation of 'from collect' is performed > ---------------------------------------------- > > Key: DROOLS-281 > URL: https://issues.jboss.org/browse/DROOLS-281 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.0.0.CR4 > Reporter: Richard Bourner > Assignee: Mark Proctor > Priority: Critical > Attachments: Drools6FromCollectIssue.zip > > > Using Drools 6.0.0.CR4, a problem has been found related to reevaluation of a condition that contains a 'from collect' statement. > A unit test is provided demonstrating the issue using 2 rules. This unit test works fine using 6.0.0.Beta2. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2214) LDAP security realm needs to have configurable timeouts

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-2214?page=com.atlassian.jira.plugin.... ] Darran Lofthouse commented on WFLY-2214: ---------------------------------------- This actually raises an interesting point to also consider - if we can detect that the first server was not used maybe for a short period of time we should re-order the server list to give a higher priority to the server we know does exist. As authentication also establishes a connection to the server to verify the password it would be beneficial to lower the priority of the missing server. > LDAP security realm needs to have configurable timeouts > ------------------------------------------------------- > > Key: WFLY-2214 > URL: https://issues.jboss.org/browse/WFLY-2214 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Affects Versions: 8.0.0.Alpha4 > Reporter: Derek Horton > Assignee: Darran Lofthouse > Fix For: 8.0.0.Beta1 > > > LDAP security realm needs to have configurable timeouts. > The default LDAP connection timeout appears to be 2 minutes. If the ldap server is down, it could take 2 minutes for the connection to timeout. This can cause unneeded delay if you have configured multiple ldap servers for failover / redundancy. > The following hack appears to work: > +++ domain-management/src/main/java/org/jboss/as/domain/management/connections/ldap/LdapConnectionManagerService.java > @@ -132,6 +132,7 @@ public class LdapConnectionManagerService implements Service<LdapConnectionManag > result.put(Context.INITIAL_CONTEXT_FACTORY,initialContextFactory); > String url = config.require(URL).asString(); > result.put(Context.PROVIDER_URL,url); > + result.put("com.sun.jndi.ldap.connect.timeout", "500"); > return result; > } -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2013