[JBoss JIRA] (JBOSGI-745) Support OSGi Bundle Native Libraries for Windows 8/2008 Server platforms
by Ed Roberts (JIRA)
Ed Roberts created JBOSGI-745:
---------------------------------
Summary: Support OSGi Bundle Native Libraries for Windows 8/2008 Server platforms
Key: JBOSGI-745
URL: https://issues.jboss.org/browse/JBOSGI-745
Project: JBoss OSGi
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: framework
Affects Versions: JBossOSGi 2.1.1
Environment: Windows 8, JDK 7.0_13
Reporter: Ed Roberts
Assignee: Thomas Diesler
I need to refactor the current jdbc driver modules as OSGi bundles. One particular bundle which contains supporting native libraries caused a startup issue in JBoss 7.2.0.Final. However, the only lead I had was the warning message "JBAS011910: Cannot resolve requirements: []", which appeared several times.
After enabling debug for the framework, I could see that a jdbc driver bundle containing supporting native libraries was the cause.
{code}
2013-08-30 10:15:07,518 DEBUG [org.jboss.osgi.framework](ClassLoader Thread) Cannot resolve bundle: x:1.0.0.SNAPSHOT: org.osgi.service.resolver.ResolutionException: org.osgi.framework.BundleException: JBOSGI011260: No native code clause selected for: [lib/windows/32/sqljdbc_auth.dll[attr={osname=[[WindowsVista, Windows2003, Windows7, WindowsXP, Windows2000, WindowsNT]], processor=[x86]},dirs={}], lib/windows/32/sqljdbc_xa.dll[attr={osname=[[WindowsVista, Windows2003, Windows7, WindowsXP, Windows2000, WindowsNT]], processor=[x86]},dirs={}], lib/windows/64/sqljdbc_auth.dll[attr={osname=[[WindowsVista, Windows2003, Windows7, WindowsXP, Windows2000, WindowsNT]], processor=[x86-64]},dirs={}], lib/windows/64/sqljdbc_xa.dll[attr={osname=[[WindowsVista, Windows2003, Windows7, WindowsXP, Windows2000, WindowsNT]], processor=[x86-64]},dirs={}]]
at org.jboss.osgi.framework.internal.ResolverImpl.applyResolverResults(ResolverImpl.java:245)
at org.jboss.osgi.framework.internal.ResolverImpl.resolveAndApply(ResolverImpl.java:138)
at org.jboss.osgi.framework.spi.BundleLifecyclePlugin$BundleLifecycleImpl.resolve(BundleLifecyclePlugin.java:97)
at org.jboss.as.osgi.service.BundleLifecycleIntegration$BundleLifecycleImpl.resolve(BundleLifecycleIntegration.java:180)
at org.jboss.osgi.framework.internal.AbstractBundleState.ensureResolved(AbstractBundleState.java:624)
at org.jboss.osgi.framework.internal.FallbackLoader.findInUnresolvedRevisions(FallbackLoader.java:285)
at org.jboss.osgi.framework.internal.FallbackLoader.findRevisionDynamically(FallbackLoader.java:192)
at org.jboss.osgi.framework.internal.FallbackLoader.loadClassLocal(FallbackLoader.java:112)
at org.jboss.modules.Module.loadModuleClass(Module.java:526)
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:182)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456)
at org.jboss.modules.ConcurrentClassLoader.access$400(ConcurrentClassLoader.java:52)
at org.jboss.modules.ConcurrentClassLoader$LoaderThread.run(ConcurrentClassLoader.java:627)
Caused by: org.osgi.framework.BundleException: JBOSGI011260: No native code clause selected for: [lib/windows/32/sqljdbc_auth.dll[attr={osname=[[WindowsVista, Windows2003, Windows7, WindowsXP, Windows2000, WindowsNT]], processor=[x86]},dirs={}], lib/windows/32/sqljdbc_xa.dll[attr={osname=[[WindowsVista, Windows2003, Windows7, WindowsXP, Windows2000, WindowsNT]], processor=[x86]},dirs={}], lib/windows/64/sqljdbc_auth.dll[attr={osname=[[WindowsVista, Windows2003, Windows7, WindowsXP, Windows2000, WindowsNT]], processor=[x86-64]},dirs={}], lib/windows/64/sqljdbc_xa.dll[attr={osname=[[WindowsVista, Windows2003, Windows7, WindowsXP, Windows2000, WindowsNT]], processor=[x86-64]},dirs={}]]
at org.jboss.osgi.framework.internal.NativeCodeImpl.resolveNativeCode(NativeCodeImpl.java:165)
at org.jboss.osgi.framework.internal.ResolverImpl.resolveNativeCodeLibraries(ResolverImpl.java:296)
at org.jboss.osgi.framework.internal.ResolverImpl.applyResolverResults(ResolverImpl.java:243)
... 13 more
{code}
This is due to the NativeCodeImpl which does not yet include support for the two operating system mentioned above.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (JBOSGI-744) JBAS011910 Cannot resolve requirements: [XPackageRequirement[atts={osgi.wiring.package=org.hibernate.criterion}
by Steve Ebersole (JIRA)
[ https://issues.jboss.org/browse/JBOSGI-744?page=com.atlassian.jira.plugin... ]
Steve Ebersole updated JBOSGI-744:
----------------------------------
Assignee: Thomas Diesler
> JBAS011910 Cannot resolve requirements: [XPackageRequirement[atts={osgi.wiring.package=org.hibernate.criterion}
> ---------------------------------------------------------------------------------------------------------------
>
> Key: JBOSGI-744
> URL: https://issues.jboss.org/browse/JBOSGI-744
> Project: JBoss OSGi
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Darryl Miles
> Assignee: Thomas Diesler
>
> EAP 6.1 with upgraded org.hibernate:main jars to 4.2.0.Final (to fix classloading issue HHH-8015 which I did observe).
> JPA has META-INF/jboss-deployment-structure.xml which has entry (amongst other things):
> <module name="org.hibernate" />
> <module name="org.hibernate.validator" />
> JPA has OSGi meta-data including OSGi-JPA:
> Meta-Persistence: META-INF/persistence.xml
> 23:00:16,860 INFO [org.jboss.osgi.framework] (MSC service thread 1-15) JBOSGI011005: Bundle uninstalled: com.domain.jpa:0.0.1.SNAPSHOT
> 23:00:16,862 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015877: Stopped deployment com.domain.jpa-0.0.1-SNAPSHOT.jar (runtime-name: com.domain.jpa-0.0.1-SNAPSHOT.jar) in 4ms
> 23:00:16,863 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015876: Starting deployment of "com.domain.jpa-0.0.1-SNAPSHOT.jar" (runtime-name: "com.domain.jpa-0.0.1-SNAPSHOT.jar")
> 23:00:16,876 INFO [org.jboss.as.jpa] (MSC service thread 1-15) JBAS011401: Read persistence.xml for com.domain.jpa
> 23:00:16,880 INFO [org.jboss.osgi.framework] (MSC service thread 1-9) JBOSGI011001: Bundle installed: com.domain.jpa:0.0.1.SNAPSHOT
> 23:00:16,884 WARN [org.jboss.as.osgi] (MSC service thread 1-14) JBAS011910: Cannot resolve requirements: [XPackageRequirement[atts={osgi.wiring.package=org.hibernate.criterion},[com.domain.jpa:0.0.1.SNAPSHOT]]]
> 23:00:16,884 INFO [org.jboss.as.server.deployment] (MSC service thread 1-14) JBAS015970: Defer FIRST_MODULE_USE for com.domain.jpa-0.0.1-SNAPSHOT.jar making it NEVER
> 23:00:16,908 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS018565: Replaced deployment "com.domain.jpa-0.0.1-SNAPSHOT.jar" with deployment "com.domain.jpa-0.0.1-SNAPSHOT.jar"
> I would expect the OSGi subsystem to have been able to find the import package org.hibernate.criterion
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (JBOSGI-744) JBAS011910 Cannot resolve requirements: [XPackageRequirement[atts={osgi.wiring.package=org.hibernate.criterion}
by Steve Ebersole (JIRA)
[ https://issues.jboss.org/browse/JBOSGI-744?page=com.atlassian.jira.plugin... ]
Steve Ebersole moved HIBERNATE-141 to JBOSGI-744:
-------------------------------------------------
Project: JBoss OSGi (was: Hibernate Integration)
Key: JBOSGI-744 (was: HIBERNATE-141)
Issue Type: Bug (was: Enhancement)
Security: Public
> JBAS011910 Cannot resolve requirements: [XPackageRequirement[atts={osgi.wiring.package=org.hibernate.criterion}
> ---------------------------------------------------------------------------------------------------------------
>
> Key: JBOSGI-744
> URL: https://issues.jboss.org/browse/JBOSGI-744
> Project: JBoss OSGi
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Darryl Miles
>
> EAP 6.1 with upgraded org.hibernate:main jars to 4.2.0.Final (to fix classloading issue HHH-8015 which I did observe).
> JPA has META-INF/jboss-deployment-structure.xml which has entry (amongst other things):
> <module name="org.hibernate" />
> <module name="org.hibernate.validator" />
> JPA has OSGi meta-data including OSGi-JPA:
> Meta-Persistence: META-INF/persistence.xml
> 23:00:16,860 INFO [org.jboss.osgi.framework] (MSC service thread 1-15) JBOSGI011005: Bundle uninstalled: com.domain.jpa:0.0.1.SNAPSHOT
> 23:00:16,862 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015877: Stopped deployment com.domain.jpa-0.0.1-SNAPSHOT.jar (runtime-name: com.domain.jpa-0.0.1-SNAPSHOT.jar) in 4ms
> 23:00:16,863 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015876: Starting deployment of "com.domain.jpa-0.0.1-SNAPSHOT.jar" (runtime-name: "com.domain.jpa-0.0.1-SNAPSHOT.jar")
> 23:00:16,876 INFO [org.jboss.as.jpa] (MSC service thread 1-15) JBAS011401: Read persistence.xml for com.domain.jpa
> 23:00:16,880 INFO [org.jboss.osgi.framework] (MSC service thread 1-9) JBOSGI011001: Bundle installed: com.domain.jpa:0.0.1.SNAPSHOT
> 23:00:16,884 WARN [org.jboss.as.osgi] (MSC service thread 1-14) JBAS011910: Cannot resolve requirements: [XPackageRequirement[atts={osgi.wiring.package=org.hibernate.criterion},[com.domain.jpa:0.0.1.SNAPSHOT]]]
> 23:00:16,884 INFO [org.jboss.as.server.deployment] (MSC service thread 1-14) JBAS015970: Defer FIRST_MODULE_USE for com.domain.jpa-0.0.1-SNAPSHOT.jar making it NEVER
> 23:00:16,908 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS018565: Replaced deployment "com.domain.jpa-0.0.1-SNAPSHOT.jar" with deployment "com.domain.jpa-0.0.1-SNAPSHOT.jar"
> I would expect the OSGi subsystem to have been able to find the import package org.hibernate.criterion
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (JBOSGI-743) Cannot restart webapp bundle
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/JBOSGI-743?page=com.atlassian.jira.plugin... ]
Thomas Diesler updated JBOSGI-743:
----------------------------------
Fix Version/s: (was: JBossOSGi 2.1.1)
> Cannot restart webapp bundle
> ----------------------------
>
> Key: JBOSGI-743
> URL: https://issues.jboss.org/browse/JBOSGI-743
> Project: JBoss OSGi
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: webapp
> Reporter: Thomas Diesler
>
> {code}
> testBundleWithWebContextPath(org.jboss.test.osgi.example.webapp.WebAppTestCase) Time elapsed: 0.437 sec <<< ERROR!
> java.lang.IllegalStateException: JBAS017345: Cannot activate context: service jboss.undertow.deployment.default-host./bundle-d
> at org.jboss.msc.inject.RetainingInjector.inject(RetainingInjector.java:50)
> at org.wildfly.extension.undertow.deployment.UndertowJSRWebSocketDeploymentProcessor$1.ready(UndertowJSRWebSocketDeploymentProcessor.java:240)
> at io.undertow.websockets.jsr.WebSocketDeploymentInfo.containerReady(WebSocketDeploymentInfo.java:64)
> at io.undertow.websockets.jsr.Bootstrap.handleDeployment(Bootstrap.java:50)
> at io.undertow.servlet.core.DeploymentManagerImpl.handleExtensions(DeploymentManagerImpl.java:209)
> at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:133)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:83)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$ContextActivatorImpl.startContext(UndertowDeploymentService.java:154)
> at org.jboss.as.osgi.web.WebContextLifecycleInterceptor.invoke(WebContextLifecycleInterceptor.java:96)
> at org.jboss.osgi.deployment.interceptor.AbstractLifecycleInterceptorService.handleStateChange(AbstractLifecycleInterceptorService.java:264)
> at org.jboss.osgi.framework.internal.AbstractBundleState.changeState(AbstractBundleState.java:252)
> at org.jboss.osgi.framework.internal.AbstractBundleState.changeState(AbstractBundleState.java:241)
> at org.jboss.osgi.framework.internal.UserBundleState.startInternalNow(UserBundleState.java:635)
> at org.jboss.osgi.framework.internal.UserBundleState.startInternal(UserBundleState.java:524)
> at org.jboss.osgi.framework.internal.BundleManagerPlugin.startBundle(BundleManagerPlugin.java:572)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (JBOSGI-699) Initial OSGi / CDI Integration
by Ampie Barnard (JIRA)
[ https://issues.jboss.org/browse/JBOSGI-699?page=com.atlassian.jira.plugin... ]
Ampie Barnard commented on JBOSGI-699:
--------------------------------------
Thomas, I see you are awaiting volunteers. Depending on the nature of the beast, I may be able offer some of my (albeit limited) skills. How were you thinking of implementing this requirement? What is currently the main obstacle?
My understanding was, and I may be wrong, that the Weld OSGi OSGi/CDI integration was going to be used. I have tested the weld-osgi-2.x branch on JBosgi 2 and Wildfly 8 Alpha 3, but I could not get Weld OSGi and the Weld subsystem to run side by side. I described my attempt in more detail on the Weld forum at [https://community.jboss.org/thread/231047]. What I don't understand though, is what JBoss OSGi can do to resolve this conflict. Is it merely a packaging issue, packaging Weld OSGi as modules and enabling them as a cability? Or does it involve re-implementing some of the Weld-OSGi logic in a more Wildfly-friendly way? Or did you have an entirely different approach in mind?
> Initial OSGi / CDI Integration
> -------------------------------
>
> Key: JBOSGI-699
> URL: https://issues.jboss.org/browse/JBOSGI-699
> Project: JBoss OSGi
> Issue Type: Feature Request
> Components: cdi
> Reporter: Thomas Diesler
>
> Provide an example test that shows CDI integration
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months
