February 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-2936) Canot remove security login moddule

by Heiko Braun (Created) (JIRA)

Canot remove security login moddule ----------------------------------- Key: AS7-2936 URL: https://issues.jboss.org/browse/AS7-2936 Project: Application Server 7 Issue Type: Bug Components: Domain Management, Security Reporter: Heiko Braun Assignee: Brian Stansberry Fix For: 7.1.0.CR1 Due to some weird DMR constraints I cannot clear the list of security domain modules: {noformat} [INFO] save:{ [INFO] "operation" => "write-attribute", [INFO] "address" => [ [INFO] ("subsystem" => "security"), [INFO] ("security-domain" => "other"), [INFO] ("authentication" => "classic") [INFO] ], [INFO] "name" => "login-modules", [INFO] "value" => [] [INFO] } [ERROR] 2011-12-07 09:21:57,097 [ERROR] On Wed Dec 07 09:21:57 CET 2011, MessageCenter received Failed to: write-attribute login-modules: other [ERROR] 2011-12-07 09:21:57,101 [ERROR] Message{conciseMessage='Failed to: write-attribute login-modules: other', detailedMessage='JBAS014706: [0] is an invalid size for parameter value. A minimum length of [1] is required', fired=Wed Dec 07 09:21:57 CET 2011, severity=Error, options=[]} {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

9
12
0 / 0

[JBoss JIRA] (AS7-3881) HornetQ configurations for broadcast and discovery groups do not use socket bindings

by Shelly McGowan (JIRA)

Shelly McGowan created AS7-3881: ----------------------------------- Summary: HornetQ configurations for broadcast and discovery groups do not use socket bindings Key: AS7-3881 URL: https://issues.jboss.org/browse/AS7-3881 Project: Application Server 7 Issue Type: Bug Reporter: Shelly McGowan Assignee: Brian Stansberry Fix For: 7.1.1.Final HornetQ configurations for broadcast and discovery groups do not use socket bindings. Every configurations values related to ports or addresses should use socket bindings. For example see configurations for JGrpups, ... standalone/configuration/standalone-full-ha.xml HornetQ {code} <broadcast-groups> <broadcast-group name="bg-group1"> <group-address>231.7.7.7</group-address> <group-port>9876</group-port> <broadcast-period>5000</broadcast-period> <connector-ref>netty</connector-ref> </broadcast-group> </broadcast-groups> <discovery-groups> <discovery-group name="dg-group1"> <group-address>231.7.7.7</group-address> <group-port>9876</group-port> <refresh-timeout>10000</refresh-timeout> </discovery-group> </discovery-groups> .... {code} {code} <socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}"> ... <socket-binding name="jgroups-diagnostics" port="0" multicast-address="224.0.75.75" multicast-port="7500"/> <socket-binding name="jgroups-mping" port="0" multicast-address="${jboss.default.multicast.address:230.0.0.4}" multicast-port="45700"/> ... {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

3
3
0 / 0

[JBoss JIRA] (AS7-3244) Convert jsr77 subsystem to i18n logging and exceptions messages as per ANDIAMO-2

by Brian Stansberry (Created) (JIRA)

Convert jsr77 subsystem to i18n logging and exceptions messages as per ANDIAMO-2 -------------------------------------------------------------------------------- Key: AS7-3244 URL: https://issues.jboss.org/browse/AS7-3244 Project: Application Server 7 Issue Type: Task Components: Server Reporter: Brian Stansberry The JSR77 subsystem has no Jsr77Logger or Jsr77Messages. It doesn't seem to really do output any text at the moment so this is not critical. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

2
1
0 / 0

[JBoss JIRA] (AS7-3801) Deleting content in "data/content" breaks JBoss startup

by Wolfgang Knauf (JIRA)

