[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, 4 months
[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, 4 months
[JBoss JIRA] (SECURITY-653) JBossPDP isDirectory called should check if the argument is of file pattern
by Anil Saldhana (JIRA)
Anil Saldhana created SECURITY-653:
--------------------------------------
Summary: JBossPDP isDirectory called should check if the argument is of file pattern
Key: SECURITY-653
URL: https://issues.jboss.org/browse/SECURITY-653
Project: PicketBox (JBoss Security and Identity Management)
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: JBossXACML
Affects Versions: jbossxacml_2.0.6.Final
Reporter: Anil Saldhana
Assignee: Anil Saldhana
Fix For: picketbox_xacml_2.0.7.Final
https://issues.jboss.org/browse/JBPAPP-8462 has an exception for the AS7 environment.
======================
15:51:51,112 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/pdp].[SOAPSAMLXACMLPDPServlet]] (http--127.0.0.1-8080-1) Allocate exception for servlet SOAPSAMLXACMLPDPServlet: java.lang.IllegalArgumentException: URI scheme is not "file"
at java.io.File.<init>(File.java:366) [rt.jar:1.6.0_31]
at org.jboss.security.xacml.core.JBossPDP.isDirectory(JBossPDP.java:590) [jbossxacml-2.0.6.Final.jar:2.0.6.Final]
at org.jboss.security.xacml.core.JBossPDP.addPolicySets(JBossPDP.java:466) [jbossxacml-2.0.6.Final.jar:2.0.6.Final]
at org.jboss.security.xacml.core.JBossPDP.bootstrap(JBossPDP.java:344) [jbossxacml-2.0.6.Final.jar:2.0.6.Final]
at org.jboss.security.xacml.core.JBossPDP.<init>(JBossPDP.java:157) [jbossxacml-2.0.6.Final.jar:2.0.6.Final]
at org.picketlink.identity.federation.core.pdp.SOAPSAMLXACMLPDP.getPDP(SOAPSAMLXACMLPDP.java:126) [picketlink-fed-2.0.2.Final.jar:2.0.2.Final]
at org.picketlink.identity.federation.core.pdp.SOAPSAMLXACMLPDP.<init>(SOAPSAMLXACMLPDP.java:75) [picketlink-fed-2.0.2.Final.jar:2.0.2.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, 4 months
[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, 4 months