March 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2881) org.jboss.as.ejb3.timer.schedule.CalendarBasedTimeoutTestCase#testCalendarBasedTimeout

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-2881?page=com.atlassian.jira.plugin.... ] Scott Marlow reopened WFLY-2881: -------------------------------- reopening to go with the pull request https://github.com/wildfly/wildfly/pull/6098 against WFLY-2881. > org.jboss.as.ejb3.timer.schedule.CalendarBasedTimeoutTestCase#testCalendarBasedTimeout > -------------------------------------------------------------------------------------- > > Key: WFLY-2881 > URL: https://issues.jboss.org/browse/WFLY-2881 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EJB > Affects Versions: 8.0.0.Final > Reporter: Frank Langelage > Assignee: Eduardo Martins > Fix For: 8.0.1.Final > > Attachments: org.jboss.as.ejb3.timer.schedule.CalendarBasedTimeoutTestCase.txt, TEST-org.jboss.as.ejb3.timer.schedule.CalendarBasedTimeoutTestCase.xml > > > Running build with smoke tests on current github sources I get failure in this test case. > HOUR_OF_DAY is not 0 as expected but 1. > I changed the Assert in the test case to print out firstTimeout.toString() instead of only timeZoneDisplayName. > See attached files for more. -- 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

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3190) Make it possible to use custom vault with CLI

by Kabir Khan (JIRA)

Kabir Khan created WFLY-3190: -------------------------------- Summary: Make it possible to use custom vault with CLI Key: WFLY-3190 URL: https://issues.jboss.org/browse/WFLY-3190 Project: WildFly Issue Type: Feature Request Security Level: Public (Everyone can see) Components: CLI Reporter: Kabir Khan Assignee: Kabir Khan Fix For: 9.0.0.CR1 -- 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

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-101) JMSService.start is doing blocking I/O

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-101?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-101: ---------------------------------------------- Pavel Jelinek <pjelinek(a)redhat.com> changed the Status of [bug 1082103|https://bugzilla.redhat.com/show_bug.cgi?id=1082103] from NEW to POST > JMSService.start is doing blocking I/O > -------------------------------------- > > Key: WFLY-101 > URL: https://issues.jboss.org/browse/WFLY-101 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 8.0.0.Alpha1 > > > flag the start context as asynchronous -- 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

10 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-459) 5.6.x: update version to 5.6.1-SNAPSHOT as 5.6.0.Final is already out

by Petr Široký (JIRA)

Petr Široký created DROOLS-459: ---------------------------------- Summary: 5.6.x: update version to 5.6.1-SNAPSHOT as 5.6.0.Final is already out Key: DROOLS-459 URL: https://issues.jboss.org/browse/DROOLS-459 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Petr Široký Assignee: Michael Biarnes Kiefer The version in 5.6.x branch is still 5.6.0-SNAPSHOT, even though the 5.6.0.Final has been already released. Please update the version to 5.6.1-SNAPSHOT. Similarly with jBPM, the version should be updated to 5.5.1-SNAPSHOT. -- 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

10 years

1
0
0 / 0

