January 2012 - jboss-jira - Jboss List Archives

[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, 3 months

2
1
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, 3 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, 3 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, 3 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, 3 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, 3 months

4
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-880) Hard-coded localhost in ejb3 test suite

by Aleksandar Kostadinov (JIRA)

Hard-coded localhost in ejb3 test suite --------------------------------------- Key: EJBTHREE-880 URL: http://jira.jboss.com/jira/browse/EJBTHREE-880 Project: EJB 3.0 Issue Type: Bug Reporter: Aleksandar Kostadinov When the ejb3 testsuite is run with "-Dnode0=IP1 -Dnode1=IP2" and IP1!=localhost there are some tests failing with "Retries exceeded, couldn't reconnect to 127.0.0.1:####". I see this for 4_0 and 4_2 jboss branches, but guess it's the same with head. One of the testcases is IiopRemoteUnitTestCase. I've checked ejb3/src/test/org/jboss/ejb3/test/iiop/unit/IiopRemoteUnitTestCase.java and there is 'props.put("java.naming.provider.url", "corbaloc::localhost:3528/NameService");'. Instead of localhost there should be used the node0 property. I guess the others have the same problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

6
16
0 / 0

[JBoss JIRA] (JBRULES-3303) Memory leak in RuleBaseEventSupport.listeners when loading StatefulKnowledgeSession - Test Attached

by Greg Chrystall (Created) (JIRA)

Memory leak in RuleBaseEventSupport.listeners when loading StatefulKnowledgeSession - Test Attached --------------------------------------------------------------------------------------------------- Key: JBRULES-3303 URL: https://issues.jboss.org/browse/JBRULES-3303 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core (flow) Affects Versions: 5.3.0.Final Environment: Linux, Java 1.6.0_24 Reporter: Greg Chrystall Assignee: Mark Proctor Attachments: mem-leak-test.tar.gz When loading a Drools Flow StatefulKnowledgeSession with JPAKnowledgeService.loadStatefulKnowledgeSession, AbstractEventSupport.listeners has 2 listeners added to it. When the StatefulKnowledgeSession is disposed() only 1 of the listeners is removed. In the attached test this causes 100 ReteooStatefulSession objects to stay alive. -- 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, 3 months

6
6
0 / 0

[JBoss JIRA] Created: (JBAS-9259) Provide an option to change the code source used by deployments

by David Lloyd (JIRA)

Provide an option to change the code source used by deployments --------------------------------------------------------------- Key: JBAS-9259 URL: https://issues.jboss.org/browse/JBAS-9259 Project: JBoss Application Server Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Modules / Class-loading, VFS Reporter: David Lloyd Priority: Minor Fix For: 7.0.0.CR1 For most use cases, using the VFS URL for the code source is best. However in certain cases the code source is expected to correspond to a physical filesystem location, possibly even a valid JAR URL. So there should be an option in jboss-deployment-structure.xml to allow the code source to be changed to be the URL of the physical location of the VFS mount point instead of the VFS root URL. This option would default to "off", meaning use the VFS URL. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

9
16
0 / 0

[JBoss JIRA] (AS7-2593) Hang in IIOPNamingTestCase with OpenJDK

by Carlo de Wolf (Created) (JIRA)

Hang in IIOPNamingTestCase with OpenJDK --------------------------------------- Key: AS7-2593 URL: https://issues.jboss.org/browse/AS7-2593 Project: Application Server 7 Issue Type: Bug Components: IIOP Environment: java version "1.6.0_22" OpenJDK Runtime Environment (IcedTea6 1.10.4) (fedora-60.1.10.4.fc15-x86_64) OpenJDK 64-Bit Server VM (build 20.0-b11, mixed mode) Reporter: Carlo de Wolf Assignee: Stefan Guilhen -- 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, 3 months

5
7
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 January 2012