January 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-8198) DomainController discovery system

by Brian Stansberry (JIRA)

DomainController discovery system --------------------------------- Key: JBAS-8198 URL: https://jira.jboss.org/browse/JBAS-8198 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: 7.0.0.M1 Mechanism(s) by which a ServerManager finds a DomainController so it can begin the process of integrating into the domain. Task includes the host.xml schema elements to configure this, the domain object model classes behind those elements, and the actual implementation of discovery from both the ServerManager and DomainController sides. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

7
14
0 / 0

[JBoss JIRA] Created: (JBAS-8139) Ability to rollback AS version updates

by Brian Stansberry (JIRA)

Ability to rollback AS version updates -------------------------------------- Key: JBAS-8139 URL: https://jira.jboss.org/browse/JBAS-8139 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: Unscheduled This JIRA is based on feedback we received after the Andiamo BOF at JBoss World 2010: >> A fixpack installer that handles version rollbacks would be fantastic. >> Of course it needs to remain flexible to work with JBoss installs that >> have been manually modified. Note that this may be out of scope for community AS 7; e.g. it may be a JON function. However, the AS 7 design of things like how we lay down content on the filesystem should take this use case into account. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

3
4
0 / 0

[JBoss JIRA] Created: (JBAS-8842) Security checks when recursively reading resources

by Emanuel Muckenhuber (JIRA)

Security checks when recursively reading resources -------------------------------------------------- Key: JBAS-8842 URL: https://issues.jboss.org/browse/JBAS-8842 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 7.0.0.Alpha1 Reporter: Emanuel Muckenhuber Assignee: Darran Lofthouse Currently the "read-resource" operation (GlobalOperationHandlers.ReadResourceHandler) just clones the subModel when recursively reading resources. We need to make sure that to also check the permissions for the children a node contains. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

5
7
0 / 0

[JBoss JIRA] (AS7-2626) Trailing forgotten --> does not generate a good error message on host.xml

by Jim Tyrrell (Created) (JIRA)

Trailing forgotten --> does not generate a good error message on host.xml ------------------------------------------------------------------------- Key: AS7-2626 URL: https://issues.jboss.org/browse/AS7-2626 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Reporter: Jim Tyrrell Assignee: Brian Stansberry This snippet from the host.xml file, note the --> that was forgotten to be removed in the remote line... <domain-controller>   </domain-controller> Generates this error message: [Host Controller] 21:24:51,341 ERROR [org.jboss.as.controller] (Controller Boot Thread) JBAS014601: Error booting the container: java.lang.RuntimeException: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration Several lines further down...you get this message... [Host Controller] Caused by: com.ctc.wstx.exc.WstxParsingException: Received non-all-whitespace CHARACTERS or CDATA event in nextTag(). [Host Controller] at [row,col {unknown-source}]: [44,4] It would be nice if the first error message in an XML parsing error would just show me the place it failed, along with maybe the prior line. Less nice would be the 44,4 to be in the first message and break it down as line 44, character 4. More verbosity would be nice. -- 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

11 years, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (AS7-1103) Intermittent failures in org.jboss.as.controller.CompositeOperationHandlerUnitTestCase

by James Perkins (JIRA)

Intermittent failures in org.jboss.as.controller.CompositeOperationHandlerUnitTestCase -------------------------------------------------------------------------------------- Key: AS7-1103 URL: https://issues.jboss.org/browse/AS7-1103 Project: Application Server 7 Issue Type: Bug Reporter: James Perkins Assignee: Brian Stansberry Fix For: 7.0.0.CR1 Below is the message from the error. ------------------------------------------------------------------------------- Test set: org.jboss.as.controller.CompositeOperationHandlerUnitTestCase ------------------------------------------------------------------------------- Tests run: 24, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.625 sec <<< FAILURE! testRestartRequired(org.jboss.as.controller.CompositeOperationHandlerUnitTestCase) Time elapsed: 0.031 sec <<< FAILURE! 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:119) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:101) 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.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103) at $Proxy0.invoke(Unknown Source) at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150) at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:91) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