[JBoss JIRA] (SECURITY-805) Overload SecurityVaultFactory.get() to be able to specify the classloader

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-805?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on SECURITY-805: -------------------------------------------------- Pavel Jelinek <pjelinek(a)redhat.com> changed the Status of [bug 1079930|https://bugzilla.redhat.com/show_bug.cgi?id=1079930] from ON_QA to VERIFIED > Overload SecurityVaultFactory.get() to be able to specify the classloader > ------------------------------------------------------------------------- > > Key: SECURITY-805 > URL: https://issues.jboss.org/browse/SECURITY-805 > Project: PicketBox > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: PicketBox_4_0_21.Beta2, PicketBox_4_0_19.SP5 > > Attachments: SECURITY-805-2.diff, SECURITY-805.diff > > > To work better with modular class loading in WF -- 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

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-2214) Allow additional environment properties to be set for outbound LDAP connections used by security realms.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2214?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2214: ----------------------------------------------- Ondrej Lukas <olukas(a)redhat.com> changed the Status of [bug 1015303|https://bugzilla.redhat.com/show_bug.cgi?id=1015303] from ON_QA to VERIFIED > Allow additional environment properties to be set for outbound LDAP connections used by security realms. > -------------------------------------------------------------------------------------------------------- > > Key: WFLY-2214 > URL: https://issues.jboss.org/browse/WFLY-2214 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Alpha4 > Reporter: Derek Horton > Assignee: Darran Lofthouse > Fix For: 8.0.0.CR1 > > > 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

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3108) Can't promote --backup slave HC to master and reload without moving domain.cached-remote.xml

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3108?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3108: ----------------------------------------------- Osamu Nagano <onagano(a)redhat.com> changed the Status of [bug 1082478|https://bugzilla.redhat.com/show_bug.cgi?id=1082478] from NEW to POST > Can't promote --backup slave HC to master and reload without moving domain.cached-remote.xml > -------------------------------------------------------------------------------------------- > > Key: WFLY-3108 > URL: https://issues.jboss.org/browse/WFLY-3108 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Final > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 8.0.1.Final > > > The prescribed mechanism for converting a slave HC to master is to: > 1) Start the slave with --backup so a local copy of the domain config is maintained (in file domain.cached-remote.xml). > 2) Stop the existing master. > 3) Use the cli to connect to the slave and > /host=<slavename>:write-local-domain-controller > 4) Then, in the CLI > reload --host=<slavename> > Problem is this fails because the HC expects to have a domain config file "domain.xml". > 2014-03-13 09:54:04,829 ERROR [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010932: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration > at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:112) [wildfly-controller-8.0.1.Final-SNAPSHOT.jar:8.0.1.Final-SNAPSHOT] > at org.jboss.as.host.controller.DomainModelControllerService.boot(DomainModelControllerService.java:514) [wildfly-host-controller-8.0.1.Final-SNAPSHOT.jar:8.0.1.Final-SNAPSHOT] > at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:256) [wildfly-controller-8.0.1.Final-SNAPSHOT.jar:8.0.1.Final-SNAPSHOT] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45] > Caused by: java.io.FileNotFoundException: /Users/bstansberry/tmp/WF801/slave/domain/configuration/domain.xml (No such file or directory) > at java.io.FileInputStream.open(Native Method) [rt.jar:1.7.0_45] > at java.io.FileInputStream.<init>(FileInputStream.java:146) [rt.jar:1.7.0_45] > at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:100) [wildfly-controller-8.0.1.Final-SNAPSHOT.jar:8.0.1.Final-SNAPSHOT] > ... 3 more > Or, MUCH WORSE, there happens to be a random domain.xml in the filesystem, which has content that is out of sync with the correct domain config. This domain.xml config will be used. -- 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

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3108) Can't promote --backup slave HC to master and reload without moving domain.cached-remote.xml

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3108?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-3108: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1076066, https://bugzilla.redhat.com/show_bug.cgi?id=1082478 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1076066) > Can't promote --backup slave HC to master and reload without moving domain.cached-remote.xml > -------------------------------------------------------------------------------------------- > > Key: WFLY-3108 > URL: https://issues.jboss.org/browse/WFLY-3108 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Final > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 8.0.1.Final > > > The prescribed mechanism for converting a slave HC to master is to: > 1) Start the slave with --backup so a local copy of the domain config is maintained (in file domain.cached-remote.xml). > 2) Stop the existing master. > 3) Use the cli to connect to the slave and > /host=<slavename>:write-local-domain-controller > 4) Then, in the CLI > reload --host=<slavename> > Problem is this fails because the HC expects to have a domain config file "domain.xml". > 2014-03-13 09:54:04,829 ERROR [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010932: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration > at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:112) [wildfly-controller-8.0.1.Final-SNAPSHOT.jar:8.0.1.Final-SNAPSHOT] > at org.jboss.as.host.controller.DomainModelControllerService.boot(DomainModelControllerService.java:514) [wildfly-host-controller-8.0.1.Final-SNAPSHOT.jar:8.0.1.Final-SNAPSHOT] > at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:256) [wildfly-controller-8.0.1.Final-SNAPSHOT.jar:8.0.1.Final-SNAPSHOT] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45] > Caused by: java.io.FileNotFoundException: /Users/bstansberry/tmp/WF801/slave/domain/configuration/domain.xml (No such file or directory) > at java.io.FileInputStream.open(Native Method) [rt.jar:1.7.0_45] > at java.io.FileInputStream.<init>(FileInputStream.java:146) [rt.jar:1.7.0_45] > at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:100) [wildfly-controller-8.0.1.Final-SNAPSHOT.jar:8.0.1.Final-SNAPSHOT] > ... 3 more > Or, MUCH WORSE, there happens to be a random domain.xml in the filesystem, which has content that is out of sync with the correct domain config. This domain.xml config will be used. -- 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

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-2950) jboss-cli using https-remoting: command not executed if certificate is unrecognised

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2950?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2950: ----------------------------------------------- Petr Kremensky <pkremens(a)redhat.com> changed the Status of [bug 1026418|https://bugzilla.redhat.com/show_bug.cgi?id=1026418] from ON_QA to VERIFIED > jboss-cli using https-remoting: command not executed if certificate is unrecognised > ----------------------------------------------------------------------------------- > > Key: WFLY-2950 > URL: https://issues.jboss.org/browse/WFLY-2950 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: CLI, Domain Management > Affects Versions: 8.0.0.Final > Environment: Windows 7 Pro > Reporter: Darren Jones > Assignee: Darran Lofthouse > Labels: cli, shutdown > Fix For: 8.0.1.Final > > > When using the https management interface from jboss-cli, commands passed with a command line option (such as --command=:shutdown) are not executed if the server certificate is unrecognised - even if accepting the certificate [T]emporarily or [P]ermenantly. > It appears to be due to the CommandContextImpl.handleSSLFailure() method, which calls error("Unable to connect..."). The error() method sets the exitCode to 1. So, when CliLauncher.processCommands() subsequently runs, it sees that the cmdCtx.exitCode is 1 and ignores any commands. > I guess the handleSSLFailure needs to reset the exitCode to 0 if the user chooses [T] or [P]. -- 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

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-2538) Certificate acceptance causing command entered on starting the CLI to be skipped.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2538?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2538: ----------------------------------------------- Petr Kremensky <pkremens(a)redhat.com> changed the Status of [bug 1026418|https://bugzilla.redhat.com/show_bug.cgi?id=1026418] from ON_QA to VERIFIED > Certificate acceptance causing command entered on starting the CLI to be skipped. > --------------------------------------------------------------------------------- > > Key: WFLY-2538 > URL: https://issues.jboss.org/browse/WFLY-2538 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: CLI > Affects Versions: 8.0.0.Beta1 > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 8.0.0.CR1 > > > e.g. > {noformat} > ./jboss-cli.sh -c shutdown > Accept certificate? [N]o, [T]emporarily, [P]ermenantly : T > {noformat} > The shutdown command is not executed. -- 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

10 years

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 March 2014