[JBoss JIRA] Created: (EJBTHREE-2177) Fix org.jboss.ejb3.test.asynchronous.unit.AsynchronousTestCase failures
by jaikiran pai (JIRA)
Fix org.jboss.ejb3.test.asynchronous.unit.AsynchronousTestCase failures
-----------------------------------------------------------------------
Key: EJBTHREE-2177
URL: https://jira.jboss.org/browse/EJBTHREE-2177
Project: EJB 3.0
Issue Type: Task
Components: testsuite
Reporter: jaikiran pai
Assignee: jaikiran pai
The http://mike.lab.bos.redhat.com:8380/hudson/job/JBoss-AS-6.x-tests-ejb3/71... tests are failing due to:
DEPLOYMENTS IN ERROR:
Deployment "vfs:///jboss/wc/jbossas/projects/ejb3/trunk/testsuite/target/test-lib/asynchronous-test.jar" is in error due to the following reason(s): java.lang.IllegalStateException: jboss.naming:application=asynchronous-test is already installed.
at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:1370) [:2.2.0.Alpha7]
at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:1316) [:2.2.0.Alpha7]
at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:968) [:2.2.0.Alpha7]
at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:957) [:2.2.0.Alpha7]
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:373) [:6.0.0-SNAPSHOT]
at org.jboss.deployment.MainDeployer.redeploy(MainDeployer.java:277) [:6.0.0-SNAPSHOT]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_16]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_16]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_16]
at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_16]
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) [:6.0.0.Beta5]
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) [:6.0.0.Beta5]
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) [:6.0.0.Beta5]
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:271) [:6.0.0.Beta5]
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:670) [:6.0.0.Beta5]
at org.jboss.system.server.jmx.MBeanServerWrapper.invoke(MBeanServerWrapper.java:138) [:6.0.0-SNAPSHOT (Build SVNTag:JBoss_6.0.0-SNAPSHOT date: 20100923)]
at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1426) [:1.6.0_16]
at javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:72) [:1.6.0_16]
at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1264) [:1.6.0_16]
at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1359) [:1.6.0_16]
at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:788) [:1.6.0_16]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_16]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_16]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_16]
at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_16]
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305) [:1.6.0_16]
at sun.rmi.transport.Transport$1.run(Transport.java:159) [:1.6.0_16]
at java.security.AccessController.doPrivileged(Native Method) [:1.6.0_16]
at sun.rmi.transport.Transport.serviceCall(Transport.java:155) [:1.6.0_16]
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535) [:1.6.0_16]
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790) [:1.6.0_16]
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649) [:1.6.0_16]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_16]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_16]
at java.lang.Thread.run(Thread.java:619) [:1.6.0_16]
This is because the testcase deploys asynchronous-test.sar and asynchronous-test.jar, which results in the JavaEE naming conflicts.
--
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
13 years, 9 months
[JBoss JIRA] Created: (JBMETA-224) Incompatible types compilation errors when building with OpenJDK Runtime Environment (IcedTea6 1.6)
by David Walluck (JIRA)
Incompatible types compilation errors when building with OpenJDK Runtime Environment (IcedTea6 1.6)
---------------------------------------------------------------------------------------------------
Key: JBMETA-224
URL: https://jira.jboss.org/jira/browse/JBMETA-224
Project: JBoss Metadata
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 1.0.1.GA
Reporter: David Walluck
Assignee: Alexey Loubyansky
Fix For: 1.0.2.GA
Incompatible types errors when building with OpenJDK Runtime Environment (IcedTea6 1.6). Does not occur with Java(TM) SE Runtime Environment (build 1.6.0_15-b03).
Build log follows:
[INFO] [compiler:compile]
[INFO] Compiling 664 source files to /home/david/dist/jboss-metadata/JPP-6/jboss-metadata-1.0.1/target/classes
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Compilation failure
/home/david/dist/jboss-metadata/JPP-6/jboss-metadata-1.0.1/src/main/java/org/jboss/metadata/ejb/jboss/JBossAssemblyDescriptorMetaData.java:[434,71] incompatible types; inferred type argument(s) java.lang.Object do not conform to bounds of type variable(s) T
found : <T>org.jboss.metadata.javaee.spec.SecurityRolesMetaData
required: org.jboss.metadata.javaee.spec.SecurityRolesMetaData
/home/david/dist/jboss-metadata/JPP-6/jboss-metadata-1.0.1/src/main/java/org/jboss/metadata/ejb/jboss/JBossAssemblyDescriptorMetaData.java:[447,77] incompatible types; inferred type argument(s) java.lang.Object do not conform to bounds of type variable(s) T
found : <T>org.jboss.metadata.javaee.spec.MessageDestinationsMetaData
required: org.jboss.metadata.javaee.spec.MessageDestinationsMetaData
/home/david/dist/jboss-metadata/JPP-6/jboss-metadata-1.0.1/src/main/java/org/jboss/metadata/javaee/spec/MessageDestinationsMetaData.java:[61,37] incompatible types; inferred type argument(s) java.lang.Object do not conform to bounds of type variable(s) T
found : <T>org.jboss.metadata.javaee.spec.MessageDestinationsMetaData
required: org.jboss.metadata.javaee.spec.MessageDestinationsMetaData
/home/david/dist/jboss-metadata/JPP-6/jboss-metadata-1.0.1/src/main/java/org/jboss/metadata/javaee/spec/EJBLocalReferencesMetaData.java:[58,37] incompatible types; inferred type argument(s) java.lang.Object do not conform to bounds of type variable(s) T
found : <T>org.jboss.metadata.javaee.spec.EJBLocalReferencesMetaData
required: org.jboss.metadata.javaee.spec.EJBLocalReferencesMetaData
/home/david/dist/jboss-metadata/JPP-6/jboss-metadata-1.0.1/src/main/java/org/jboss/metadata/javaee/spec/EJBReferencesMetaData.java:[58,37] incompatible types; inferred type argument(s) java.lang.Object do not conform to bounds of type variable(s) T
found : <T>org.jboss.metadata.javaee.spec.EJBReferencesMetaData
required: org.jboss.metadata.javaee.spec.EJBReferencesMetaData
/home/david/dist/jboss-metadata/JPP-6/jboss-metadata-1.0.1/src/main/java/org/jboss/metadata/javaee/spec/MessageDestinationReferencesMetaData.java:[59,37] incompatible types; inferred type argument(s) java.lang.Object do not conform to bounds of type variable(s) T
found : <T>org.jboss.metadata.javaee.spec.MessageDestinationReferencesMetaData
required: org.jboss.metadata.javaee.spec.MessageDestinationReferencesMetaData
/home/david/dist/jboss-metadata/JPP-6/jboss-metadata-1.0.1/src/main/java/org/jboss/metadata/javaee/spec/PersistenceContextReferencesMetaData.java:[49,37] incompatible types; inferred type argument(s) java.lang.Object do not conform to bounds of type variable(s) T
found : <T>org.jboss.metadata.javaee.spec.PersistenceContextReferencesMetaData
required: org.jboss.metadata.javaee.spec.PersistenceContextReferencesMetaData
/home/david/dist/jboss-metadata/JPP-6/jboss-metadata-1.0.1/src/main/java/org/jboss/metadata/javaee/spec/ResourceEnvironmentReferencesMetaData.java:[56,37] incompatible types; inferred type argument(s) java.lang.Object do not conform to bounds of type variable(s) T
found : <T>org.jboss.metadata.javaee.spec.ResourceEnvironmentReferencesMetaData
required: org.jboss.metadata.javaee.spec.ResourceEnvironmentReferencesMetaData
/home/david/dist/jboss-metadata/JPP-6/jboss-metadata-1.0.1/src/main/java/org/jboss/metadata/javaee/spec/ResourceReferencesMetaData.java:[56,37] incompatible types; inferred type argument(s) java.lang.Object do not conform to bounds of type variable(s) T
found : <T>org.jboss.metadata.javaee.spec.ResourceReferencesMetaData
required: org.jboss.metadata.javaee.spec.ResourceReferencesMetaData
/home/david/dist/jboss-metadata/JPP-6/jboss-metadata-1.0.1/src/main/java/org/jboss/metadata/javaee/spec/ServiceReferencesMetaData.java:[64,37] incompatible types; inferred type argument(s) java.lang.Object do not conform to bounds of type variable(s) T
found : <T>org.jboss.metadata.javaee.spec.ServiceReferencesMetaData
required: org.jboss.metadata.javaee.spec.ServiceReferencesMetaData
/home/david/dist/jboss-metadata/JPP-6/jboss-metadata-1.0.1/src/main/java/org/jboss/metadata/javaee/spec/AnnotatedEJBReferencesMetaData.java:[59,37] incompatible types; inferred type argument(s) java.lang.Object do not conform to bounds of type variable(s) T
found : <T>org.jboss.metadata.javaee.spec.AnnotatedEJBReferencesMetaData
required: org.jboss.metadata.javaee.spec.AnnotatedEJBReferencesMetaData
/home/david/dist/jboss-metadata/JPP-6/jboss-metadata-1.0.1/src/main/java/org/jboss/metadata/javaee/support/JavaEEMetaDataUtil.java:[48,18] incompatible types; inferred type argument(s) java.lang.Object do not conform to bounds of type variable(s) T
found : <T>M
required: M
/home/david/dist/jboss-metadata/JPP-6/jboss-metadata-1.0.1/src/main/java/org/jboss/metadata/javaee/support/JavaEEMetaDataUtil.java:[145,26] incompatible types; inferred type argument(s) org.jboss.metadata.javaee.support.MappableMetaData,java.lang.Object do not conform to bounds of type variable(s) C,T
found : <C,T>M
required: M
/home/david/dist/jboss-metadata/JPP-6/jboss-metadata-1.0.1/src/main/java/org/jboss/metadata/javaee/support/JavaEEMetaDataUtil.java:[154,26] incompatible types; inferred type argument(s) org.jboss.metadata.javaee.support.MappableMetaData,java.lang.Object do not conform to bounds of type variable(s) C,T
found : <C,T>M
required: M
--
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, 9 months
[JBoss JIRA] Created: (JBMETA-299) Add support for <addressing> <respect-binding> & <mtom-threshold> subelements of <port-component-ref> element
by Richard Opalka (JIRA)
Add support for <addressing> <respect-binding> & <mtom-threshold> subelements of <port-component-ref> element
--------------------------------------------------------------------------------------------------------------
Key: JBMETA-299
URL: https://jira.jboss.org/browse/JBMETA-299
Project: JBoss Metadata
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: common
Reporter: Richard Opalka
Assignee: Richard Opalka
Fix For: jboss-metadata-common-2.0.0-alpha-17
<xsd:complexType name="port-component-refType">
<xsd:annotation>
<xsd:documentation>
The port-component-ref element declares a client dependency
on the container for resolving a Service Endpoint Interface
to a WSDL port. It optionally associates the Service Endpoint
Interface with a particular port-component. This is only used
by the container for a Service.getPort(Class) method call.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="service-endpoint-interface"
type="javaee:fully-qualified-classType">
<xsd:annotation>
<xsd:documentation>
The service-endpoint-interface element defines a fully qualified
Java class that represents the Service Endpoint Interface of a
WSDL port.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="enable-mtom"
type="javaee:true-falseType"
minOccurs="0"
maxOccurs="1">
<xsd:annotation>
<xsd:documentation>
Used to enable or disable SOAP MTOM/XOP mechanism on the client
side for a port-component.
Not to be specified for JAX-RPC runtime
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="mtom-threshold"
type="javaee:xsdNonNegativeIntegerType"
minOccurs="0"
maxOccurs="1">
<xsd:annotation>
<xsd:documentation>
When MTOM is enabled, binary data above this size in bytes
should be XOP encoded or sent as attachment. Default value is 0.
Not to be specified for JAX-RPC runtime
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="addressing"
type="javaee:addressingType"
minOccurs="0"
maxOccurs="1">
<xsd:annotation>
<xsd:documentation>
This specifies the WS-Addressing requirements for a JAX-WS
web service. It corresponds to javax.xml.ws.soap.Addressing
annotation or its feature javax.xml.ws.soap.AddressingFeature.
See the addressingType for more information.
Not to be specified for JAX-RPC runtime
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="respect-binding"
type="javaee:respect-bindingType"
minOccurs="0"
maxOccurs="1">
<xsd:annotation>
<xsd:documentation>
Corresponds to the javax.xml.ws.RespectBinding annotation
or its corresponding javax.xml.ws.RespectBindingFeature web
service feature. This is used to control whether a JAX-WS
implementation must respect/honor the contents of the
wsdl:binding in the WSDL that is associated with the service.
Not to be specified for JAX-RPC runtime
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="port-component-link"
type="javaee:string"
minOccurs="0"
maxOccurs="1">
<xsd:annotation>
<xsd:documentation>
The port-component-link element links a port-component-ref
to a specific port-component required to be made available
by a service reference.
The value of a port-component-link must be the
port-component-name of a port-component in the same module
or another module in the same application unit. The syntax
for specification follows the syntax defined for ejb-link
in the EJB 2.0 specification.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id"
type="xsd:ID"/>
</xsd:complexType>
--
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
13 years, 9 months
[JBoss JIRA] Created: (JBAS-7997) JBoss AS 6.0.0.M3 fails to boot when not on network
by jaikiran pai (JIRA)
JBoss AS 6.0.0.M3 fails to boot when not on network
---------------------------------------------------
Key: JBAS-7997
URL: https://jira.jboss.org/jira/browse/JBAS-7997
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 6.0.0.M3
Environment: JBoss AS 6.0.0.M3, Sun Java 1.6, RHEL OS and not connected to any network
Reporter: jaikiran pai
When the system is not connected to a network, JBoss AS 6.0.0.M3 fails with the following boot error related to HornetQ:
13:00:47,688 ERROR [AbstractKernelController] Error installing to Start: name=JMSServerManager state=Create: java.net.SocketException: No such device
at java.net.PlainDatagramSocketImpl.join(Native Method) [:1.6.0_16]
at java.net.PlainDatagramSocketImpl.join(PlainDatagramSocketImpl.java:172) [:1.6.0_16]
at java.net.MulticastSocket.joinGroup(MulticastSocket.java:276) [:1.6.0_16]
at org.hornetq.core.cluster.impl.DiscoveryGroupImpl.start(DiscoveryGroupImpl.java:124) [:6.0.0.20100429-M3]
at org.hornetq.core.server.cluster.impl.ClusterManagerImpl.deployDiscoveryGroup(ClusterManagerImpl.java:357) [:6.0.0.20100429-M3]
at org.hornetq.core.server.cluster.impl.ClusterManagerImpl.start(ClusterManagerImpl.java:142) [:6.0.0.20100429-M3]
at org.hornetq.core.server.impl.HornetQServerImpl.initialisePart2(HornetQServerImpl.java:1090) [:6.0.0.20100429-M3]
at org.hornetq.core.server.impl.HornetQServerImpl.start(HornetQServerImpl.java:310) [:6.0.0.20100429-M3]
at org.hornetq.jms.server.impl.JMSServerManagerImpl.start(JMSServerManagerImpl.java:233) [:6.0.0.20100429-M3]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_16]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_16]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_16]
at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_16]
at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:59) [jboss-reflect.jar:2.2.0.Alpha4]
at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:168) [jboss-reflect.jar:2.2.0.Alpha4]
at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66) [jboss-reflect.jar:2.2.0.Alpha4]
at org.jboss.kernel.plugins.dependency.KernelControllerContextAction$JoinpointDispatchWrapper.execute(KernelControllerContextAction.java:257) [jboss-kernel.jar:2.2.0.Alpha9]
at org.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(ExecutionWrapper.java:47) [jboss-kernel.jar:2.2.0.Alpha9]
at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchExecutionWrapper(KernelControllerContextAction.java:125) [jboss-kernel.jar:2.2.0.Alpha9]
at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:72) [jboss-kernel.jar:2.2.0.Alpha9]
at org.jboss.kernel.plugins.dependency.LifecycleAction.installActionInternal(LifecycleAction.java:202) [jboss-kernel.jar:2.2.0.Alpha9]
at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:54) [jboss-kernel.jar:2.2.0.Alpha9]
at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:42) [jboss-kernel.jar:2.2.0.Alpha9]
at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62) [jboss-dependency.jar:2.2.0.Alpha9]
at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71) [jboss-dependency.jar:2.2.0.Alpha9]
at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) [jboss-dependency.jar:2.2.0.Alpha9]
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:377) [jboss-dependency.jar:2.2.0.Alpha9]
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2042) [jboss-dependency.jar:2.2.0.Alpha9]
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1081) [jboss-dependency.jar:2.2.0.Alpha9]
at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1320) [jboss-dependency.jar:2.2.0.Alpha9]
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1244) [jboss-dependency.jar:2.2.0.Alpha9]
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1137) [jboss-dependency.jar:2.2.0.Alpha9]
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:892) [jboss-dependency.jar:2.2.0.Alpha9]
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:639) [jboss-dependency.jar:2.2.0.Alpha9]
at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:180) [:2.2.0.Alpha4]
at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:58) [:2.2.0.Alpha4]
at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62) [:2.2.0.Alpha4]
at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:55) [:2.2.0.Alpha4]
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179) [:2.2.0.Alpha4]
at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1857) [:2.2.0.Alpha4]
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1575) [:2.2.0.Alpha4]
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1596) [:2.2.0.Alpha4]
at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1516) [:2.2.0.Alpha4]
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:377) [jboss-dependency.jar:2.2.0.Alpha9]
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2042) [jboss-dependency.jar:2.2.0.Alpha9]
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1081) [jboss-dependency.jar:2.2.0.Alpha9]
at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1320) [jboss-dependency.jar:2.2.0.Alpha9]
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1244) [jboss-dependency.jar:2.2.0.Alpha9]
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1137) [jboss-dependency.jar:2.2.0.Alpha9]
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:937) [jboss-dependency.jar:2.2.0.Alpha9]
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:652) [jboss-dependency.jar:2.2.0.Alpha9]
at org.jboss.deployers.plugins.deployers.DeployersImpl.change(DeployersImpl.java:2008) [:2.2.0.Alpha4]
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:1101) [:2.2.0.Alpha4]
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:679) [:2.2.0.Alpha4]
at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117) [:6.0.0.20100429-M3]
at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70) [:6.0.0.20100429-M3]
at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53) [:6.0.0.20100429-M3]
at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:403) [:6.0.0.20100429-M3]
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:377) [jboss-dependency.jar:2.2.0.Alpha9]
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2042) [jboss-dependency.jar:2.2.0.Alpha9]
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1081) [jboss-dependency.jar:2.2.0.Alpha9]
at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1320) [jboss-dependency.jar:2.2.0.Alpha9]
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1244) [jboss-dependency.jar:2.2.0.Alpha9]
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1137) [jboss-dependency.jar:2.2.0.Alpha9]
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:892) [jboss-dependency.jar:2.2.0.Alpha9]
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:639) [jboss-dependency.jar:2.2.0.Alpha9]
at org.jboss.system.server.profileservice.repository.AbstractProfileService.registerProfile(AbstractProfileService.java:308) [:6.0.0.20100429-M3]
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:256) [:6.0.0.20100429-M3]
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:97) [:6.0.0.20100429-M3]
at org.jboss.bootstrap.impl.base.server.AbstractServer.startBootstraps(AbstractServer.java:827) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-5]
at org.jboss.bootstrap.impl.base.server.AbstractServer$StartServerTask.run(AbstractServer.java:417) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-5]
at java.lang.Thread.run(Thread.java:619) [:1.6.0_16]
13:00:47,767 INFO [WebService] Using RMI server codebase: http://localhost.localdomain:8083/
13:00:48,530 INFO [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /NotBackedUp/jpai/jboss-6.0.0.M3/bin/native/lib
13:00:48,729 INFO [TomcatDeployment] deploy, ctxPath=/invoker
13:00:49,318 INFO [RARDeployment] Required license terms exist, view vfs:/NotBackedUp/jpai/jboss-6.0.0.M3/server/default/deploy/jboss-local-jdbc.rar/META-INF/ra.xml
13:00:49,333 INFO [RARDeployment] Required license terms exist, view vfs:/NotBackedUp/jpai/jboss-6.0.0.M3/server/default/deploy/jboss-xa-jdbc.rar/META-INF/ra.xml
13:00:49,356 INFO [RARDeployment] Required license terms exist, view vfs:/NotBackedUp/jpai/jboss-6.0.0.M3/server/default/deploy/jms-ra.rar/META-INF/ra.xml
13:00:49,385 INFO [HornetQResourceAdapter] HornetQ resource adaptor started
13:00:49,391 INFO [RARDeployment] Required license terms exist, view vfs:/NotBackedUp/jpai/jboss-6.0.0.M3/server/default/deploy/mail-ra.rar/META-INF/ra.xml
13:00:49,402 INFO [RARDeployment] Required license terms exist, view vfs:/NotBackedUp/jpai/jboss-6.0.0.M3/server/default/deploy/quartz-ra.rar/META-INF/ra.xml
13:00:49,467 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: Thread-2
13:00:49,498 INFO [SchedulerSignalerImpl] Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl
13:00:49,499 INFO [QuartzScheduler] Quartz Scheduler v.1.7.3 created.
13:00:49,501 INFO [RAMJobStore] RAMJobStore initialized.
13:00:49,501 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
13:00:49,501 INFO [StdSchedulerFactory] Quartz scheduler version: 1.7.3
13:00:49,505 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
13:00:50,181 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
13:00:50,458 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
13:00:50,491 INFO [xnio] XNIO Version 2.1.0.CR2
13:00:50,494 INFO [nio] XNIO NIO Implementation Version 2.1.0.CR2
13:00:50,893 INFO [remoting] JBoss Remoting version 3.1.0.Beta2
13:00:50,974 INFO [TomcatDeployment] deploy, ctxPath=/
13:00:51,045 INFO [service] Removing bootstrap log handlers
13:00:51,120 INFO [org.jboss.system.server.profileservice.ProfileServiceBootstrap] Loading profile: ProfileKey@181f5b[domain=default, server=default, name=default]
13:00:51,123 ERROR [org.jboss.system.server.profileservice.ProfileServiceBootstrap] Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
DEPLOYMENTS MISSING DEPENDENCIES:
Deployment "JMSConnectionFactoryManageMO" is missing the following dependencies:
Dependency "<UNKNOWN JMSConnectionFactoryManageMO>" (should be in state "Installed", but is actually in state "** UNRESOLVED Demands 'JMSServerManager' **")
Deployment "JMSQueueManageMO" is missing the following dependencies:
Dependency "<UNKNOWN JMSQueueManageMO>" (should be in state "Installed", but is actually in state "** UNRESOLVED Demands 'JMSServerManager' **")
Deployment "JMSServerMO" is missing the following dependencies:
Dependency "<UNKNOWN JMSServerMO>" (should be in state "Installed", but is actually in state "** UNRESOLVED Demands 'JMSServerManager' **")
Deployment "JMSTopicManageMO" is missing the following dependencies:
Dependency "<UNKNOWN JMSTopicManageMO>" (should be in state "Installed", but is actually in state "** UNRESOLVED Demands 'JMSServerManager' **")
Deployment "org.hornetq:module=JMS,name="InVMConnectionFactory",type=ConnectionFactory" is missing the following dependencies:
Dependency "JMSServerManager" (should be in state "Installed", but is actually in state "**ERROR**")
Deployment "org.hornetq:module=JMS,name="NettyConnectionFactory",type=ConnectionFactory" is missing the following dependencies:
Dependency "JMSServerManager" (should be in state "Installed", but is actually in state "**ERROR**")
Deployment "org.hornetq:module=JMS,name="NettyThroughputConnectionFactory",type=ConnectionFactory" is missing the following dependencies:
Dependency "JMSServerManager" (should be in state "Installed", but is actually in state "**ERROR**")
Deployment "org.hornetq:module=JMS,type=Queue,name="DLQ"" is missing the following dependencies:
Dependency "JMSServerManager" (should be in state "Installed", but is actually in state "**ERROR**")
Deployment "org.hornetq:module=JMS,type=Queue,name="ExpiryQueue"" is missing the following dependencies:
Dependency "JMSServerManager" (should be in state "Installed", but is actually in state "**ERROR**")
DEPLOYMENTS IN ERROR:
Deployment "JMSServerManager" is in error due to the following reason(s): java.net.SocketException: No such device, **ERROR**
Deployment "<UNKNOWN JMSServerMO>" is in error due to the following reason(s): ** UNRESOLVED Demands 'JMSServerManager' **
Deployment "<UNKNOWN JMSConnectionFactoryManageMO>" is in error due to the following reason(s): ** UNRESOLVED Demands 'JMSServerManager' **
Deployment "<UNKNOWN JMSTopicManageMO>" is in error due to the following reason(s): ** UNRESOLVED Demands 'JMSServerManager' **
Deployment "<UNKNOWN JMSQueueManageMO>" is in error due to the following reason(s): ** UNRESOLVED Demands 'JMSServerManager' **
13:00:51,144 INFO [org.apache.coyote.http11.Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080
13:00:51,151 INFO [org.apache.coyote.ajp.AjpProtocol] Starting Coyote AJP/1.3 on ajp-0.0.0.0-8009
13:00:51,152 INFO [org.jboss.bootstrap.impl.base.server.AbstractServer] JBossAS [6.0.0.20100429-M3 "Neo"] Started in 29s:478ms
Please see the referenced forum thread for the details
--
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, 9 months