[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
15 years, 10 months
[JBoss JIRA] Created: (JBAS-8263) between M3 and M4, a bunch of classes under org.jboss.deployers.spi package were moved from jboss-integration.jar to jboss-deployment.jar and classes from org.jboss.profileservice.spi package were also removed from jboss-integration.jar
by Ian Springer (JIRA)
between M3 and M4, a bunch of classes under org.jboss.deployers.spi package were moved from jboss-integration.jar to jboss-deployment.jar and classes from org.jboss.profileservice.spi package were also removed from jboss-integration.jar
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBAS-8263
URL: https://jira.jboss.org/browse/JBAS-8263
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: ProfileService
Affects Versions: 6.0.0.M4
Reporter: Ian Springer
Assignee: Emanuel Muckenhuber
Here's the classes that are no longer in jboss-integration.jar that used to be in that jar in AS6 M3 and piror:
org/jboss/deployers/spi/management/ContextStateMapper.class
org/jboss/deployers/spi/management/DelegatingComponentDispatcher.class
org/jboss/deployers/spi/management/deploy/DeploymentID.class
org/jboss/deployers/spi/management/deploy/DeploymentManager.class
org/jboss/deployers/spi/management/deploy/DeploymentOptions.class
org/jboss/deployers/spi/management/deploy/DeploymentProgress.class
org/jboss/deployers/spi/management/deploy/DeploymentStatus.class
org/jboss/deployers/spi/management/deploy/DeploymentStatus$CommandType.class
org/jboss/deployers/spi/management/deploy/DeploymentStatus$StateType.class
org/jboss/deployers/spi/management/deploy/DeploymentTarget.class
org/jboss/deployers/spi/management/DeploymentTemplate.class
org/jboss/deployers/spi/management/deploy/ProgressEvent.class
org/jboss/deployers/spi/management/deploy/ProgressListener.class
org/jboss/deployers/spi/management/KnownComponentTypes.class
org/jboss/deployers/spi/management/KnownComponentTypes$ConnectionFactoryTypes.class
org/jboss/deployers/spi/management/KnownComponentTypes$DataSourceTypes.class
org/jboss/deployers/spi/management/KnownComponentTypes$EJB3.class
org/jboss/deployers/spi/management/KnownComponentTypes$EJB.class
org/jboss/deployers/spi/management/KnownComponentTypes$JMSDestination.class
org/jboss/deployers/spi/management/KnownComponentTypes$JPA.class
org/jboss/deployers/spi/management/KnownComponentTypes$MBean.class
org/jboss/deployers/spi/management/KnownComponentTypes$MCBean.class
org/jboss/deployers/spi/management/KnownComponentTypes$Server.class
org/jboss/deployers/spi/management/KnownComponentTypes$Web.class
org/jboss/deployers/spi/management/KnownDeploymentTypes.class
org/jboss/deployers/spi/management/ManagementView.class
org/jboss/deployers/spi/management/NameMatcher.class
org/jboss/deployers/spi/management/RuntimeComponentDispatcher.class
org/jboss/profileservice/spi/DeploymentContentFlags.class
org/jboss/profileservice/spi/DeploymentOption.class
org/jboss/profileservice/spi/DeploymentRepository.class
org/jboss/profileservice/spi/DeploymentRepositoryFactory.class
org/jboss/profileservice/spi/metadata/ProfileDeploymentMetaData.class
org/jboss/profileservice/spi/metadata/ProfileKeyMetaData.class
org/jboss/profileservice/spi/metadata/ProfileMetaData.class
org/jboss/profileservice/spi/metadata/ProfileSourceMetaData.class
org/jboss/profileservice/spi/metadata/SubProfileMetaData.class
org/jboss/profileservice/spi/ModificationInfo.class
org/jboss/profileservice/spi/ModificationInfo$ModifyStatus.class
org/jboss/profileservice/spi/MutableProfile.class
org/jboss/profileservice/spi/NoSuchDeploymentException.class
org/jboss/profileservice/spi/NoSuchProfileException.class
org/jboss/profileservice/spi/Profile.class
org/jboss/profileservice/spi/ProfileDeployment.class
org/jboss/profileservice/spi/ProfileFactory.class
org/jboss/profileservice/spi/ProfileKey.class
org/jboss/profileservice/spi/ProfileRepository.class
org/jboss/profileservice/spi/ProfileService.class
org/jboss/profileservice/spi/types/ControllerStateMetaType.class
The org.jboss.deployers.spi classes appear to have been moved to jboss-deployment.jar, and the org.jboss.profileservice.spi classes are nowhere to be found in any of the jars under the the JBOSS_HOME/client/ dir, but can be found in the JBOSS_HOME/common/lib/jboss-as-profileservice.jar,
This broke the RHQ/JON as5 plugin which uses a bunch of the classes under both of these packages (org/jboss/profileservice/spi/ProfileService and org/jboss/deployers/spi/management/deploy/DeploymentManager, to name a couple of the most important ones). The as5 plugin adds the following set of jars to its classloader in order to find the classes it needs to connect to and use the Profile Service remotely:
private static final List<String> CLIENT_JARS = Arrays.asList(
// NOTE: The jbossall-client.jar aggregates a whole bunch of other jars from the client dir via its
// MANIFEST.MF Class-Path.
"client/jbossall-client.jar",
"client/trove.jar",
"client/javassist.jar",
"common/lib/jboss-security-aspects.jar",
"lib/jboss-managed.jar",
"lib/jboss-metatype.jar",
"lib/jboss-dependency.jar"
);
So as of AS6 M4, this set of jars no longer contains all of the required classes.
We can add client/jboss-deployment.jar and common/lib/jboss-as-profileservice.jar to this set of jars to get RHQ working with M4, but there are some fixes that should be made to JBAS before the final release:
1) jboss-deployment.jar should be added to the manifest classpath of jbossall-client.jar, since it contains mgmt client API classes.
2) the classes in common/lib/jboss-as-profileservice.jar from the org.jboss.profileservice.spi package also need to be made available in some jar under the client dir (perhaps jboss-profileservice-client.jar?), since they are mgmt client API classes. Whatever jar they are moved to should be included in the manifest classpath of jbossall-client.jar.
3) client/trove.jar, client/javassist.jar, common/lib/jboss-security-aspects.jar, lib/jboss-managed.jar, lib/jboss-metatype.jar, lib/jboss-dependency.jar should all be added to jbossall-client.jar's manifest classpath, since they are all required jars for a management client.
--
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
15 years, 10 months