Wolfgang Knauf created AS7-3801: ----------------------------------- Summary: Deleting content in "data/content" breaks JBoss startup Key: AS7-3801 URL: https://issues.jboss.org/browse/AS7-3801 Project: Application Server 7 Issue Type: Bug Components: Server Affects Versions: 7.1.0.CR1b Environment: Happens at least with the snapshot of 2012-02-07 Reporter: Wolfgang Knauf Assignee: Jason Greene Priority: Minor Attachments: boot.log I deployed an app by JSR88 (full sample + deployer attached to AS7-3474 ). Then I started some vandalism and deleted the directory "standalone\data\content\91\107bf1efaf37237132c7e7ec9b02ec178f4bfe", where the deployed app was found. This prevented JBoss from starting. Attached is the boot.log. Though it tells that the server was started, it seems to have skipped all modules. This error message was found: 21:14:48,203 ERROR [org.jboss.as.controller.management-operation] Operation ("add") failed - address: ([("deployment" => "file:/C:/DOCUME~1/Knuffi/LOCALS~1/Temp/___Stateless.ear")]) - failure description: "JBAS015812: No deployment content with hash 91107bf1efaf37237132c7e7ec9b02ec178f4bfe is available in the deployment content repository." I would expect that it skips the missing deployment, but continues with the rest of the startup process. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

2
2
0 / 0

[JBoss JIRA] (AS7-2002) Simplify runtime resource registration

by Emanuel Muckenhuber (Created) (JIRA)

Simplify runtime resource registration -------------------------------------- Key: AS7-2002 URL: https://issues.jboss.org/browse/AS7-2002 Project: Application Server 7 Issue Type: Task Components: Domain Management Affects Versions: 7.0.0.Final Reporter: Emanuel Muckenhuber Assignee: Emanuel Muckenhuber Priority: Critical Fix For: 7.1.0.CR1 We need to review and simplify the process of creating and registering runtime resources - to avoid having something like: https://github.com/jbossas/jboss-as/blob/master/messaging/src/main/java/o... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

3
2
0 / 0

[JBoss JIRA] (AS7-3979) org.jboss.as.controller.client.helpers.standalone.ServerDeploymentManager leaks ModelCotrollerClients

by Stuart Douglas (JIRA)

Stuart Douglas created AS7-3979: ----------------------------------- Summary: org.jboss.as.controller.client.helpers.standalone.ServerDeploymentManager leaks ModelCotrollerClients Key: AS7-3979 URL: https://issues.jboss.org/browse/AS7-3979 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.1.0.Final Reporter: Stuart Douglas Assignee: Brian Stansberry This helper creates a ModelControllerClient that is never closed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

3
2
0 / 0

[JBoss JIRA] (AS7-2673) CLI shutdown * operation (kills domain controller first, beheads host controllers)

by mark yarborough (Created) (JIRA)

CLI shutdown * operation (kills domain controller first, beheads host controllers) ---------------------------------------------------------------------------------- Key: AS7-2673 URL: https://issues.jboss.org/browse/AS7-2673 Project: Application Server 7 Issue Type: Bug Components: CLI Affects Versions: 7.1.0.Alpha1 Reporter: mark yarborough Assignee: Alexey Loubyansky Priority: Trivial >From the CLI with a domain controller and two host controllers running, using wildcard command intended to shut down everything: [domain@localhost:9999 host] cd .. [domain@localhost:9999 /] ls host host2-9 host3 master [domain@localhost:9999 /] ./host=*:shutdown {"outcome" => "success"} [domain@localhost:9999 /] ls [domain@localhost:9999 /] Success is reported, and we're no longer connected to a domain controller. A follow up check reveals that the domain controller (host=master) was shutdown, but the host controllers (host2-9 and host3) are still up and now searching for the missing domain controller: <snippet from host3 console> [Host Controller] 20:47:07,351 WARN [org.jboss.as.domain.controller] (Thread-14) Could not connect to remote domain controller 127.0.0.1:9999 [Host Controller] 20:47:22,357 WARN [org.jboss.as.domain.controller] (Thread-14) Could not connect to remote domain controller 127.0.0.1:9999 [Host Controller] 20:47:37,364 WARN [org.jboss.as.domain.controller] (Thread-14) Could not connect to remote domain controller 127.0.0.1:9999 [Host Controller] 20:47:52,370 WARN [org.jboss.as.domain.controller] (Thread-14) Could not connect to remote domain controller 127.0.0.1:9999 It appears that the DC was shutdown first, so no communication path the HCs, so they were not shutdown. Perhaps the wildcard should be disallowed for the shutdown operation, or intelligence added to shutdown the DC last... Just wanted to let you know. Running something called jboss-as-7.1.0.Alpha2-SNAPSHOT downloaded by Rich Raposa for a GLS class around 10-Nov-2011. I chose "Affects Version" because that was the closest on the list... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

