Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

hazelcast-client.jar does not deploy as OSGi bundle in JBoss7 #447

Closed
MrEasy opened this issue Mar 19, 2013 · 1 comment

Comments

Projects
None yet
1 participant
@MrEasy
Copy link
Contributor

commented Mar 19, 2013

hazelcast-client.jar version 2.5 has some Bundle-Classpath-entries in its manifest, which prevents it from being deployed flawlessly as OSGi-bundle in JBoss 7.1.1. See log at end of text.

The issue can be resolved by removing these entries from the manifest:
Class-Path: hazelcast-2.5.jar
Bundle-ClassPath: .,hazelcast-2.5.jar

hazelcast.jar versio 2.5 deploys successfully, but shows a warning about its Classpath entry, also see log blow..
hazelcast-all.jar has similar issues as hazelcast-client.jar, which I refrained from investigating further. (Additionally: "Bundle-Version: 2.52" - really?)

org.jboss.as.server.deployment JB5280 MSC service thread 1-5 Starting deployment of "hazelcast-client-2.5.jar"
org.jboss.as.server.deployment JB5280 MSC service thread 1-5 Starting deployment of "hazelcast-2.5.jar"
org.jboss.msc.service.fail JB8716 MSC service thread 1-3 LOCALHOST ERROR MSC00001: Failed to start service jboss.deployment.unit."hazelcast-client-2.5.jar".STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.unit."hazelcast-client-2.5.jar".STRUCTURE: Failed to process phase STRUCTURE of deployment "hazelcast-client-2.5.jar"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:722)
Caused by: java.lang.IllegalArgumentException: Given parent is not an ancestor of this virtual file
at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:116)
at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)
at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)
at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)
at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)
at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)
at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)
at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)
at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:110)
at org.jboss.as.server.deployment.module.ManifestClassPathProcessor.createAdditionalModule(ManifestClassPathProcessor.java:193)
at org.jboss.as.server.deployment.module.ManifestClassPathProcessor.handlingExistingClassPathEntry(ManifestClassPathProcessor.java:185)
at org.jboss.as.server.deployment.module.ManifestClassPathProcessor.deploy(ManifestClassPathProcessor.java:160)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113)
... 5 more
org.jboss.as.server.deployment JB5280 MSC service thread 1-8 WARN Class Path entry hazelcast-2.5.jar in "/D:/test/BIS6-5-2_2013-03-11/log/run/PE-BIS-1/content/hazelcast-client-2.5.jar" does not point to a valid jar for a Class-Path reference.
org.jboss.osgi.framework.internal.BundleManager JB5280 MSC service thread 1-11 Install bundle: com.hazelcast:2.5.0
org.jboss.as.server JB5280 Controller Boot Thread Deployed "hazelcast-client-2.5.jar"
org.jboss.as.server JB5280 Controller Boot Thread Deployed "hazelcast-2.5.jar"
JBAS014777: Services which failed to start: service jboss.deployment.unit."hazelcast-client-2.5.jar".STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.unit."hazelcast-client-2.5.jar".STRUCTURE: Failed to process phase STRUCTURE of deployment "hazelcast-client-2.5.jar"

@MrEasy

This comment has been minimized.

Copy link
Contributor Author

commented Mar 20, 2013

See #448 for the hazelcast-all.jar manifest.

@mdogan mdogan closed this in 49d67ce Mar 21, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.