April 2010 - jboss-osgi-issues - Jboss List Archives

[JBoss JIRA] Created: (JBOSGI-241) Framework classpath

by Thomas Diesler (JIRA)

Framework classpath ------------------- Key: JBOSGI-241 URL: https://jira.jboss.org/jira/browse/JBOSGI-241 Project: JBoss OSGi Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Thomas Diesler -- 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, 8 months

1
10
0 / 0

[JBoss JIRA] Created: (JBOSGI-248) Framework lifecycle

by Thomas Diesler (JIRA)

Framework lifecycle ------------------- Key: JBOSGI-248 URL: https://jira.jboss.org/jira/browse/JBOSGI-248 Project: JBoss OSGi Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Thomas Diesler -- 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, 8 months

1
8
0 / 0

[JBoss JIRA] Created: (JBOSGI-209) Implement resolver preferences

by Thomas Diesler (JIRA)

Implement resolver preferences ------------------------------ Key: JBOSGI-209 URL: https://jira.jboss.org/jira/browse/JBOSGI-209 Project: JBoss OSGi Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Core Framework Reporter: Thomas Diesler Assignee: Adrian Brock Fix For: JBossOSGi 1.0.x The following list defines the preferences, if multiple choices are possible, in order of decreasing priority: * A resolved exporter must be preferred over an unresolved exporter. * An exporter with a higher version is preferred over an exporter with a lower version. * An exporter with a lower bundle ID is preferred over a bundle with a higher ID. -- 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

1
7
0 / 0

[JBoss JIRA] Created: (JBOSGI-195) Provide a LifecycleInterceptorAdaptor for Deployers

by Thomas Diesler (JIRA)

Provide a LifecycleInterceptorAdaptor for Deployers --------------------------------------------------- Key: JBOSGI-195 URL: https://jira.jboss.org/jira/browse/JBOSGI-195 Project: JBoss OSGi Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Other Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.x This is to re-use existing Deployer logic. -- 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

1
2
0 / 0

[JBoss JIRA] Created: (JBOSGI-294) WebApp Extender fails on embedded Equinox

by Thomas Diesler (JIRA)

