as7-master-testsuite-ip6 - Build # 5918 - Failure!
by ci-builds＠redhat.com
as7-master-testsuite-ip6 - Build # 5918 - Failure:
Check console output at to view the results.
Public: http://hudson.jboss.org/hudson/job/as7-master-testsuite-ip6/5918
Internal: http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-master-testsui...
Test summary:
1 tests failed.
REGRESSION: org.jboss.as.test.integration.osgi.webapp.WebAppTestCase.testOSGiStructureDeployment
Error Message:
java.util.concurrent.ExecutionException: java.io.IOException: <html><head><title>JBoss Web/7.2.0.Alpha5 - JBWEB000064: Error report</title><style><!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}--></style> </head><body><h1>JBWEB000065: HTTP Status 500 - No resources</h1><HR size="1" noshade="noshade"><p><b>JBWEB000309: type</b> JBWEB000066: Exception report</p><p><b>JBWEB000068: message</b> <u>No resources</u></p><p><b>JBWEB000069: description</b> <u>JBWEB000145: The server encountered an internal error that prevented it from fulfilling this request.</u></p><p><b>JBWEB000070: exception</b> <pre>javax.servlet.ServletException: No resources org.apache.catalina.servlets.DefaultServlet.init(DefaultServlet.java:278) javax.servlet.GenericServlet.init(GenericServlet.java:242) org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:652) org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:919) java.lang.Thread.run(Thread.java:662) </pre></p><p><b>JBWEB000071: root cause</b> <pre>javax.naming.NameNotFoundException: comp/Resources -- service jboss.naming.context.java.comp.Resources org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:103) org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193) org.jboss.as.naming.InitialContext.lookup(InitialContext.java:120) org.jboss.as.naming.NamingContext.lookup(NamingContext.java:182) org.jboss.as.naming.NamingContext.lookup(NamingContext.java:178) javax.naming.InitialContext.lookup(InitialContext.java:392) org.apache.catalina.servlets.DefaultServlet.init(DefaultServlet.java:273) javax.servlet.GenericServlet.init(GenericServlet.java:242) org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:652) org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:919) java.lang.Thread.run(Thread.java:662) </pre></p><p><b>JBWEB000072: note</b> <u>JBWEB000073: The full stack trace of the root cause is available in the JBoss Web/7.2.0.Alpha5 logs.</u></p><HR size="1" noshade="noshade"><h3>JBoss Web/7.2.0.Alpha5</h3></body></html>
11 years, 4 months
Provide access to OSGiMetaData for server, web, etc
by Thomas Diesler
Folks,
currently we have a policy that server does not have a dependency on OSGi API and as a result on OSGiMetaData.
In several places we do a check like this
if (depUnit.hasAttachment(Attachments.OSGI_MANIFEST)) {
...
}
This however implies that the Manifest is the only possible source of valid OSGi metadata. The OSGi webapp spec allows for metadata to be specified as part of a "webbundle://" URI (see AS7-6006)
To make this work, the integration code currently generates a Manifest and later OSGiMetaData from it. The above code still works even if the deployment content does not have a Manifest.
I propose to move the OSGiMetaData one level up so that
if (depUnit.hasAttachment(Attachments.OSGI_METADATA)) {
...
}
can be the deciding criteria. As a additional benefit web would no longer need to produce/consume the raw Manifest headers and OSGiMetaData would be treated like all other metadata structures.
cheers
--thomas
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
11 years, 4 months
[OSGi WAB support] webbundle: URL handler
by David Bosschaert
Hi all,
As part of making the JBoss OSGi Web Application Support compliant with
the spec I have started running it through the OSGi TCK.
I noticed that the TCK depends heavily on the webbundle: URL protocol
which is specified in section 128.4 of the specification - it is not an
optional piece. So in order to support this we need to provide such a
URL handler.
As the webbundle: handler is never part of runtime operation (it only
converts a WAR file into a WAB file on the fly) I was looking into
possibly using existing implementations of the URL handler instead.
However the ones that I found are quite heavy on the dependencies. The
implementation in Aries depends on Blueprint being present and the one
in Pax has about 10 other dependencies (including junit) - they drag in
too much baggage IMHO.
So I'm starting to come to the conclusion that we need to provide such
an implementation as part of the OSGi webbundle support in AS7. The JIRA
is https://issues.jboss.org/browse/AS7-6006
Any other ideas?
Cheers,
David
11 years, 4 months
as7-master-testsuite-ip6 - Build # 5904 - Failure!
by ci-builds＠redhat.com
as7-master-testsuite-ip6 - Build # 5904 - Failure:
Check console output at to view the results.
Public: http://hudson.jboss.org/hudson/job/as7-master-testsuite-ip6/5904
Internal: http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-master-testsui...
Test summary:
53 tests failed.
REGRESSION: org.jboss.as.test.integration.deployment.deploymentoverlay.DeploymentOverlayTestCase.testContentOverridden
Error Message:
expected:<[]OVERRIDDEN> but was:<[NON ]OVERRIDDEN>
REGRESSION: org.jboss.as.test.integration.deployment.deploymentoverlay.DeploymentOverlayTestCase.testAddingNewFile
Error Message:
null
REGRESSION: org.jboss.as.test.integration.deployment.xml.datasource.DeployedXmlDataSourceManagementTestCase.testDeployedDatasourceInManagementModel
Error Message:
expected:<[jdbc:h2:mem:test;DB_CLOSE_DELAY=-1]> but was:<[undefined]>
REGRESSION: org.jboss.as.test.integration.deployment.xml.datasource.DeployedXmlDataSourceManagementTestCase.testDeployedXaDatasourceInManagementModel
Error Message:
expected:<[h2]> but was:<[undefined]>
REGRESSION: org.jboss.as.test.integration.deployment.xml.datasource.DeployedXmlDataSourceManagementTestCase.testDeployedXaDatasourcePropertiesInManagementModel
Error Message:
expected:<[jdbc:h2:mem:test]> but was:<[undefined]>
REGRESSION: org.jboss.as.test.integration.deployment.xml.datasource.DeployedXmlDataSourceManagementTestCase.testDeployedDatasourceStatisticsInManagementModel
Error Message:
ActiveCount
REGRESSION: org.jboss.as.test.integration.deployment.xml.datasource.DeployedXmlDataSourceManagementTestCase.testDeployedXaDatasourceStatisticsInManagementModel
Error Message:
ActiveCount
REGRESSION: org.jboss.as.test.integration.deployment.xml.datasource.DeployedXmlDataSourceTestCase.testDeployedDataSource
Error Message:
datasources/DeployedDS -- service jboss.naming.context.java.jboss.datasources.DeployedDS
REGRESSION: org.jboss.as.test.integration.deployment.xml.datasource.DeployedXmlDataSourceTestCase.testDeployedXaDataSource
Error Message:
H2XADS -- service jboss.naming.context.java.H2XADS
REGRESSION: org.jboss.as.test.integration.ejb.client.descriptor.EJBClientDescriptorTestCase.testEJBClientContextConfiguration
Error Message:
Cannot deploy: ejb-client-descriptor-test.jar
REGRESSION: org.jboss.as.test.integration.ejb.client.descriptor.EJBClientDescriptorTestCase.testLocalAndRemoteReceiversClientConfig
Error Message:
Cannot deploy: ejb-client-descriptor-with-local-and-remote-receivers-test.jar
REGRESSION: org.jboss.as.test.integration.ejb.client.descriptor.EJBClientDescriptorTestCase.testClientInvocationTimeout
Error Message:
Cannot deploy: ejb-client-descriptor-test-with-jboss-ejb-client_1_2_xml.jar
REGRESSION: org.jboss.as.test.integration.ejb.remote.byreference.RemoteInvocationByReferenceTestCase.testPassByReferenceSemanticsOnRemoteInterface
Error Message:
Invocation on remote interface of a EJB did *not* use pass-by-reference semantics expected:<[fo]o> but was:<[hell]o>
REGRESSION: org.jboss.as.test.integration.ejb.remote.distinctname.defaultname.DefaultDistinctNameTestCase.testRemoteSLSBInvocation
Error Message:
EJBCLIENT000025: No EJB receiver available for handling [appName:, moduleName:remote-ejb-distinct-name-jar-test-case, distinctName:distinct-name-in-jboss-ejb3-xml] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@12768ace
REGRESSION: org.jboss.as.test.integration.ejb.remote.distinctname.defaultname.DefaultDistinctNameTestCase.testRemoteSFSBInvocation
Error Message:
Failed to create proxy
REGRESSION: org.jboss.as.test.integration.ejb.remote.distinctname.defaultname.DefaultDistinctNameTestCase.testRemoteSingletonInvocation
Error Message:
EJBCLIENT000025: No EJB receiver available for handling [appName:, moduleName:remote-ejb-distinct-name-jar-test-case, distinctName:distinct-name-in-jboss-ejb3-xml] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@70afe432
REGRESSION: org.jboss.as.test.integration.ejb.stateful.passivation.PassivationSucceedsUnitTestCase.testPassivationMaxSize
Error Message:
@PrePassivate not called, check cache configuration and client sleep time
REGRESSION: org.jboss.as.test.integration.ejb.stateful.passivation.PassivationSucceedsUnitTestCase.testPassivationIdleTimeout
Error Message:
@PostActivate not called, check CacheConfig and client sleep time
REGRESSION: org.jboss.as.test.integration.ejb.stateful.passivation.ejb2.PassivationSucceedsEJB2TestCase.testPassivationMaxSize
Error Message:
ejbPassivate not called on remote1, check cache configuration and client sleep time
REGRESSION: org.jboss.as.test.integration.ejb.stateful.passivation.ejb2.PassivationSucceedsEJB2TestCase.testPassivationIdleTimeout
Error Message:
ejbActivate not called, check CacheConfig and client sleep time
FAILED: org.jboss.as.test.integration.ejb.stateless.pooling.ejb2.EjbRemoveUnitTestCase.org.jboss.as.test.integration.ejb.stateless.pooling.ejb2.EjbRemoveUnitTestCase
Error Message:
Cannot deploy: test-session-remove.jar
REGRESSION: org.jboss.as.test.integration.jca.beanvalidation.DisabledValidationTestCase.testWrongAO
Error Message:
Cannot deploy: wrong-ao.rar
REGRESSION: org.jboss.as.test.integration.jca.beanvalidation.DisabledValidationTestCase.testWrongCf
Error Message:
Cannot deploy: wrong-cf.rar
REGRESSION: org.jboss.as.test.integration.jca.beanvalidation.DisabledValidationTestCase.testWrongRA
Error Message:
Cannot deploy: wrong-ra.rar
REGRESSION: org.jboss.as.test.integration.jca.statistics.IronJacamarDeploymentStatisticsTestCase.testOneConnection
Error Message:
Management operation failed: "JBAS014739: No handler for flush-all-connection-in-pool at address [ (\"deployment\" => \"archive1.rar\"), (\"subsystem\" => \"resource-adapters\"), (\"ironjacamar\" => \"ironjacamar\"), (\"resource-adapter\" => \"archive1.rar\"), (\"connection-definitions\" => \"java:jboss/ConnectionFactory1\") ]"
REGRESSION: org.jboss.as.test.integration.management.cli.DataSourceTestCase.testXaDataSource
Error Message:
Expected: <null> but was: java:jboss/datasources/StatXaDS
REGRESSION: org.jboss.as.test.integration.naming.ObjectFactoryWithEnvironmentBindingTestCase.testBindingWithEnvironment
Error Message:
b -- service jboss.naming.context.java.global.b
FAILED: org.jboss.as.test.integration.security.auditing.SecurityAuditingTestCase.org.jboss.as.test.integration.security.auditing.SecurityAuditingTestCase
Error Message:
Cannot deploy: form-auth.war
FAILED: org.jboss.as.test.integration.security.jaas.JAASIdentityCachingTestCase.org.jboss.as.test.integration.security.jaas.JAASIdentityCachingTestCase
Error Message:
Cannot deploy: ear-jaas-test.ear
FAILED: org.jboss.as.test.integration.security.jacc.JACCForEarModulesTestCase.org.jboss.as.test.integration.security.jacc.JACCForEarModulesTestCase
Error Message:
Cannot deploy: ear-jacc-test.ear
FAILED: org.jboss.as.test.integration.security.jacc.JACCTranslateServletDDTestCase.org.jboss.as.test.integration.security.jacc.JACCTranslateServletDDTestCase
Error Message:
Cannot deploy: jacc-test.war
FAILED: org.jboss.as.test.integration.security.jaspi.BasicJASPITestCase.org.jboss.as.test.integration.security.jaspi.BasicJASPITestCase
Error Message:
Cannot deploy: jaspi-test.war
FAILED: org.jboss.as.test.integration.security.jaspi.StackingJASPITestCase.org.jboss.as.test.integration.security.jaspi.StackingJASPITestCase
Error Message:
Cannot deploy: jaspi-test-1.war
FAILED: org.jboss.as.test.integration.security.loginmodules.CustomLoginModuleTestCase.org.jboss.as.test.integration.security.loginmodules.CustomLoginModuleTestCase
Error Message:
Cannot deploy: custom-login-module.war
FAILED: org.jboss.as.test.integration.security.loginmodules.DatabaseLoginModuleTestCase.org.jboss.as.test.integration.security.loginmodules.DatabaseLoginModuleTestCase
Error Message:
Cannot deploy: DEP1.war
FAILED: org.jboss.as.test.integration.security.loginmodules.IdentityLoginModuleTestCase.org.jboss.as.test.integration.security.loginmodules.IdentityLoginModuleTestCase
Error Message:
Cannot deploy: IdentityLoginModule-defaultPrincipal.war
FAILED: org.jboss.as.test.integration.security.loginmodules.RunAsLoginModuleTestCase.org.jboss.as.test.integration.security.loginmodules.RunAsLoginModuleTestCase
Error Message:
Cannot deploy: RunAsLoginModule.war
FAILED: org.jboss.as.test.integration.security.loginmodules.UsersRolesLoginModuleTestCase.org.jboss.as.test.integration.security.loginmodules.UsersRolesLoginModuleTestCase
Error Message:
Cannot deploy: UsersRoles-externalFiles.war
REGRESSION: org.jboss.as.test.integration.security.perimeter.WebConsoleSecurityTestCase.testGet
Error Message:
consoleURL should have been initialized!
REGRESSION: org.jboss.as.test.integration.security.perimeter.WebConsoleSecurityTestCase.testPost
Error Message:
consoleURL should have been initialized!
REGRESSION: org.jboss.as.test.integration.security.perimeter.WebConsoleSecurityTestCase.testHead
Error Message:
consoleURL should have been initialized!
REGRESSION: org.jboss.as.test.integration.security.perimeter.WebConsoleSecurityTestCase.testOptions
Error Message:
consoleURL should have been initialized!
REGRESSION: org.jboss.as.test.integration.security.perimeter.WebConsoleSecurityTestCase.testPut
Error Message:
consoleURL should have been initialized!
REGRESSION: org.jboss.as.test.integration.security.perimeter.WebConsoleSecurityTestCase.testTrace
Error Message:
consoleURL should have been initialized!
REGRESSION: org.jboss.as.test.integration.security.perimeter.WebConsoleSecurityTestCase.testDelete
Error Message:
consoleURL should have been initialized!
FAILED: org.jboss.as.test.integration.security.xacml.EjbXACMLAuthorizationModuleTestCase.org.jboss.as.test.integration.security.xacml.EjbXACMLAuthorizationModuleTestCase
Error Message:
Cannot deploy: test-custom-xacml.jar
FAILED: org.jboss.as.test.integration.security.xacml.WebXACMLAuthorizationModuleTestCase.org.jboss.as.test.integration.security.xacml.WebXACMLAuthorizationModuleTestCase
Error Message:
Cannot deploy: xacml-web-test.war
FAILED: org.jboss.as.test.integration.web.rootcontext.RootContextEarUnitTestCase.org.jboss.as.test.integration.web.rootcontext.RootContextEarUnitTestCase
Error Message:
Cannot deploy: root-web.ear
FAILED: org.jboss.as.test.integration.web.rootcontext.RootContextWarUnitTestCase.org.jboss.as.test.integration.web.rootcontext.RootContextWarUnitTestCase
Error Message:
Cannot deploy: root-context.war
REGRESSION: org.jboss.as.test.integration.web.valve.ValveUnitTestCase.testValve
Error Message:
null
FAILED: org.jboss.as.test.integration.ws.authentication.EJBEndpointAuthenticationTestCase.org.jboss.as.test.integration.ws.authentication.EJBEndpointAuthenticationTestCase
Error Message:
Cannot deploy: jaxws-authentication-ejb.jar
FAILED: org.jboss.as.test.integration.ws.authentication.EJBEndpointSecuredWSDLAccessTestCase.org.jboss.as.test.integration.ws.authentication.EJBEndpointSecuredWSDLAccessTestCase
Error Message:
Cannot deploy: jaxws-authentication-ejb3-for-wsdl.jar
FAILED: org.jboss.as.test.integration.ws.authentication.PojoEndpointAuthenticationTestCase.org.jboss.as.test.integration.ws.authentication.PojoEndpointAuthenticationTestCase
Error Message:
Cannot deploy: jaxws-authentication-pojo.war
11 years, 4 months
