[JBoss JIRA] (JBOSGI-753) ServiceTracker ignores filter when started with "open(true)"
by Daniel Yokomizo (JIRA)
Daniel Yokomizo created JBOSGI-753:
--------------------------------------
Summary: ServiceTracker ignores filter when started with "open(true)"
Key: JBOSGI-753
URL: https://issues.jboss.org/browse/JBOSGI-753
Project: JBoss OSGi
Issue Type: Bug
Security Level: Public (Everyone can see)
Environment: Linux 3.5.0-43-generic #66-Ubuntu SMP Wed Oct 23 17:33:43 UTC 2013 i686 i686 i686 GNU/Linux
java version "1.7.0_25"
OpenJDK Runtime Environment (IcedTea 2.3.10) (7u25-2.3.10-1ubuntu0.12.10.2)
OpenJDK Server VM (build 23.7-b01, mixed mode)
WildFly-8.0.0.Beta1
JBossOSGi-2.1.0
Reporter: Daniel Yokomizo
Assignee: Thomas Diesler
I created a project on github[1] to illustrate the problem. I have a bundle activator that instantiates a ServiceTracker with some filter and calls "open(true)" on it. In another bundle I register a couple of services. The tracker ends up calling its customizer's "addingService(ServiceReference)" for all registered services, regardless if they match or not the filter. When starting the ServiceTracker with "open()" or "open(false)" only the matching services are passed to the customizer.
The specification states that only matching services should be tracked:
http://www.osgi.org/javadoc/r5/core/org/osgi/util/tracker/ServiceTracker....
The server.log contents, showing the incorrect calls, are:
22:03:56,949 INFO [stdout] (MSC service thread 1-1) ServiceATracker.addingService(ServiceState{service.id=20, objectClass=[test.ServiceA], foo=bar})
22:03:56,950 INFO [stdout] (MSC service thread 1-1) ServiceBTracker.addingService(ServiceState{service.id=20, objectClass=[test.ServiceA], foo=bar})
22:03:56,951 INFO [stdout] (MSC service thread 1-1) ServiceATracker.addingService(ServiceState{service.id=21, objectClass=[test.ServiceB], foo=bar})
22:03:56,952 INFO [stdout] (MSC service thread 1-1) ServiceBTracker.addingService(ServiceState{service.id=21, objectClass=[test.ServiceB], foo=bar})
1. https://github.com/dyokomizo/wildfly-service-tracker-test
--
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, 5 months
- 1
- 0
[JBoss JIRA] (JBOSGI-752) Deployment hangs if BundleActivator.start tries to install bundle using pax-url-mvn
by Daniel Yokomizo (JIRA)
[ https://issues.jboss.org/browse/JBOSGI-752?page=com.atlassian.jira.plugin... ]
Daniel Yokomizo updated JBOSGI-752:
-----------------------------------
Workaround Description: If we start a background thread to call both BundleContext.install(String) the installation works, but calling Bundle.uninstall() inside Bundle.stop() also hangs.
> Deployment hangs if BundleActivator.start tries to install bundle using pax-url-mvn
> -----------------------------------------------------------------------------------
>
> Key: JBOSGI-752
> URL: https://issues.jboss.org/browse/JBOSGI-752
> Project: JBoss OSGi
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Environment: Linux 3.5.0-43-generic #66-Ubuntu SMP Wed Oct 23 17:33:43 UTC 2013 i686 i686 i686 GNU/Linux
> java version "1.7.0_25"
> OpenJDK Runtime Environment (IcedTea 2.3.10) (7u25-2.3.10-1ubuntu0.12.10.2)
> OpenJDK Server VM (build 23.7-b01, mixed mode)
> WildFly-8.0.0.Beta1
> JBossOSGi-2.1.0
> Reporter: Daniel Yokomizo
> Assignee: Thomas Diesler
>
> I created a project on github[1] to illustrate the problem. I have a bundle activator that on start tries to install another bundle using pax-url-mvn. The bundle's deployment hangs instead of installing the bundle. After that even pressing CTRL+C on the console won't fully shutdown the server, it's necessary to kill -9 a single remaining process.
> The server.log contents (up to hanging) are:
> 2013-11-11 19:18:52,246 INFO [org.jboss.as.repository] (management-handler-thread - 2) JBAS014900: Content added at location <redacted>/wildfly-8.0.0.Beta1/standalone/data/content/fb/8cd3f1c0af3cbce9cee495848969aebe084da2/content
> 2013-11-11 19:18:52,249 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "pax-url-mvn-1.3.5.jar" (runtime-name: "pax-url-mvn-1.3.5.jar")
> 2013-11-11 19:18:52,282 INFO [org.jboss.osgi.framework] (MSC service thread 1-5) JBOSGI011001: Bundle installed: org.ops4j.pax.url.mvn:1.3.5
> 2013-11-11 19:18:52,335 INFO [org.jboss.osgi.framework] (MSC service thread 1-1) JBOSGI011002: Bundle started: org.ops4j.pax.url.mvn:1.3.5
> 2013-11-11 19:18:52,357 INFO [org.jboss.as.server] (management-handler-thread - 2) JBAS018559: Deployed "pax-url-mvn-1.3.5.jar" (runtime-name : "pax-url-mvn-1.3.5.jar")
> 2013-11-11 19:18:52,502 INFO [org.jboss.as.repository] (management-handler-thread - 3) JBAS014900: Content added at location <redacted>/wildfly-8.0.0.Beta1/standalone/data/content/b3/eaa327823200f054fd3f9cac87e7f7bc4174a5/content
> 2013-11-11 19:18:52,505 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "wildfly-pax-url-mvn-test-0.0.1.jar" (runtime-name: "wildfly-pax-url-mvn-test-0.0.1.jar")
> 2013-11-11 19:18:52,518 INFO [org.jboss.osgi.framework] (MSC service thread 1-1) JBOSGI011001: Bundle installed: wildfly-pax-url-mvn-test:0.0.1
> 2013-11-11 19:18:52,542 INFO [stdout] (MSC service thread 1-4) Activator: Installed Bundles List
> 2013-11-11 19:18:52,542 INFO [stdout] (MSC service thread 1-4) org.jboss.spec.javax.annotation.jboss-annotations-api_1.2_spec RESOLVED
> 2013-11-11 19:18:52,543 INFO [stdout] (MSC service thread 1-4) org.jboss.osgi.framework ACTIVE
> 2013-11-11 19:18:52,543 INFO [stdout] (MSC service thread 1-4) org.ops4j.pax.url.mvn ACTIVE
> 2013-11-11 19:18:52,543 INFO [stdout] (MSC service thread 1-4) wildfly-pax-url-mvn-test STARTING
> 2013-11-11 19:18:52,544 INFO [stdout] (MSC service thread 1-4) Activator: Installing Guava
> 1. https://github.com/dyokomizo/wildfly-pax-url-mvn-test
--
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, 5 months
- 1
- 0
[JBoss JIRA] (JBOSGI-752) Deployment hangs if BundleActivator.start tries to install bundle using pax-url-mvn
by Daniel Yokomizo (JIRA)
Daniel Yokomizo created JBOSGI-752:
--------------------------------------
Summary: Deployment hangs if BundleActivator.start tries to install bundle using pax-url-mvn
Key: JBOSGI-752
URL: https://issues.jboss.org/browse/JBOSGI-752
Project: JBoss OSGi
Issue Type: Bug
Security Level: Public (Everyone can see)
Environment: Linux 3.5.0-43-generic #66-Ubuntu SMP Wed Oct 23 17:33:43 UTC 2013 i686 i686 i686 GNU/Linux
java version "1.7.0_25"
OpenJDK Runtime Environment (IcedTea 2.3.10) (7u25-2.3.10-1ubuntu0.12.10.2)
OpenJDK Server VM (build 23.7-b01, mixed mode)
WildFly-8.0.0.Beta1
JBossOSGi-2.1.0
Reporter: Daniel Yokomizo
Assignee: Thomas Diesler
I created a project on github[1] to illustrate the problem. I have a bundle activator that on start tries to install another bundle using pax-url-mvn. The bundle's deployment hangs instead of installing the bundle. After that even pressing CTRL+C on the console won't fully shutdown the server, it's necessary to kill -9 a single remaining process.
The server.log contents (up to hanging) are:
2013-11-11 19:18:52,246 INFO [org.jboss.as.repository] (management-handler-thread - 2) JBAS014900: Content added at location <redacted>/wildfly-8.0.0.Beta1/standalone/data/content/fb/8cd3f1c0af3cbce9cee495848969aebe084da2/content
2013-11-11 19:18:52,249 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "pax-url-mvn-1.3.5.jar" (runtime-name: "pax-url-mvn-1.3.5.jar")
2013-11-11 19:18:52,282 INFO [org.jboss.osgi.framework] (MSC service thread 1-5) JBOSGI011001: Bundle installed: org.ops4j.pax.url.mvn:1.3.5
2013-11-11 19:18:52,335 INFO [org.jboss.osgi.framework] (MSC service thread 1-1) JBOSGI011002: Bundle started: org.ops4j.pax.url.mvn:1.3.5
2013-11-11 19:18:52,357 INFO [org.jboss.as.server] (management-handler-thread - 2) JBAS018559: Deployed "pax-url-mvn-1.3.5.jar" (runtime-name : "pax-url-mvn-1.3.5.jar")
2013-11-11 19:18:52,502 INFO [org.jboss.as.repository] (management-handler-thread - 3) JBAS014900: Content added at location <redacted>/wildfly-8.0.0.Beta1/standalone/data/content/b3/eaa327823200f054fd3f9cac87e7f7bc4174a5/content
2013-11-11 19:18:52,505 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "wildfly-pax-url-mvn-test-0.0.1.jar" (runtime-name: "wildfly-pax-url-mvn-test-0.0.1.jar")
2013-11-11 19:18:52,518 INFO [org.jboss.osgi.framework] (MSC service thread 1-1) JBOSGI011001: Bundle installed: wildfly-pax-url-mvn-test:0.0.1
2013-11-11 19:18:52,542 INFO [stdout] (MSC service thread 1-4) Activator: Installed Bundles List
2013-11-11 19:18:52,542 INFO [stdout] (MSC service thread 1-4) org.jboss.spec.javax.annotation.jboss-annotations-api_1.2_spec RESOLVED
2013-11-11 19:18:52,543 INFO [stdout] (MSC service thread 1-4) org.jboss.osgi.framework ACTIVE
2013-11-11 19:18:52,543 INFO [stdout] (MSC service thread 1-4) org.ops4j.pax.url.mvn ACTIVE
2013-11-11 19:18:52,543 INFO [stdout] (MSC service thread 1-4) wildfly-pax-url-mvn-test STARTING
2013-11-11 19:18:52,544 INFO [stdout] (MSC service thread 1-4) Activator: Installing Guava
1. https://github.com/dyokomizo/wildfly-pax-url-mvn-test
--
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, 5 months
- 1
- 0
- ← Newer
- 1
- Older →