July 2013 - jboss-osgi-issues - Jboss List Archives

[JBoss JIRA] (JBOSGI-671) Cannot get bytes from InputStream for DEPLOYMENT_ROOT VirtualFile.openStream() on second call

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-671?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-671: ---------------------------------- Comment: was deleted (was: Won't Fix - OSGi is going to get removed) > Cannot get bytes from InputStream for DEPLOYMENT_ROOT VirtualFile.openStream() on second call > --------------------------------------------------------------------------------------------- > > Key: JBOSGI-671 > URL: https://issues.jboss.org/browse/JBOSGI-671 > Project: JBoss OSGi > Issue Type: Bug > Reporter: Thomas Diesler > > The effect is that the copy of a installed OSGi bundle is 0bytes in the data/osgi-store area > Digging into this shows that during the first call isDirectory() is false and the file gets mounted. The returned stream works fine. For the second call isDirectory() is true and e read() on the returned InputStream returns -1 > {code} > public InputStream openStream() throws IOException { > if(isDirectory()) { > return new VirtualJarInputStream(this); > } > final VFS.Mount mount = VFS.getMount(this); > return mount.getFileSystem().openInputStream(mount.getMountPoint(), this); > } > {code} > I assume that the root VirtualFile > {code} > VirtualFile virtualFile = deploymentUnit.getAttachment(Attachments.DEPLOYMENT_ROOT).getRoot(); > {code} > should be readable twice. -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-681) Cannot restart webapp bundle after activation failure

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-681?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-681: ---------------------------------- Comment: was deleted (was: Won't Fix - OSGi is going to get removed) > Cannot restart webapp bundle after activation failure > ----------------------------------------------------- > > Key: JBOSGI-681 > URL: https://issues.jboss.org/browse/JBOSGI-681 > Project: JBoss OSGi > Issue Type: Bug > Reporter: Thomas Diesler > > {code} > Caused by: java.lang.IllegalStateException > at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:47) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at org.jboss.as.connector.deployers.ra.processors.CachedConnectionManagerSetupProcessor$CachedConnectionManagerSetupAction.setup(CachedConnectionManagerSetupProcessor.java:74) > at org.jboss.as.web.ThreadSetupBindingListener.bind(ThreadSetupBindingListener.java:50) > at org.apache.catalina.core.StandardContext.bindThread(StandardContext.java:4234) > at org.apache.catalina.core.StandardContext.start(StandardContext.java:3740) > at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:102) > {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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-677) Some javax.* bundles show version 0.0.0 in AS7

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-677?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-677: ---------------------------------- Comment: was deleted (was: Won't Fix - OSGi is going to get removed) > Some javax.* bundles show version 0.0.0 in AS7 > ---------------------------------------------- > > Key: JBOSGI-677 > URL: https://issues.jboss.org/browse/JBOSGI-677 > Project: JBoss OSGi > Issue Type: Bug > Reporter: Thomas Diesler > > Some javax bundles that we configure by default do not show valid bundle version info > javax.jws.api:0.0.0 > javax.ws.rs.api:0.0.0 > The javax.persistence.api has its metadata defined in jbosgi-xservice.properties like this > {code} > Bundle-SymbolicName: hibernate-jpa-2.0-api > Bundle-Version: 1.0.1.Final > Export-Package: javax.persistence.spi;version="2.0.0",javax.persistence.criteria;version="2.0.0",javax.persistence;version="2.0.0",javax.persistence.metamodel;version="2.0.0" > {code} > This should be replaced by metadata coming from the artefacts manifest. > Generally, all javax api artefacts should have valid OSGi metadata -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-681) Cannot restart webapp bundle after activation failure

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-681?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-681: ---------------------------------- Component/s: WildFly > Cannot restart webapp bundle after activation failure > ----------------------------------------------------- > > Key: JBOSGI-681 > URL: https://issues.jboss.org/browse/JBOSGI-681 > Project: JBoss OSGi > Issue Type: Bug > Components: WildFly > Reporter: Thomas Diesler > > {code} > Caused by: java.lang.IllegalStateException > at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:47) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at org.jboss.as.connector.deployers.ra.processors.CachedConnectionManagerSetupProcessor$CachedConnectionManagerSetupAction.setup(CachedConnectionManagerSetupProcessor.java:74) > at org.jboss.as.web.ThreadSetupBindingListener.bind(ThreadSetupBindingListener.java:50) > at org.apache.catalina.core.StandardContext.bindThread(StandardContext.java:4234) > at org.apache.catalina.core.StandardContext.start(StandardContext.java:3740) > at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:102) > {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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-679) Console does not support install/start semantic for bundles

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-679?page=com.atlassian.jira.plugin... ] Thomas Diesler resolved JBOSGI-679. ----------------------------------- Resolution: Won't Fix > Console does not support install/start semantic for bundles > ----------------------------------------------------------- > > Key: JBOSGI-679 > URL: https://issues.jboss.org/browse/JBOSGI-679 > Project: JBoss OSGi > Issue Type: Bug > Reporter: Thomas Diesler > Labels: Console > > Currently, when you deploy a bundle through the console it is started automatically. For a set of bundles it means that you must install them in order otherwise they might not resolve. > Digging up the related issues ... -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-677) Some javax.* bundles show version 0.0.0 in AS7

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-677?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-677: ---------------------------------- Component/s: WildFly > Some javax.* bundles show version 0.0.0 in AS7 > ---------------------------------------------- > > Key: JBOSGI-677 > URL: https://issues.jboss.org/browse/JBOSGI-677 > Project: JBoss OSGi > Issue Type: Bug > Components: WildFly > Reporter: Thomas Diesler > > Some javax bundles that we configure by default do not show valid bundle version info > javax.jws.api:0.0.0 > javax.ws.rs.api:0.0.0 > The javax.persistence.api has its metadata defined in jbosgi-xservice.properties like this > {code} > Bundle-SymbolicName: hibernate-jpa-2.0-api > Bundle-Version: 1.0.1.Final > Export-Package: javax.persistence.spi;version="2.0.0",javax.persistence.criteria;version="2.0.0",javax.persistence;version="2.0.0",javax.persistence.metamodel;version="2.0.0" > {code} > This should be replaced by metadata coming from the artefacts manifest. > Generally, all javax api artefacts should have valid OSGi metadata -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-678) Cannot restart jpa bundle after activation failure

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-678?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-678: ---------------------------------- Component/s: WildFly > Cannot restart jpa bundle after activation failure > -------------------------------------------------- > > Key: JBOSGI-678 > URL: https://issues.jboss.org/browse/JBOSGI-678 > Project: JBoss OSGi > Issue Type: Bug > Components: JPA/JDBC, WildFly > Reporter: Thomas Diesler > > {code} > Caused by: java.lang.IllegalStateException: JBAS014666: Duplicate resource persistence-bundle-b.jar#simple-persistence > at org.jboss.as.controller.registry.AbstractModelResource$DefaultResourceProvider.register(AbstractModelResource.java:225) > at org.jboss.as.controller.registry.AbstractModelResource.registerChild(AbstractModelResource.java:135) > at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.addManagementConsole(PersistenceUnitServiceHandler.java:727) > at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.deployPersistenceUnit(PersistenceUnitServiceHandler.java:406) > at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.addPuService(PersistenceUnitServiceHandler.java:274) > at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.handleJarDeployment(PersistenceUnitServiceHandler.java:142) > at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.deploy(PersistenceUnitServiceHandler.java:117) > at org.jboss.as.jpa.processor.PersistenceCompleteInstallProcessor.deploy(PersistenceCompleteInstallProcessor.java:48) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:120) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2 > {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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-678) Cannot restart jpa bundle after activation failure

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-678?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-678: ---------------------------------- Comment: was deleted (was: Won't Fix - OSGi is going to get removed) > Cannot restart jpa bundle after activation failure > -------------------------------------------------- > > Key: JBOSGI-678 > URL: https://issues.jboss.org/browse/JBOSGI-678 > Project: JBoss OSGi > Issue Type: Bug > Components: JPA/JDBC > Reporter: Thomas Diesler > > {code} > Caused by: java.lang.IllegalStateException: JBAS014666: Duplicate resource persistence-bundle-b.jar#simple-persistence > at org.jboss.as.controller.registry.AbstractModelResource$DefaultResourceProvider.register(AbstractModelResource.java:225) > at org.jboss.as.controller.registry.AbstractModelResource.registerChild(AbstractModelResource.java:135) > at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.addManagementConsole(PersistenceUnitServiceHandler.java:727) > at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.deployPersistenceUnit(PersistenceUnitServiceHandler.java:406) > at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.addPuService(PersistenceUnitServiceHandler.java:274) > at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.handleJarDeployment(PersistenceUnitServiceHandler.java:142) > at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.deploy(PersistenceUnitServiceHandler.java:117) > at org.jboss.as.jpa.processor.PersistenceCompleteInstallProcessor.deploy(PersistenceCompleteInstallProcessor.java:48) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:120) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2 > {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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-667) OSGi: "Export-EJB" header is not supported to install/start EJB3 bundle from repository

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-667?page=com.atlassian.jira.plugin... ] Thomas Diesler commented on JBOSGI-667: --------------------------------------- This is a conceptual issue that cannot get fixed easily. Subsystem capabilities are considered to be part of the WildFly configuration - they are not deployments that go through the chain of deployment unit processors (DUP) where the JavaEE integration happens. WildFly does support persistent deployments. When you deploy ejb-high-velocity-queue-mdb regularly, it should redeploy on server restart. The start level can however not be associated with the deployment because of WFLY-1643. Please vote on that issue. > OSGi: "Export-EJB" header is not supported to install/start EJB3 bundle from repository > --------------------------------------------------------------------------------------- > > Key: JBOSGI-667 > URL: https://issues.jboss.org/browse/JBOSGI-667 > Project: JBoss OSGi > Issue Type: Bug > Reporter: Igor Shulika > > I am using the latest WildFly 8.0.0.Alpha2-SNAPSHOT server to install/start all of my OSGi bundles from Maven repository. The EJB 3 MDB is not starting if I am just declare capability in the standalone-osgi.xml file. > > Here is my capability configuration. > <capability name="org.test.ejb3.mdb:ejb-high-velocity-queue-mdb:1.0" startlevel="4"/> > > Note: When I just simply drop my EJB 3 MDB JAR file inside "deployments" directory the message driven bean starting successfully (see below). > INFO [org.jboss.as.ejb3] (MSC service thread 1-2) JBAS014142: Started message driven bean 'HighVelocityQueueMessageBean' with 'hornetq-ra' resource adapter. -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-667) OSGi: "Export-EJB" header is not supported to install/start EJB3 bundle from repository

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-667?page=com.atlassian.jira.plugin... ] Thomas Diesler commented on JBOSGI-667: --------------------------------------- Due to insufficient demand it has been decided to remove OSGi as Tech Preview from EAP. OSGi will continue to be available in WildFly via regular JBOSGi releases. > OSGi: "Export-EJB" header is not supported to install/start EJB3 bundle from repository > --------------------------------------------------------------------------------------- > > Key: JBOSGI-667 > URL: https://issues.jboss.org/browse/JBOSGI-667 > Project: JBoss OSGi > Issue Type: Bug > Reporter: Igor Shulika > > I am using the latest WildFly 8.0.0.Alpha2-SNAPSHOT server to install/start all of my OSGi bundles from Maven repository. The EJB 3 MDB is not starting if I am just declare capability in the standalone-osgi.xml file. > > Here is my capability configuration. > <capability name="org.test.ejb3.mdb:ejb-high-velocity-queue-mdb:1.0" startlevel="4"/> > > Note: When I just simply drop my EJB 3 MDB JAR file inside "deployments" directory the message driven bean starting successfully (see below). > INFO [org.jboss.as.ejb3] (MSC service thread 1-2) JBAS014142: Started message driven bean 'HighVelocityQueueMessageBean' with 'hornetq-ra' resource adapter. -- 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

12 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-osgi-issues July 2013