WebApp Extender fails on embedded Equinox ----------------------------------------- Key: JBOSGI-294 URL: https://jira.jboss.org/jira/browse/JBOSGI-294 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: jboss-osgi-webapp Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.x We have an intermittent failure with Equinox where the registered endpoint is not available. In the logfile I see 2010-02-23 00:10:41,947 DEBUG [org.ops4j.pax.web.extender.war.internal.Activator] Pax Web WAR Extender - Started 2010-02-23 00:10:41,947 DEBUG [org.ops4j.pax.swissbox.extender.BundleWatcher] Scanning bundle [org.ops4j.pax.web.pax-web-extender-war] 2010-02-23 00:10:41,948 DEBUG [org.jboss.osgi.spi.util.ExportedPackageHelper] Exported-Packages: org.ops4j.pax.web.pax-web-extender-war 2010-02-23 00:10:41,958 DEBUG [org.ops4j.pax.swissbox.extender.BundleWatcher] Scanning bundle [example-webapp] 2010-02-23 00:10:41,962 DEBUG [org.ops4j.pax.swissbox.extender.BundleWatcher] Found resources [bundleentry://9.fwk11165301/WEB-INF/web.xml] 2010-02-23 00:10:41,964 DEBUG [org.ops4j.pax.web.extender.war.internal.WebXmlObserver] Parsing a web application from [bundleentry://9.fwk11165301/WEB-INF/web.xml] 2010-02-23 00:10:41,969 DEBUG [org.ops4j.pax.web.service.internal.ConfigurationImpl] Reading configuration property org.ops4j.pax.web.session.timeout has failed 2010-02-23 00:10:41,970 DEBUG [org.ops4j.pax.web.service.jetty.internal.ServerControllerImpl] Configuring server [ServerControllerImpl{state=UNCONFIGURED}] -> [ConfigurationImpl{http enabled=true,http port=8090,http secure enabled=false,http secure port=8443,ssl keystore=/home/hudson/.keystore,ssl keystoreType=null,session timeout=null,session url=null,session cookie=null,worker name=null,listening addresses=[Ljava.lang.String;@89a2d9}] 2010-02-23 00:10:41,972 DEBUG [org.ops4j.pax.web.service.jetty.internal.ServerControllerImpl] Starting server [ServerControllerImpl{state=STOPPED}] 2010-02-23 00:10:41,992 DEBUG [org.ops4j.pax.web.extender.war.internal.WebXmlObserver] Parsed web app [WebApp{displayName=WebApp Sample,contextName=null}] 2010-02-23 00:10:41,993 DEBUG [org.ops4j.pax.web.extender.war.internal.WebXmlObserver] No 'Webapp-Context' manifest attribute specified 2010-02-23 00:10:41,993 DEBUG [org.ops4j.pax.web.extender.war.internal.WebXmlObserver] Using bundle symbolic name [example-webapp] as context name 2010-02-23 00:10:41,993 INFO [org.ops4j.pax.web.extender.war.internal.WebXmlObserver] Using [example-webapp] as web application context name 2010-02-23 00:10:41,993 DEBUG [org.ops4j.pax.web.extender.war.internal.WebAppPublisher] Publishing web application [WebApp{displayName=WebApp Sample,contextName=example-webapp}] 2010-02-23 00:10:41,999 DEBUG [org.ops4j.pax.swissbox.tracker.ReplaceableService] Creating replaceable service for [interface org.osgi.service.http.HttpService] 2010-02-23 00:10:42,003 DEBUG [org.ops4j.pax.swissbox.tracker.ServiceCollection] Creating service collection for [interface org.osgi.service.http.HttpService] 2010-02-23 00:10:42,005 DEBUG [org.jboss.osgi.spi.util.ExportedPackageHelper] Exported-Packages: example-webapp 2010-02-23 00:10:42,007 DEBUG [org.jboss.osgi.testing.OSGiTest] ### START org.jboss.test.osgi.example.webapp.WebAppExtenderTestCase 2010-02-23 00:10:42,018 DEBUG [org.ops4j.pax.web.service.internal.ConfigurationImpl] Reading configuration property org.ops4j.pax.web.session.timeout has failed 2010-02-23 00:10:42,019 DEBUG [org.ops4j.pax.web.service.jetty.internal.JettyServerImpl] Starting JettyServerImpl{} 2010-02-23 00:10:42,019 DEBUG [org.mortbay.jetty] jetty-6.1.x 2010-02-23 00:10:42,044 DEBUG [org.mortbay.jetty] Container JettyServerWrapper@1fa12f6 + org.mortbay.thread.QueuedThreadPool@11c7f8d as threadpool 2010-02-23 00:10:42,048 DEBUG [org.mortbay.jetty] started org.mortbay.thread.QueuedThreadPool@11c7f8d 2010-02-23 00:10:42,048 DEBUG [org.mortbay.jetty] starting JettyServerWrapper@1fa12f6 2010-02-23 00:10:42,050 DEBUG [org.mortbay.jetty] started JettyServerWrapper@1fa12f6 2010-02-23 00:10:42,063 INFO [org.ops4j.pax.web.service.jetty.internal.JettyServerImpl] Pax Web available at [0.0.0.0]:[8090] 2010-02-23 00:10:42,064 DEBUG [org.mortbay.jetty] Container JettyServerWrapper@1fa12f6 + NIOSocketConnectorWrapper@0.0.0.0:8090 as connector 2010-02-23 00:10:42,074 DEBUG [org.mortbay.jetty] started org.mortbay.jetty.nio.SelectChannelConnector$1@54c2b8 2010-02-23 00:10:42,078 DEBUG [org.mortbay.jetty] Started NIOSocketConnectorWrapper@0.0.0.0:8090 2010-02-23 00:10:42,079 DEBUG [org.mortbay.jetty] started NIOSocketConnectorWrapper@0.0.0.0:8090 2010-02-23 00:10:42,080 DEBUG [org.ops4j.pax.web.service.internal.ConfigurationImpl] Reading configuration property org.ops4j.pax.web.session.timeout has failed 2010-02-23 00:10:42,084 DEBUG [org.ops4j.pax.web.service.internal.ConfigurationImpl] Reading configuration property org.ops4j.pax.web.session.timeout has failed 2010-02-23 00:10:42,087 DEBUG [org.ops4j.pax.web.service.jetty.internal.ServerControllerImpl] Configuring server [ServerControllerImpl{state=STARTED}] -> [ConfigurationImpl{http enabled=true,http port=8090,http secure enabled=false,http secure port=8443,ssl keystore=/home/hudson/.keystore,ssl keystoreType=null,session timeout=null,session url=null,session cookie=null,worker name=null,listening addresses=[Ljava.lang.String;@a17378}] 2010-02-23 00:10:42,088 DEBUG [org.ops4j.pax.web.service.jetty.internal.ServerControllerImpl] Stopping server [ServerControllerImpl{state=STARTED}] 2010-02-23 00:10:42,088 DEBUG [org.ops4j.pax.web.service.jetty.internal.JettyServerImpl] Stopping JettyServerImpl{} 2010-02-23 00:10:42,090 DEBUG [org.mortbay.jetty] stopped org.mortbay.jetty.nio.SelectChannelConnector$1@54c2b8 2010-02-23 00:10:42,091 DEBUG [org.mortbay.jetty] stopped NIOSocketConnectorWrapper@0.0.0.0:8090 2010-02-23 00:10:42,091 DEBUG [org.mortbay.jetty] stopping JettyServerWrapper@1fa12f6 2010-02-23 00:10:42,095 DEBUG [org.ops4j.pax.swissbox.tracker.ServiceCollection] Added service with reference [{org.osgi.service.http.HttpService, org.ops4j.pax.web.service.WebContainer}={org.ops4j.pax.web.ssl.keystore=/home/hudson/.keystore, org.osgi.service.http.port.secure=8443, org.ops4j.pax.web.listening.addresses=, org.osgi.service.http.port=8090, org.ops4j.pax.web.ssl.clientauthneeded=false, org.osgi.service.http.useNIO=true, org.osgi.service.http.enabled=true, org.osgi.service.http.secure.enabled=true, org.ops4j.pax.web.ssl.clientauthwanted=false, javax.servlet.context.tempdir=/tmp/.paxweb1233425339357219478, service.id=35}] 2010-02-23 00:10:42,096 INFO [org.ops4j.pax.web.service.internal.HttpServiceFactoryImpl] Binding bundle: [example-webapp_0.0.0 [9]] to http service 2010-02-23 00:10:42,105 DEBUG [org.ops4j.pax.web.service.internal.HttpServiceStarted] Creating http service for: example-webapp_0.0.0 [9] Why is Jetty being stopped? Stopping server [ServerControllerImpl{state=STARTED}] -- 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

