[ 
http://issues.ops4j.org/jira/browse/PAXWEBEX-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11729#action_11729
 ] 

Damian Golda commented on PAXWEBEX-28:
--------------------------------------

I found, that while stopping bundle, HttpServiceFactoryImpl.ungetService is 
called but HttpServiceTracker is NOT notified that HttpService is unregistered 
(no removedService call).
So HttpServiceTracker doesn't notify listeners that means WebApplication and 
WebApplication still keeps reference to HttpService which actually is 
HttpServiceProxy to HttpServiceStopped.

When I start my bundle again, the same WebApplication is used and pax web 
whiteboard try to register servlet in HttpServiceStopped which fails.



> Stop and start for bundle with servlet gets Http service has already been 
> stopped
> ---------------------------------------------------------------------------------
>
>                 Key: PAXWEBEX-28
>                 URL: http://issues.ops4j.org/jira/browse/PAXWEBEX-28
>             Project: Pax Web Extender
>          Issue Type: Bug
>          Components: whiteboard extender
>    Affects Versions: 0.4.0
>            Reporter: Damian Golda
>            Assignee: Damian Golda
>
> I start equinox with org.ops4j.pax.web.extender.whiteboard, 
> org.ops4j.pax.web.bundle and my whiteboard.test with simple servlet:
> ss
> Framework is launched.
> id    State       Bundle
> 0     ACTIVE      org.eclipse.osgi_3.4.0.v20080605-1900
>                   Fragments=1
> 1     RESOLVED    org.eclipse.equinox.weaving.hook_1.0.0.200809192119
>                   Master=0
> 2     ACTIVE      org.mortbay.jetty.util_6.1.11
> 3     ACTIVE      org.eclipse.osgi.services_3.1.200.v20071203
> 4     ACTIVE      org.ops4j.pax.logging.pax-logging-api_1.1.1
> 5     ACTIVE      org.ops4j.pax.web.extender.whiteboard_0.4.0.SNAPSHOT
> 6     ACTIVE      org.ops4j.pax.logging.pax-logging-service_1.1.1
> 7     ACTIVE      whiteboard.test_1.0.0
> 8     ACTIVE      org.mortbay.jetty.server_6.1.11
> 9     ACTIVE      org.mortbay.jetty.servlet-api-2.5_2.5.0
> 10    ACTIVE      org.ops4j.pax.web.bundle_0.5.2.SNAPSHOT
> 11    ACTIVE      org.apache.felix.configadmin_1.0.1
> Then, I stop my bundle:
> osgi> stop 7
> ..
> [OSGi Console] INFO org.ops4j.pax.web.service.internal.HttpServiceProxy - 
> Stopping http service: [EMAIL PROTECTED]
> [OSGi Console] INFO org.ops4j.pax.web.service.internal.HttpServiceStopped - 
> Changing HttpService state to [EMAIL PROTECTED]
> ...
> Then, I start my bundle again:
> start 7
> [OSGi Console] DEBUG 
> org.ops4j.pax.web.extender.whiteboard.internal.tracker.AbstractTracker - 
> Service available {javax.servlet.http.HttpServlet}={alias=/hello, 
> service.id=30}
> [OSGi Console] INFO org.ops4j.pax.web.service.internal.HttpServiceProxy - 
> Registering servlet: [/hello] -> [EMAIL PROTECTED]
> [OSGi Console] WARN org.ops4j.pax.web.service.internal.HttpServiceStopped - 
> Http service has already been stopped
> And my servlet is not registered in pax web service.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.ops4j.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

_______________________________________________
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general

Reply via email to