| Summary: | BundleException when persistence bundle refreshed | ||
|---|---|---|---|
| Product: | [RT] Gemini.JPA | Reporter: | Shaun Smith <shaun.smith> |
| Component: | Core | Assignee: | Michael Keith <michael.keith> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | eduard.bartsch, jan.sievers, krum.tsvetkov |
| Version: | 1.0.0 | ||
| Target Milestone: | 1.0.0 RC2 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Shaun Smith
I am seeing the same problem sporadically with a different sample application, during startup of the OSGi framework. And I'm pretty sure there is no re-start of the DataSourceFactory. I'm still wondering if the refreshPackages could be avoided in some way (and by this prevent problems like this one). But I already asked this in Bug 337157, hoping to get a better understanding why it is done. Not sure about this one, but it may be related to a timing problem of the bundle being in some middle state after being installed but not yet started and that it is being refreshed before it has been activated. In any case, I think it has to do with the refresh, rather than the data source not being started yet. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=337157 for an explanation of why the refresh happens. I will be looking into this issue soon, I hope. I can't reproduce but while fixing 342996 I saw some funniness in the state change code that could have caused this. Am hoping that it is fixed, now, but if someone encounters this again please reopen this bug. |