3
2
0 / 0

[JBoss JIRA] (AS7-2757) Update the add-user script to check existing users, if they exist prompt if password should be updated instead of new user added

by Darran Lofthouse (Created) (JIRA)

Update the add-user script to check existing users, if they exist prompt if password should be updated instead of new user added --------------------------------------------------------------------------------------------------------------------------------- Key: AS7-2757 URL: https://issues.jboss.org/browse/AS7-2757 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Reporter: Darran Lofthouse Fix For: Open To Community Another issue that would be good to start contributing changes to AS 7. Within the add-user utility add a check for existing users and if the user does exist ask the user to confirm if they want to update the password of that user. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

5
8
0 / 0

[JBoss JIRA] Created: (AS7-1753) Intermittent failure in CompositeOperationHandlerUnitTestCase testRestartRequired

by Brian Stansberry (JIRA)

Intermittent failure in CompositeOperationHandlerUnitTestCase testRestartRequired --------------------------------------------------------------------------------- Key: AS7-1753 URL: https://issues.jboss.org/browse/AS7-1753 Project: Application Server 7 Issue Type: Bug Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.1.0.Alpha1 This pops up occasionally <testcase time="0.203" classname="org.jboss.as.controller.CompositeOperationHandlerUnitTestCase" name="testRestartRequired"> <failure message="expected:<[restart-requir]ed> but was:<[undefin]ed>" type="org.junit.ComparisonFailure">org.junit.ComparisonFailure: expected:<[restart-requir]ed> but was:<[undefin]ed> at org.junit.Assert.assertEquals(Assert.java:123) at org.junit.Assert.assertEquals(Assert.java:145) at org.jboss.as.controller.CompositeOperationHandlerUnitTestCase.testRestartRequired(CompositeOperationHandlerUnitTestCase.java:496) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) at org.junit.runners.ParentRunner.run(ParentRunner.java:236) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164) at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110) at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:172) at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcessWhenForked(SurefireStarter.java:104) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:70) </failure> <system-out>========= New Test { "outcome" => "success", "result" => { "step-1" => { "outcome" => "success", "result" => 1, "response-headers" => { "runtime-update-skipped" => true, "operation-requires-restart" => true } }, "step-2" => { "outcome" => "success", "result" => 2 } } } ====================== </system-out> </testcase> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

4
6
0 / 0

[JBoss JIRA] (AS7-2684) CLI should when making changes...log the current logged in user in the written out XML file

by Jim Tyrrell (Created) (JIRA)

CLI should when making changes...log the current logged in user in the written out XML file ------------------------------------------------------------------------------------------- Key: AS7-2684 URL: https://issues.jboss.org/browse/AS7-2684 Project: Application Server 7 Issue Type: Feature Request Components: CLI Reporter: Jim Tyrrell Assignee: Alexey Loubyansky Some notion of logging who is making changes to the domain needs to be logged so that troubleshooting who is making changes to the configurations can be tracked/figured out. A comment in the domain and or host.xml is all that is required. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

4
3
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 February 2012