I'm not sure if this is possible, but there are multiple auto deploy
dirs under the osgi folder. Did you make sure a JAR with the bundle
name isn't somewhere else it can be auto-deployed?
And, it's probably a dumb quesiton, but you're sure that the gogo
shell output showing the bundle as Active is what you see after
deleting the module JAR?
Another potentially dumb question: are you sure one of those other
modules doesn't use the bundle name "wellcare-roster"?
If so, here are some hings to try:
Try to run, from gogo, uninstall 2048. If it works it probably won't
persist on restart though.
You might have to clean the osgi/state folder (delete it).
I'm a bit confused about the framework error you're seeing. I guess
it makes sense, a portlet service tracker is complaining that you're
uninstalling the bundle that provides a component that it defines as
"already in use". Just not sure what it's getting at precisely.
Edited to Add: That first Framework Error (already in use) is thrown
when adding the service (so, when you installed the module). I'm still
not sure what the NPE is all about.
However, look at the bundle ID for the bundle that was
uninstalled--it's 2058, not 2048 which is the active bundle id in the
gogo output you pasted. So yeah, you have another bundle floating
around. If you're sure it's not one of those other JARs, I'd go
through the gogo shell + osgi/state deletion procdeure I mentioned and
see if that wipes out your ghost bundle.
