[JBoss JIRA] Created: (JBAS-9387) JBoss fail to startup after formatting $JBOSS_HOME/server/$PROFILE/conf/bootstrap/profile.xml
by Marcelo Guimarães (JIRA)
JBoss fail to startup after formatting $JBOSS_HOME/server/$PROFILE/conf/bootstrap/profile.xml
---------------------------------------------------------------------------------------------
Key: JBAS-9387
URL: https://issues.jboss.org/browse/JBAS-9387
Project: Legacy JBoss Application Server 6
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 6.0.0.Final, JBossAS-5.1.0.GA, JBossAS-5.0.0.GA
Environment: Fedora 14 32-bits, kernel 2.6.35.13-91.fc14.i686.PAE, Oracle Java build 1.6.0_24-b07
Reporter: Marcelo Guimarães
If I edit the $JBOSS_HOME/server/$PROFILE/conf/bootstrap/profile.xml and format this part
<classloader name="profile-classloader" xmlns="urn:jboss:classloader:1.0" export-all="NON_EMPTY" import-all="true">
<root>${jboss.lib.url}jboss-profileservice-spi.jar</root>
...
to this one
<classloader name="profile-classloader" xmlns="urn:jboss:classloader:1.0" export-all="NON_EMPTY" import-all="true">
<root>
${jboss.lib.url}jboss-profileservice-spi.jar
</root>
I get an error in JBoss startup:
09:37:14,763 ERROR [AbstractKernelController] Error installing to Create: name=profile-classloader:0.0.0$MODULE state=Configured: java.lang.RuntimeException: Error creating VFS file for
file:/home/ataxexe/jboss/org/jboss-6.0.0.Final/lib/jboss-profileservice-spi.jar
at org.jboss.classloading.spi.vfs.dependency.VFSClassLoaderPolicyModule.determineVFSRoots(VFSClassLoaderPolicyModule.java:219) [jboss-classloading-vfs.jar:2.2.0.GA]
at org.jboss.classloading.spi.vfs.dependency.VFSClassLoaderPolicyModule.create(VFSClassLoaderPolicyModule.java:266) [jboss-classloading-vfs.jar:2.2.0.GA]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_24]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_24]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_24]
at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_24]
at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:60) [jboss-reflect.jar:2.2.0.GA]
at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:168) [jboss-reflect.jar:2.2.0.GA]
at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66) [jboss-reflect.jar:2.2.0.GA]
at org.jboss.kernel.plugins.dependency.KernelControllerContextAction$JoinpointDispatchWrapper.execute(KernelControllerContextAction.java:257) [jboss-kernel.jar:2.2.0.GA]
at org.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(ExecutionWrapper.java:47) [jboss-kernel.jar:2.2.0.GA]
at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchExecutionWrapper(KernelControllerContextAction.java:125) [jboss-kernel.jar:2.2.0.GA]
at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:72) [jboss-kernel.jar:2.2.0.GA]
at org.jboss.kernel.plugins.dependency.LifecycleAction.installActionInternal(LifecycleAction.java:202) [jboss-kernel.jar:2.2.0.GA]
at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:54) [jboss-kernel.jar:2.2.0.GA]
at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:42) [jboss-kernel.jar:2.2.0.GA]
at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:379) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2044) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1083) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1322) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1246) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1139) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:894) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:641) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBean(AbstractKernelDeployer.java:319) [jboss-kernel.jar:2.2.0.GA]
at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBeans(AbstractKernelDeployer.java:297) [jboss-kernel.jar:2.2.0.GA]
at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deploy(AbstractKernelDeployer.java:130) [jboss-kernel.jar:2.2.0.GA]
at org.jboss.kernel.plugins.deployment.BasicKernelDeployer.deploy(BasicKernelDeployer.java:76) [jboss-kernel.jar:2.2.0.GA]
at org.jboss.bootstrap.impl.mc.deployer.TempBasicXMLDeployer.deploy(TempBasicXMLDeployer.java:92) [jboss-bootstrap-impl-mc.jar:2.1.0-alpha-5]
at org.jboss.bootstrap.impl.mc.deployer.TempBasicXMLDeployer.deploy(TempBasicXMLDeployer.java:193) [jboss-bootstrap-impl-mc.jar:2.1.0-alpha-5]
at org.jboss.bootstrap.impl.mc.server.AbstractMCServerBase.bootstrapMcAndDescriptors(AbstractMCServerBase.java:310) [jboss-bootstrap-impl-mc.jar:2.1.0-alpha-5]
at org.jboss.bootstrap.impl.mc.server.AbstractMCServerBase.doStart(AbstractMCServerBase.java:257) [jboss-bootstrap-impl-mc.jar:2.1.0-alpha-5]
at org.jboss.bootstrap.impl.as.server.AbstractJBossASServerBase.doStart(AbstractJBossASServerBase.java:381) [jboss-bootstrap-impl-as.jar:2.1.0-alpha-5]
at org.jboss.bootstrap.impl.base.server.AbstractServer$StartServerTask.run(AbstractServer.java:413) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-5]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_24]
Caused by: java.net.URISyntaxException: Illegal character in scheme name at index 0:
file:/home/ataxexe/jboss/org/jboss-6.0.0.Final/lib/jboss-profileservice-spi.jar
at java.net.URI$Parser.fail(URI.java:2809) [:1.6.0_24]
at java.net.URI$Parser.checkChars(URI.java:2982) [:1.6.0_24]
at java.net.URI$Parser.checkChar(URI.java:2992) [:1.6.0_24]
at java.net.URI$Parser.parse(URI.java:3008) [:1.6.0_24]
at java.net.URI.<init>(URI.java:578) [:1.6.0_24]
at org.jboss.classloading.spi.vfs.dependency.VFSClassLoaderPolicyModule.determineVFSRoots(VFSClassLoaderPolicyModule.java:214) [jboss-classloading-vfs.jar:2.2.0.GA]
... 37 more
Failed to boot JBoss:
java.lang.Exception: Encountered exception in server startup
at org.jboss.bootstrap.impl.mc.server.AbstractMCServerBase.bootstrapMcAndDescriptors(AbstractMCServerBase.java:325)
at org.jboss.bootstrap.impl.mc.server.AbstractMCServerBase.doStart(AbstractMCServerBase.java:257)
at org.jboss.bootstrap.impl.as.server.AbstractJBossASServerBase.doStart(AbstractJBossASServerBase.java:381)
at org.jboss.bootstrap.impl.base.server.AbstractServer$StartServerTask.run(AbstractServer.java:413)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.IllegalStateException: Incompletely deployed:
DEPLOYMENTS IN ERROR:
Deployment "profile-classloader:0.0.0$MODULE" is in error due to: java.lang.RuntimeException: Error creating VFS file for
file:/home/ataxexe/jboss/org/jboss-6.0.0.Final/lib/jboss-profileservice-spi.jar
DEPLOYMENTS MISSING DEPENDENCIES:
Deployment "ScanningProfileFactory" is missing the following dependencies:
Dependency "DelegateModificationChecker" (should be in state "Installed", but is actually in state "Real")
Dependency "ProfileServiceConfig" (should be in state "Installed", but is actually in state "Real")
Dependency "ArtifactRepositoryManager" (should be in state "Installed", but is actually in state "Real")
Dependency "profile-classloader:0.0.0" (should be in state "Installed", but is actually in state "Described")
Deployment "WebVisitorAttributes" is missing the following dependencies:
Dependency "profile-classloader:0.0.0" (should be in state "Installed", but is actually in state "Described")
Deployment "BasicProfileFactory" is missing the following dependencies:
Dependency "ProfileServiceConfig" (should be in state "Installed", but is actually in state "Real")
Dependency "ArtifactRepositoryManager" (should be in state "Installed", but is actually in state "Real")
Dependency "profile-classloader:0.0.0" (should be in state "Installed", but is actually in state "Described")
Deployment "ArtifactRepositoryManager" is missing the following dependencies:
Dependency "profile-classloader:0.0.0" (should be in state "Installed", but is actually in state "Described")
Deployment "MavenArtifactMetaData" is missing the following dependencies:
Dependency "profile-classloader:0.0.0" (should be in state "Installed", but is actually in state "Described")
Deployment "ProfileLifeCycleCallbackActions" is missing the following dependencies:
Dependency "ActionController" (should be in state "Installed", but is actually in state "Real")
Dependency "profile-classloader:0.0.0" (should be in state "Installed", but is actually in state "Described")
Deployment "MainDeployerPlugin" is missing the following dependencies:
Dependency "profile-classloader:0.0.0" (should be in state "Installed", but is actually in state "Described")
Dependency "ProfileDeployerPluginRegistry" (should be in state "Installed", but is actually in state "Real")
Deployment "TypedProfileFactory" is missing the following dependencies:
Dependency "profile-classloader:0.0.0" (should be in state "Installed", but is actually in state "Described")
Deployment "KernelDeploymentComponentMapper" is missing the following dependencies:
Dependency "PersistenceFactory" (should be in state "Installed", but is actually in state "Real")
Dependency "profile-classloader:0.0.0" (should be in state "Installed", but is actually in state "Described")
Deployment "PersistenceFactory" is missing the following dependencies:
Dependency "profile-classloader:0.0.0" (should be in state "Installed", but is actually in state "Described")
Deployment "ProfileRepositoryFactory" is missing the following dependencies:
Dependency "profile-classloader:0.0.0" (should be in state "Installed", but is actually in state "Described")
Deployment "ProfileServiceConfig" is missing the following dependencies:
Dependency "ProfileLifeCycleCallbackActions" (should be in state "Installed", but is actually in state "Real")
Dependency "ProfileDeployerPluginRegistry" (should be in state "Installed", but is actually in state "Real")
Dependency "TypedProfileFactory" (should be in state "Installed", but is actually in state "Real")
Dependency "profile-classloader:0.0.0" (should be in state "Installed", but is actually in state "Described")
Deployment "StructureModCache" is missing the following dependencies:
Dependency "profile-classloader:0.0.0" (should be in state "Installed", but is actually in state "Described")
Deployment "DelegateModificationChecker" is missing the following dependencies:
Dependency "StructureModificationChecker" (should be in state "Installed", but is actually in state "Real")
Dependency "profile-classloader:0.0.0" (should be in state "Installed", but is actually in state "Described")
Deployment "ProfileDeployerPluginRegistry" is missing the following dependencies:
Dependency "jboss.kernel:service=Kernel" (should be in state "Installed", but is actually in state "**ERROR**")
Dependency "profile-classloader:0.0.0" (should be in state "Installed", but is actually in state "Described")
Deployment "MavenArtifactRepository" is missing the following dependencies:
Dependency "MavenArtifactMetaData" (should be in state "Installed", but is actually in state "Real")
Dependency "profile-classloader:0.0.0" (should be in state "Installed", but is actually in state "Described")
Deployment "UserProfileFactory" is missing the following dependencies:
Dependency "profile-classloader:0.0.0" (should be in state "Installed", but is actually in state "Described")
Deployment "AttachmentsSerializer" is missing the following dependencies:
Dependency "UserProfileFactory" (should be in state "Installed", but is actually in state "Real")
Dependency "profile-classloader:0.0.0" (should be in state "Installed", but is actually in state "Described")
Deployment "ServiceDeploymentComponentMapper" is missing the following dependencies:
Dependency "profile-classloader:0.0.0" (should be in state "Installed", but is actually in state "Described")
Dependency "PersistenceFactory" (should be in state "Installed", but is actually in state "Real")
Deployment "PersistenceRepository" is missing the following dependencies:
Dependency "AttachmentsSerializer" (should be in state "Installed", but is actually in state "Real")
Dependency "UserProfileFactory" (should be in state "Installed", but is actually in state "Real")
Dependency "PersistenceFactory" (should be in state "Installed", but is actually in state "Real")
Dependency "profile-classloader:0.0.0" (should be in state "Installed", but is actually in state "Described")
Deployment "ActionController" is missing the following dependencies:
Dependency "profile-classloader:0.0.0" (should be in state "Installed", but is actually in state "Described")
Deployment "StructureModificationChecker" is missing the following dependencies:
Dependency "StructureModCache" (should be in state "Installed", but is actually in state "Real")
Dependency "profile-classloader:0.0.0" (should be in state "Installed", but is actually in state "Described")
Deployment "profile-classloader:0.0.0" is missing the following dependencies:
Dependency "profile-classloader:0.0.0$MODULE" (should be in state "Installed", but is actually in state "**ERROR**")
Deployment "BootstrapProfileFactory" is missing the following dependencies:
Dependency "ArtifactRepositoryManager" (should be in state "Installed", but is actually in state "Real")
Dependency "ProfileServiceConfig" (should be in state "Installed", but is actually in state "Real")
Dependency "profile-classloader:0.0.0" (should be in state "Installed", but is actually in state "Described")
Deployment "HDScannerFactory" is missing the following dependencies:
Dependency "ActionController" (should be in state "Installed", but is actually in state "Real")
Dependency "profile-classloader:0.0.0" (should be in state "Installed", but is actually in state "Described")
Deployment "FileArtifactRepositoryFactory" is missing the following dependencies:
Dependency "ProfileServiceConfig" (should be in state "Installed", but is actually in state "Real")
Dependency "profile-classloader:0.0.0" (should be in state "Installed", but is actually in state "Described")
Deployment "ProfileServicePersistenceDeployer" is missing the following dependencies:
Dependency "profile-classloader:0.0.0" (should be in state "Installed", but is actually in state "Described")
Dependency "PersistenceRepository" (should be in state "Installed", but is actually in state "Real")
Deployment "ProfileServiceBootstrap" is missing the following dependencies:
Dependency "UserProfileFactory" (should be in state "Installed", but is actually in state "Real")
Dependency "HDScannerFactory" (should be in state "Installed", but is actually in state "Real")
Dependency "ProfileServiceConfig" (should be in state "Installed", but is actually in state "Real")
Dependency "jboss.kernel:service=Kernel" (should be in state "Installed", but is actually in state "**ERROR**")
Dependency "profile-classloader:0.0.0" (should be in state "Installed", but is actually in state "Described")
Deployment "HDScannerCallbackAction" is missing the following dependencies:
Dependency "HDScannerFactory" (should be in state "Installed", but is actually in state "Real")
Dependency "profile-classloader:0.0.0" (should be in state "Installed", but is actually in state "Described")
at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.internalValidate(AbstractKernelDeployer.java:278)
at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.validate(AbstractKernelDeployer.java:174)
at org.jboss.bootstrap.impl.mc.server.AbstractMCServerBase.bootstrapMcAndDescriptors(AbstractMCServerBase.java:314)
... 4 more
I also tested it in EAP 5.1, EAP 5.0, SOA-P 5.1, SOA-P 5.0 and EPP 5.1 (all fresh installs, no patches) and I got the same error.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] Created: (JBAS-9275) JavaEE 5 annotated Webservice-EJB fails
by Rainer Flicker (JIRA)
JavaEE 5 annotated Webservice-EJB fails
---------------------------------------
Key: JBAS-9275
URL: https://issues.jboss.org/browse/JBAS-9275
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 6.0.0.Final
Environment: JBoss AS 6.0.0.Final
JBoss Seam 2.2.1 Final
Oracle JDK 1.6.24
Windows XP SP3
Reporter: Rainer Flicker
A JavaEE 5 annotated Webservice-EJB (works with JBoss AS 5.1, Glassfish 2.1 and Websphere 7) fails with:
Caused by: java.lang.LinkageError: loader constraint violation in interface itable initialization: when resolving method "$Proxy280.setElementType(Ljavax/xml/namespace/QName;)V" the class loader (instance of org/jboss/classloader/spi/base/BaseClassLoader) of the current class, $Proxy280, and the class loader (instance of org/jboss/classloader/spi/base/BaseClassLoader) for interface javax/wsdl/extensions/ExtensibilityElement have different Class objects for the type javax/xml/namespace/QName used in the signature
at java.lang.Class.getDeclaredConstructors0(Native Method) [:1.6.0_24]
at java.lang.Class.privateGetDeclaredConstructors(Class.java:2389) [:1.6.0_24]
at java.lang.Class.getConstructor0(Class.java:2699) [:1.6.0_24]
at java.lang.Class.getConstructor(Class.java:1657) [:1.6.0_24]
at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:587) [:1.6.0_24]
at org.apache.cxf.tools.util.SOAPBindingUtil.getProxy(SOAPBindingUtil.java:87) [:2.3.1]
at org.apache.cxf.tools.util.SOAPBindingUtil.getSoapBinding(SOAPBindingUtil.java:274) [:2.3.1]
at org.apache.cxf.tools.util.SOAPBindingUtil.createSoapBinding(SOAPBindingUtil.java:426) [:2.3.1]
at org.apache.cxf.binding.soap.SoapBindingFactory.createSoapBinding(SoapBindingFactory.java:213) [:2.3.1]
at org.apache.cxf.binding.soap.SoapBindingFactory.createBindingInfo(SoapBindingFactory.java:198) [:2.3.1]
at org.apache.cxf.binding.AbstractBindingFactory.createBindingInfo(AbstractBindingFactory.java:97) [:2.3.1]
at org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createBindingInfo(AbstractWSDLBasedEndpointFactory.java:339) [:2.3.1]
at org.apache.cxf.jaxws.JaxWsServerFactoryBean.createBindingInfo(JaxWsServerFactoryBean.java:166) [:2.3.1]
at org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createEndpointInfo(AbstractWSDLBasedEndpointFactory.java:251) [:2.3.1]
at org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createEndpoint(AbstractWSDLBasedEndpointFactory.java:147) [:2.3.1]
at org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.java:148) [:2.3.1]
at org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(JaxWsServerFactoryBean.java:183) [:2.3.1]
at org.apache.cxf.jaxws.EndpointImpl.getServer(EndpointImpl.java:407) [:2.3.1]
at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:314) [:2.3.1]
at org.jboss.wsf.stack.cxf.deployment.EndpointImpl.doPublish(EndpointImpl.java:62) [:3.4.1.GA]
at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:238) [:2.3.1]
at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:481) [:2.3.1]
at org.jboss.wsf.stack.cxf.configuration.NonSpringBusHolder.configure(NonSpringBusHolder.java:112) [:3.4.1.GA]
at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.start(BusDeploymentAspect.java:110) [:3.4.1.GA]
at org.jboss.webservices.integration.deployers.WSDeploymentAspectDeployer.internalDeploy(WSDeploymentAspectDeployer.java:123) [:6.0.0.Final]
at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:55) [:2.2.0.GA]
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179) [:2.2.0.GA]
... 44 more
Webservice-EJB:
@Stateless
@WebService(name = "TestReportService",
serviceName = "AsmsWebservice",
targetNamespace= "http://webservice.asms.airsight.de")
@SOAPBinding(style = SOAPBinding.Style.DOCUMENT,
use = SOAPBinding.Use.LITERAL,
parameterStyle = SOAPBinding.ParameterStyle.WRAPPED)
public class TestReportService implements TestReportServiceRemote, Serializable {
@PersistenceContext
private EntityManager em;
@WebMethod(action = "createFullTestReport")
@WebResult(name="successful")
public boolean createFullTestReport(
@WebParam(name="name") String name,
@WebParam(name="id") Long id,
@WebParam(name="feedback") Boolean feedback,
@WebParam(name="altitude") Double altitude) {
return true;
}
}
@Remote
public interface TestReportServiceRemote {
public boolean createFullTestReport(String name, Long id, Boolean feedback, Double altitude);
}
standard-jaxws-endpoint-config.xml:
<jaxws-config xmlns="urn:jboss:jaxws-config:2.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:javaee="http://java.sun.com/xml/ns/javaee"
xsi:schemaLocation="urn:jboss:jaxws-config:2.0 jaxws-config_2_0.xsd">
<endpoint-config>
<config-name>Seam WebService Endpoint</config-name>
<pre-handler-chains>
<javaee:handler-chain>
<javaee:protocol-bindings>##SOAP11_HTTP</javaee:protocol-bindings>
<javaee:handler>
<javaee:handler-name>SOAP Request Handler</javaee:handler-name>
<javaee:handler-class>org.jboss.seam.webservice.SOAPRequestHandler</javaee:handler-class>
</javaee:handler>
</javaee:handler-chain>
</pre-handler-chains>
</endpoint-config>
</jaxws-config>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] Created: (JBAS-7909) AOPClassLoaderDeployer breaks OSGi integration
by Thomas Diesler (JIRA)
AOPClassLoaderDeployer breaks OSGi integration
----------------------------------------------
Key: JBAS-7909
URL: https://jira.jboss.org/jira/browse/JBAS-7909
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: AOP
Reporter: Thomas Diesler
Assignee: Kabir Khan
Fix For: JBossAS-6.0.0.M3
11:11:21,726 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to ClassLoader: name=vfs:///home/tdiesler/svn/jbossas/trunk/build/target/jboss-6.0.0-SNAPSHOT/server/default/deploy/osgi/org.osgi.compendium.jar state=Describe mode=Manual requiredState=ClassLoader: org.jboss.deployers.spi.DeploymentException: Error during deploy: vfs:///home/tdiesler/svn/jbossas/trunk/build/target/jboss-6.0.0-SNAPSHOT/server/default/deploy/osgi/org.osgi.compendium.jar
at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
Caused by: java.lang.IllegalStateException: Have ClassLoaderDomain@12078a{NOT_USED_PLACEHOLDER} but no classloader domain
at org.jboss.aop.asintegration.jboss5.AOPVFSClassLoaderDomainRegistry.validateInitMaps(AOPVFSClassLoaderDomainRegistry.java:85)
at org.jboss.classpool.plugins.jbosscl.VFSClassLoaderDomainRegistry.initMapsForModule(VFSClassLoaderDomainRegistry.java:119)
at org.jboss.classpool.plugins.jbosscl.RegisterModuleCallback.registerModule(RegisterModuleCallback.java:87)
at org.jboss.classpool.plugins.jbosscl.JBossClDelegatingClassPoolFactory.create(JBossClDelegatingClassPoolFactory.java:83)
at org.jboss.classpool.plugins.jbosscl.JBossClDelegatingClassPoolFactory.create(JBossClDelegatingClassPoolFactory.java:50)
at org.jboss.aop.asintegration.jboss5.JBoss5Integration.create(JBoss5Integration.java:157)
at org.jboss.classpool.scoped.ScopedClassPoolRepositoryImpl.createScopedClassPool(ScopedClassPoolRepositoryImpl.java:93)
at org.jboss.classpool.scoped.ScopedClassPoolRepositoryImpl.registerClassLoader(ScopedClassPoolRepositoryImpl.java:125)
at org.jboss.classpool.spi.ClassPoolRepository.registerClassLoader(ClassPoolRepository.java:138)
at org.jboss.aop.AspectManager.registerClassLoader(AspectManager.java:846)
at org.jboss.aop.asintegration.jboss5.VFSClassLoaderScopingPolicy.registerClassLoader(VFSClassLoaderScopingPolicy.java:46)
at org.jboss.aop.asintegration.jboss5.AOPClassLoaderInitializer.registerLoaders(AOPClassLoaderInitializer.java:84)
at org.jboss.aop.asintegration.jboss5.AOPClassLoaderInitializer.initializeForUnit(AOPClassLoaderInitializer.java:41)
at org.jboss.aop.asintegration.jboss5.AOPClassLoaderDeployer.internalDeploy(AOPClassLoaderDeployer.java:65)
at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:55)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] Created: (JBAS-8730) Hudson testsuite hangs because of Null deploymentHash
by Thomas Diesler (JIRA)
Hudson testsuite hangs because of Null deploymentHash
------------------------------------------------------
Key: JBAS-8730
URL: https://issues.jboss.org/browse/JBAS-8730
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Thomas Diesler
http://jbmuc.dyndns.org:8280/hudson/job/jbosgi-remote/6/console
09:32:34,528 INFO [org.jboss.as.server.deployment] (pool-5-thread-2) Content with name example-xservice-client-module added at location /usr/share/tomcat6/workspace/hudson-home/jobs/jbosgi-remote/workspace/jboss-7.0.0.Alpha2/standalone/data/content/00/7a37a86ec7949184af8867631ca10f61c1f7a1/content
09:32:34,612 ERROR [org.jboss.as.protocol.connection] (pool-5-thread-2) Failed to read a message: java.io.IOException: Failed to handle management operation
at org.jboss.as.protocol.mgmt.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:63)
at org.jboss.as.protocol.ConnectionImpl.safeHandleMessage(ConnectionImpl.java:239)
at org.jboss.as.protocol.ConnectionImpl$1$1.run(ConnectionImpl.java:198)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_22]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_22]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_22]
Caused by: java.lang.IllegalArgumentException: deploymentHash is null
at org.jboss.as.model.ServerModelDeploymentAdd.<init>(ServerModelDeploymentAdd.java:48)
at org.jboss.as.server.mgmt.deployment.ServerDeploymentManagerImpl.addServerGroupDeploymentUpdate(ServerDeploymentManagerImpl.java:302)
at org.jboss.as.server.mgmt.deployment.ServerDeploymentManagerImpl.execute(ServerDeploymentManagerImpl.java:211)
at org.jboss.as.server.standalone.management.ServerControllerOperationHandler$ExecuteDeploymentPlanOperation.sendResponse(ServerControllerOperationHandler.java:386)
at org.jboss.as.protocol.mgmt.ManagementResponse$2.handle(ManagementResponse.java:119)
at org.jboss.as.protocol.mgmt.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:59)
... 5 more
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] Created: (JBAS-8657) Provide an installer for AS7
by Thomas Diesler (JIRA)
Provide an installer for AS7
----------------------------
Key: JBAS-8657
URL: https://jira.jboss.org/browse/JBAS-8657
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Installer
Reporter: Thomas Diesler
Assignee: Amit Bhayani
Brian says
I don't see commented out config as a solution. First, at this point, when the file is re-written following an update, comments are lost. That may change, but in general using the file as documentation is fragile. Second, if we added commented out sections for all the various options different subsystems may want to expose, we'll soon have a 1,00 line file full of confusing stuff.
I think we're going to need a mix of things to solve this:
1) Ship a few different canned configs files for the most common profiles, with the user able to select which they want via a command line switch.
2) An "examples" dir in the dist where some less common choices can be highlighted.
3) Most importantly, an installer application where users can easily tell us what subsystems they want in their profile. This is the most important part; #1 is mostly to provide a very easy out-of-the-box experience.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years