1
3
0 / 0

[JBoss JIRA] Created: (JBOSGI-293) Cannot start example-jndi on Felix

by Thomas Diesler (JIRA)

Cannot start example-jndi on Felix ---------------------------------- Key: JBOSGI-293 URL: https://jira.jboss.org/jira/browse/JBOSGI-293 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Integration (Felix) Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta7 Caused by: javax.naming.CommunicationException: Could not obtain connection to any of these urls: 127.0.0.1:1099 and discovery failed with error: javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out] at org.jnp.interfaces.NamingContext.discoverServer(NamingContext.java:1682) at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1753) at org.jnp.interfaces.NamingContext.createSubcontext(NamingContext.java:1108) at org.jnp.interfaces.NamingContext.createSubcontext(NamingContext.java:1098) at javax.naming.InitialContext.createSubcontext(InitialContext.java:464) at org.jboss.test.osgi.example.jndi.bundle.JNDIExampleActivator.start(JNDIExampleActivator.java:46) at org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:640) at org.apache.felix.framework.Felix.activateBundle(Felix.java:1700) at org.apache.felix.framework.Felix.startBundle(Felix.java:1622) at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:915) at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:902) at org.apache.aries.jmx.framework.Framework.startBundle(Framework.java:298) Caused by: java.lang.ClassNotFoundException: org.jnp.server.NamingServer_Stub (no security manager: RMI class loader disabled) at sun.rmi.server.LoaderHandler.loadClass(LoaderHandler.java:375) at sun.rmi.server.LoaderHandler.loadClass(LoaderHandler.java:165) at java.rmi.server.RMIClassLoader$2.loadClass(RMIClassLoader.java:620) at org.jboss.system.JBossRMIClassLoader.loadClass(JBossRMIClassLoader.java:91) at java.rmi.server.RMIClassLoader.loadClass(RMIClassLoader.java:247) -- 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

1
2
0 / 0

[JBoss JIRA] Created: (JBOSGI-214) Cannot repeatedly register service bound to an interface from the system classpath

by Thomas Diesler (JIRA)

Cannot repeatedly register service bound to an interface from the system classpath ---------------------------------------------------------------------------------- Key: JBOSGI-214 URL: https://jira.jboss.org/jira/browse/JBOSGI-214 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Integration (Equinox) Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.x -- 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

1
5
0 / 0

[JBoss JIRA] Created: (JBOSGI-147) Autostart in JBossAS recycle the bundle

by Thomas Diesler (JIRA)

Autostart in JBossAS recycle the bundle --------------------------------------- Key: JBOSGI-147 URL: https://jira.jboss.org/jira/browse/JBOSGI-147 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Integration (JBoss) Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.x -- 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

1
3
0 / 0

[JBoss JIRA] Created: (JBOSGI-261) Service Integration Javadoc

by Thomas Diesler (JIRA)

Service Integration Javadoc ---------------------------- Key: JBOSGI-261 URL: https://jira.jboss.org/jira/browse/JBOSGI-261 Project: JBoss OSGi Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assignee: Ales Justin -- 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

1
7
0 / 0

[JBoss JIRA] Created: (JBOSGI-196) Provide a DeployerAdaptor for LifecycleInterceptors

by Thomas Diesler (JIRA)

Provide a DeployerAdaptor for LifecycleInterceptors --------------------------------------------------- Key: JBOSGI-196 URL: https://jira.jboss.org/jira/browse/JBOSGI-196 Project: JBoss OSGi Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Other Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.x This is to re-use existing Deployer logic. -- 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

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-osgi-issues April 2010