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: ----------------------------------------------- Vladimir Dosoudil <dosoudil(a)redhat.com> changed the Status of [bug 1012968|https://bugzilla.redhat.com/show_bug.cgi?id=1012968] from MODIFIED to ON_QA > 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-2177) org.jboss.logmanager module needs dependency on javax.api for the SocketFactory

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2177?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2177: ----------------------------------------------- Vladimir Dosoudil <dosoudil(a)redhat.com> changed the Status of [bug 1013169|https://bugzilla.redhat.com/show_bug.cgi?id=1013169] from MODIFIED to ON_QA > org.jboss.logmanager module needs dependency on javax.api for the SocketFactory > ------------------------------------------------------------------------------- > > Key: WFLY-2177 > URL: https://issues.jboss.org/browse/WFLY-2177 > Project: WildFly > Issue Type: Bug > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Fix For: 8.0.0.Beta1 > > > The {{javax.net.SocketFactory}} is part of the {{javax.api}} module. Since the {{org.jboss.logmanager}} uses this for the syslog handler on TCP and SSL connections, a dependency on the module is needed. -- 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-1871) CLI module command doesn't allow cross platform resource paths

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1871?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1871: ----------------------------------------------- Ivo Studensky <istudens(a)redhat.com> changed the Status of [bug 1015400|https://bugzilla.redhat.com/show_bug.cgi?id=1015400] from NEW to ASSIGNED > CLI module command doesn't allow cross platform resource paths > -------------------------------------------------------------- > > Key: WFLY-1871 > URL: https://issues.jboss.org/browse/WFLY-1871 > Project: WildFly > Issue Type: Enhancement > Components: CLI > Affects Versions: 8.0.0.Alpha4 > Reporter: Stan Silvert > Assignee: Stan Silvert > Fix For: 8.0.0.Beta1 > > > The CLI module command has an argument called "resources". This argument allows you to specify one or more resources separated by the platform-specific path separator. The problem with this is that you can not create a platform-independent script that uses this resources argument. > I have not found a universal path separator character that would work. However, since the creator of the script knows the characters used in his path, we can allow him to specify his own separator. > As an enhancement, I propose to add an argument called "resourceDelimiter". If present, the ASModuleHandler class will use the user-defined delimiter instead of the platform-specific path separator character. > Example usage: > {noformat} > module add --name=org.foo --resources=firstResource.jar:secondResource.jar --resourceDelimiter=: --module-xml=foo-module.xml > {noformat} > The above command would work on Unix, Windows, or any other platform. -- 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-1871) CLI module command doesn't allow cross platform resource paths

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1871?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1871: ----------------------------------------------- Ivo Studensky <istudens(a)redhat.com> made a comment on [bug 1015400|https://bugzilla.redhat.com/show_bug.cgi?id=1015400] Description of problem: Backport of WFLY-1871 to EAP. Original description: The CLI module command has an argument called "resources". This argument allows you to specify one or more resources separated by the platform-specific path separator. The problem with this is that you can not create a platform-independent script that uses this resources argument. I have not found a universal path separator character that would work. However, since the creator of the script knows the characters used in his path, we can allow him to specify his own separator. As an enhancement, I propose to add an argument called "resourceDelimiter". If present, the ASModuleHandler class will use the user-defined delimiter instead of the platform-specific path separator character. Example usage: module add --name=org.foo --resources=firstResource.jar:secondResource.jar --resourceDelimiter=: --module-xml=foo-module.xml The above command would work on Unix, Windows, or any other platform. > CLI module command doesn't allow cross platform resource paths > -------------------------------------------------------------- > > Key: WFLY-1871 > URL: https://issues.jboss.org/browse/WFLY-1871 > Project: WildFly > Issue Type: Enhancement > Components: CLI > Affects Versions: 8.0.0.Alpha4 > Reporter: Stan Silvert > Assignee: Stan Silvert > Fix For: 8.0.0.Beta1 > > > The CLI module command has an argument called "resources". This argument allows you to specify one or more resources separated by the platform-specific path separator. The problem with this is that you can not create a platform-independent script that uses this resources argument. > I have not found a universal path separator character that would work. However, since the creator of the script knows the characters used in his path, we can allow him to specify his own separator. > As an enhancement, I propose to add an argument called "resourceDelimiter". If present, the ASModuleHandler class will use the user-defined delimiter instead of the platform-specific path separator character. > Example usage: > {noformat} > module add --name=org.foo --resources=firstResource.jar:secondResource.jar --resourceDelimiter=: --module-xml=foo-module.xml > {noformat} > The above command would work on Unix, Windows, or any other platform. -- 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-1871) CLI module command doesn't allow cross platform resource paths

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1871?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-1871: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1015400 > CLI module command doesn't allow cross platform resource paths > -------------------------------------------------------------- > > Key: WFLY-1871 > URL: https://issues.jboss.org/browse/WFLY-1871 > Project: WildFly > Issue Type: Enhancement > Components: CLI > Affects Versions: 8.0.0.Alpha4 > Reporter: Stan Silvert > Assignee: Stan Silvert > Fix For: 8.0.0.Beta1 > > > The CLI module command has an argument called "resources". This argument allows you to specify one or more resources separated by the platform-specific path separator. The problem with this is that you can not create a platform-independent script that uses this resources argument. > I have not found a universal path separator character that would work. However, since the creator of the script knows the characters used in his path, we can allow him to specify his own separator. > As an enhancement, I propose to add an argument called "resourceDelimiter". If present, the ASModuleHandler class will use the user-defined delimiter instead of the platform-specific path separator character. > Example usage: > {noformat} > module add --name=org.foo --resources=firstResource.jar:secondResource.jar --resourceDelimiter=: --module-xml=foo-module.xml > {noformat} > The above command would work on Unix, Windows, or any other platform. -- 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] (JBBUILD-731) Nexus staging repo close validation for jboss.org should validate that no artifacts end with "-redhat-0" or "-redhat-1"

by Geoffrey De Smet (JIRA)

Geoffrey De Smet created JBBUILD-731: ---------------------------------------- Summary: Nexus staging repo close validation for jboss.org should validate that no artifacts end with "-redhat-0" or "-redhat-1" Key: JBBUILD-731 URL: https://issues.jboss.org/browse/JBBUILD-731 Project: JBoss Build System Issue Type: Task Components: Artifact Repositories Reporter: Geoffrey De Smet All wolf artifacts will end with "-redhat-0", "-redhat-1", etc. None of the jboss.org artifacts should end with that. Otherwise a user/customer that has both repo's in his repository list, might find that a GAV is not unique. -- 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-284) Timer nullpointer due to race condition during update

by Mark Proctor (JIRA)

[ https://issues.jboss.org/browse/DROOLS-284?page=com.atlassian.jira.plugin... ] Mark Proctor resolved DROOLS-284. --------------------------------- Fix Version/s: 6.0.0.CR5 Resolution: Done > Timer nullpointer due to race condition during update > ----------------------------------------------------- > > Key: DROOLS-284 > URL: https://issues.jboss.org/browse/DROOLS-284 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Mark Proctor > Assignee: Mark Proctor > Fix For: 6.0.0.CR5 > > > If the timer fires at the same time as an update it results in the child being propagated twice. We need to synchronize to ensure that this does not happen. The update should cancel the timer, so it doens't try and schedule a propagation. -- 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-284) Timer nullpointer due to race condition during update

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-284?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated DROOLS-284: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1015323 > Timer nullpointer due to race condition during update > ----------------------------------------------------- > > Key: DROOLS-284 > URL: https://issues.jboss.org/browse/DROOLS-284 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Mark Proctor > Assignee: Mark Proctor > > If the timer fires at the same time as an update it results in the child being propagated twice. We need to synchronize to ensure that this does not happen. The update should cancel the timer, so it doens't try and schedule a propagation. -- 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-283) SegmentMemory staged LeftTuples not always accessed correctly

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-283?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated DROOLS-283: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1015208 > SegmentMemory staged LeftTuples not always accessed correctly > ------------------------------------------------------------- > > Key: DROOLS-283 > URL: https://issues.jboss.org/browse/DROOLS-283 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Mark Proctor > Assignee: Mark Proctor > Fix For: 6.0.0.CR5 > > > Some times it accesses the current staging list, instead of the one in the segment memory. > The NotNode should use the passed staging list, and not retrieve it directly. > They should always use takeAll, to ensure they are thread safe. -- 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-283) SegmentMemory staged LeftTuples not always accessed correctly

by Mark Proctor (JIRA)

[ https://issues.jboss.org/browse/DROOLS-283?page=com.atlassian.jira.plugin... ] Mark Proctor resolved DROOLS-283. --------------------------------- Fix Version/s: 6.0.0.CR5 Resolution: Done > SegmentMemory staged LeftTuples not always accessed correctly > ------------------------------------------------------------- > > Key: DROOLS-283 > URL: https://issues.jboss.org/browse/DROOLS-283 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Mark Proctor > Assignee: Mark Proctor > Fix For: 6.0.0.CR5 > > > Some times it accesses the current staging list, instead of the one in the segment memory. > The NotNode should use the passed staging list, and not retrieve it directly. > They should always use takeAll, to ensure they are thread safe. -- 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