March 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-1535) More management operations for timers

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-1535?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-1535: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > More management operations for timers > ------------------------------------- > > Key: AS7-1535 > URL: https://issues.jboss.org/browse/AS7-1535 > Project: Application Server 7 > Issue Type: Feature Request > Components: Domain Management, EJB > Reporter: Stuart Douglas > Assignee: Bartosz Baranowski > Fix For: 8.0.0.Alpha1 > > > Using the management api it should be possible to perform additional operations on timers such as: > suspending > cancelling > invoking a timeout method -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-3524) HostControllerConnectionService connection timeout is not configurable

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-3524?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-3524: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > HostControllerConnectionService connection timeout is not configurable > ---------------------------------------------------------------------- > > Key: AS7-3524 > URL: https://issues.jboss.org/browse/AS7-3524 > Project: Application Server 7 > Issue Type: Enhancement > Components: Domain Management > Affects Versions: 7.1.0.Final > Reporter: Dominik Pospisil > Assignee: Bartosz Baranowski > Fix For: 8.0.0.Alpha1 > > > I am seeing intermittent failures when starting AS7 in domain mode. It seems that this is due to HostControllerConnectionService has hardcoded 15s timeout when trying to connect to DC. I think that this value should be configurable. > HostControllerConnectionService.java: > ... > ProtocolChannelClient.Configuration configuration = new ProtocolChannelClient.Configuration(); > configuration.setEndpoint(endpointInjector.getValue()); > configuration.setConnectionTimeout(15000); > configuration.setUri(new URI("remote://" + hcAddressInjector.getValue().getHostName() + ":" + hcAddressInjector.getValue().getPort())); > client = ProtocolChannelClient.create(configuration); > ... > Exception I am getting: > [Server:server-two] 13:52:54,766 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.host.controller.channel: org.jboss.msc.service.StartException in service jboss.host.controller.channel: java.net.ConnectException: JBAS012144: Could not connect to remote://localhost.localdomain:9999. The connection timed out > [Server:server-two] at org.jboss.as.server.mgmt.domain.HostControllerConnectionService.start(HostControllerConnectionService.java:103) [jboss-as-server-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] > [Server:server-two] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] > [Server:server-two] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] > [Server:server-two] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_22] > [Server:server-two] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_22] > [Server:server-two] at java.lang.Thread.run(Thread.java:679) [:1.6.0_22] > [Server:server-two] Caused by: java.net.ConnectException: JBAS012144: Could not connect to remote://localhost.localdomain:9999. The connection timed out > [Server:server-two] at org.jboss.as.protocol.ProtocolChannelClient.connectSync(ProtocolChannelClient.java:166) [jboss-as-protocol-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6257) AttributeDefinition validateOperation should convert all expression strings to ModelType.EXPRESSION

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6257?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-6257: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > AttributeDefinition validateOperation should convert all expression strings to ModelType.EXPRESSION > --------------------------------------------------------------------------------------------------- > > Key: AS7-6257 > URL: https://issues.jboss.org/browse/AS7-6257 > Project: Application Server 7 > Issue Type: Enhancement > Components: Domain Management > Reporter: Brian Stansberry > Fix For: 8.0.0.Alpha1 > > > AttributeDefinition.validateOperation currently only converts a string to an expression if the attribute supports expressions. It should convert any time it sees the syntax. This way if a STRING attribute that doesn't support expressions finds one, it will reject it instead of accepting it as a raw string. > Scheduling for 7.3 out of concern this may break things in 7.2 without time to notice/adapt. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6309) Verify audit implications and required APIs

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6309?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-6309: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > Verify audit implications and required APIs > ------------------------------------------- > > Key: AS7-6309 > URL: https://issues.jboss.org/browse/AS7-6309 > Project: Application Server 7 > Issue Type: Sub-task > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 8.0.0.Alpha1 > > > Auditing may be logging as the user that executes a request, if we have used a trust relationship for a request to be run as a different user we need to be able to track back to identify how the user for the request was selected. > i.e. If userA runs something as userB and does something bad we must be able to track back that it was userA making the overall request without userB getting the blame. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-5501) provide means to specify allowed ciphers for management https or change default to exclude weak ciphers

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-5501?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-5501: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > provide means to specify allowed ciphers for management https or change default to exclude weak ciphers > ------------------------------------------------------------------------------------------------------- > > Key: AS7-5501 > URL: https://issues.jboss.org/browse/AS7-5501 > Project: Application Server 7 > Issue Type: Feature Request > Components: Domain Management, Security > Affects Versions: 7.1.2.Final (EAP) > Reporter: R Stokoe > Assignee: Darran Lofthouse > Fix For: 8.0.0.Alpha1 > > > Provide means to specify allowed ciphers for management https. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6411) Cygwin, add-user.sh and error "JBAS015232: Aucune java.io.Console disponible pour interagir avec l'utilisateur."

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6411?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-6411: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > Cygwin, add-user.sh and error "JBAS015232: Aucune java.io.Console disponible pour interagir avec l'utilisateur." > ---------------------------------------------------------------------------------------------------------------- > > Key: AS7-6411 > URL: https://issues.jboss.org/browse/AS7-6411 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management, Security > Affects Versions: 7.1.3.Final (EAP) > Environment: Windows XP with CYGWIN_NT-5.1 ... 1.7.17 (0.262/5/3) 2012-10-19 i686 > Java HotSpot 1.7.0_11, RE build 1.7.0_11-b21, Client VM build 23.6-b04, mixed mode > JBoss AS 7.1.3.Final > Reporter: Bernard Giroud > Assignee: Darran Lofthouse > Labels: as7, management > Fix For: 8.0.0.Alpha1 > > > First of all, the add-user.sh script has an invalid syntax on line 14 which reads: > {code} > cygwin = true; > {code} > It should read: > {code} > cygwin=true; > {code} > without spaces around the equal sign, Otherwise the truth value is not set, and the conversion back to Windows pathes is not done. > Furthermore, the back-conversions should be conditioned to avoid a "cygpath: can't convert empty path" in lines 56-60, especially with JAVA_HOME. > Finally, issuance of the following command : bin/add-user.sh u p > Gives: > {noformat} > cygpath: can't convert empty path > Exception in thread "main" java.lang.IllegalStateException: JBAS015232: Aucune java.io.Console disponible pour interagir avec l'utilisateur. > at org.jboss.as.domain.management.security.AddPropertiesUser.<init>(AddPropertiesUser.java:107) > at org.jboss.as.domain.management.security.AddPropertiesUser.<init>(AddPropertiesUser.java:118) > at org.jboss.as.domain.management.security.AddPropertiesUser.main(AddPropertiesUser.java:166) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) > at java.lang.reflect.Method.invoke(Unknown Source) > at org.jboss.modules.Module.run(Module.java:270) > at org.jboss.modules.Main.main(Main.java:294) > {noformat} > Issuance of the following command : bin/add-user.sh > Gives: > {noformat} > cygpath: can't convert empty path > Exception in thread "main" java.lang.IllegalStateException: JBAS015232: Aucune java.io.Console disponible pour interagir avec l'utilisateur. > at org.jboss.as.domain.management.security.AddPropertiesUser.<init>(AddPropertiesUser.java:78) > at org.jboss.as.domain.management.security.AddPropertiesUser.main(AddPropertiesUser.java:168) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) > at java.lang.reflect.Method.invoke(Unknown Source) > at org.jboss.modules.Module.run(Module.java:270) > at org.jboss.modules.Main.main(Main.java:294) > {noformat} > Option --silent doesn't make a difference. > An obvious workaround exists though: use with a CMD windows > {noformat} > bin\add-user.bat u p > {noformat} -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-5763) timeout handling waiting for future

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-5763?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-5763: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > timeout handling waiting for future > ----------------------------------- > > Key: AS7-5763 > URL: https://issues.jboss.org/browse/AS7-5763 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Reporter: Alexey Loubyansky > Assignee: Brian Stansberry > Fix For: 8.0.0.Alpha1 > > > The issue was reported in AS7-5350 which points to a CLI testcase that fails on windows. > The test starts a CLI process and deliberately specifies a wrong port for the controller expecting a failure during connection. The CLI sends a read-attribute operation request on connect to make sure the connection is working. The test is waiting for a response from the controller for 10 sec and then times out. The time out of the ModelControllerClient is 5 sec. The test still fails after 10 sec time out but the error output stream of the CLI process does contain the stack trace of the expected exception, i.e. that the controller was not available at the specified address. > When the testcase times out, it destroys the CLI process, perhaps, this triggers some actions and the exception is finally thrown and the stack trace gets logged but it's too late. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-4529) a "failure-causes-rollback="false"" attribute for the filesystem scanner

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-4529?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-4529: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > a "failure-causes-rollback="false"" attribute for the filesystem scanner > ------------------------------------------------------------------------ > > Key: AS7-4529 > URL: https://issues.jboss.org/browse/AS7-4529 > Project: Application Server 7 > Issue Type: Feature Request > Components: Domain Management > Reporter: Max Rydahl Andersen > Fix For: 8.0.0.Alpha1 > > > JBIDE-11509, AS7-783 and TORQUE-576 all talk about the problem of all deployments found at startup is deployed in one operation and if one deployment fails all is rolled back resulting in some rather bad usability issues - especially at development time, but even also at production time for those using file deployments. > Suggestion on irc was that there could be an option on the file scanner (possibly false by default?) to say that failure causes rollback. > Individual deployments could then still fail, but at least not everything would be rolledback and it would still allow proper interdependent deployments to work. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6437) Web subsystem executor configuration integration

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6437?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-6437: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > Web subsystem executor configuration integration > ------------------------------------------------ > > Key: AS7-6437 > URL: https://issues.jboss.org/browse/AS7-6437 > Project: Application Server 7 > Issue Type: Sub-task > Reporter: David Lloyd > Fix For: 8.0.0.Alpha1 > > > The web subsystem's executor injection mechanism needs to be replaced with an integrated executor configuration like JCA did. This must be done in the next rev of the subsystem. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-390) Eliminate the threads subsystem

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-390?page=com.atlassian.jira.plugin.sy... ] Brian Stansberry updated AS7-390: --------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > Eliminate the threads subsystem > ------------------------------- > > Key: AS7-390 > URL: https://issues.jboss.org/browse/AS7-390 > Project: Application Server 7 > Issue Type: Task > Reporter: David Lloyd > Assignee: Tomaz Cerar > Fix For: 8.0.0.Alpha1 > > > The threads subsystem should be eliminated, and instead the individual consuming subsystems should utilize common code from the jboss-as-threads module to define and manage thread pools within their own configuration models. > Subtasks for affected subsystems. -- 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

13 years, 2 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 2013