7
12
0 / 0

[JBoss JIRA] (AS7-2625) No Spaces Allowed in Host -> Name, but ' do work, odd

by Jim Tyrrell (Created) (JIRA)

No Spaces Allowed in Host -> Name, but ' do work, odd ----------------------------------------------------- Key: AS7-2625 URL: https://issues.jboss.org/browse/AS7-2625 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Reporter: Jim Tyrrell Assignee: Brian Stansberry For some reason spaces do not seem to be allowed, but an Apostrophe seems to be okay. [Host Controller] 20:56:20,250 ERROR [org.jboss.as.controller] (Controller Boot Thread) JBAS014601: Error booting the container: java.lang.IllegalArgumentException: JBAS014719: Invalid value specification Jim's Most_Excellent_Domain_Ever_so_here Would be nice if the error message would kick out what values are acceptable? -- 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

11 years, 5 months

4
4
0 / 0

[JBoss JIRA] Created: (AS7-762) Provide an operation to request service status report after server has been started

by Heiko Braun (JIRA)

Provide an operation to request service status report after server has been started ------------------------------------------------------------------------------------- Key: AS7-762 URL: https://issues.jboss.org/browse/AS7-762 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Reporter: Heiko Braun Assignee: Brian Stansberry For proper healthcare it would beneficial if I could verify the server status after is has been started. I.e. to catch these, which currently only appear in the server log: [Server:server-three] 17:48:26,636 INFO [org.jboss.as.server] (MSC service thread 1-2) Service status report [Server:server-three] New missing/unsatisfied dependencies: [Server:server-three] service jboss.binding.http2 (missing) [Server:server-three] [Server:server-three] 17:48:26,636 ERROR [org.jboss.as] (MSC service thread 1-4) JBoss AS 7.0.0.Beta4-SNAPSHOT "(TBD)" started (with errors) in 3893ms - Started 101 of 149 services (1 services failed or missing dependencies, 47 services are passive or on-demand) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

5
10
0 / 0

[JBoss JIRA] (AS7-3406) Authorization check for JMX

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-3406: ------------------------------------- Summary: Authorization check for JMX Key: AS7-3406 URL: https://issues.jboss.org/browse/AS7-3406 Project: Application Server 7 Issue Type: Sub-task Components: JMX, Remoting, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse -- 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

11 years, 5 months

1
4
0 / 0

[JBoss JIRA] (AS7-3407) Authorization check for JNDI

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-3407: ------------------------------------- Summary: Authorization check for JNDI Key: AS7-3407 URL: https://issues.jboss.org/browse/AS7-3407 Project: Application Server 7 Issue Type: Sub-task Components: Naming, Remoting, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.1.0.Final -- 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

11 years, 5 months

1
4
0 / 0

[JBoss JIRA] (AS7-3414) Symbolic links inside deployed ear/war are not followed by web server

by Ronen Angluster (JIRA)

Ronen Angluster created AS7-3414: ------------------------------------ Summary: Symbolic links inside deployed ear/war are not followed by web server Key: AS7-3414 URL: https://issues.jboss.org/browse/AS7-3414 Project: Application Server 7 Issue Type: Bug Components: Web Services Affects Versions: 7.1.0.CR1, 7.1.0.Beta1 Environment: Fedora 16 Reporter: Ronen Angluster Assignee: Alessio Soldano when creating a symbolic link inside a deployed ear/war the symbolic link's target is not followed when accessing it from a web browser i.e. in jboss-as/standalone/deplyoment/somedomain.ear/files we created a symbolic link named "version.js" which points to /usr/share/something/version.js the target file (/usr/share/...) is accessible by all (chmod'd to 777) and is readable by the jboss-as user which runs the Jboss application server. when accessing http://domain:8080/something/files/version.js we get an 404 error, seems like the file is not found by the server. when placing the file instead of symbolic link, the file is accessible and all is well -- 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

11 years, 5 months

7
10
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2012