Issues holding us back from upgrading to 1.8.0
|
View:
New views
5 Messages
—
Rating Filter:
Alert me
|
 |
Issues holding us back from upgrading to 1.8.0
by Don Brown-5
::
Rate this Message:
With a set of releases out the door, I set to look at upgrading our
(Atlassian) usage of felix from a forked 1.2.1 to 1.8.0. These seem to be the issues remaining: * Strange issue with WebLogic 9.2 - https://issues.apache.org/jira/browse/FELIX-1158 * Ability to disable "helpful" boot delegation - https://issues.apache.org/jira/browse/FELIX-712 * Memory leak when restarting Felix - https://issues.apache.org/jira/browse/FELIX-1170 * Occasional concurrency issue with the filter cache - https://issues.apache.org/jira/browse/FELIX-765 FELIX-1170 was fixed, but only in trunk. Any chance I could get it backported to 1.8? FELIX-765 was reported fixed, but I won't know until we run it under load for a while. Yes, FELIX-1158 makes no sense, but it is the only way we could get it working in WebLogic 9.2 Since FELIX-712, if accepted, would involve a new feature, am I right in guessing I'll need to wait till Felix 2.0 to upgrade? The reason it is more important now is the behavior seems to exist for resources as well as classes, which will definitely cause issues for us. Don --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
Re: Issues holding us back from upgrading to 1.8.0
by Karl Pauls
::
Rate this Message:
On Fri, Jun 19, 2009 at 9:55 AM, Don Brown<donald.brown@...> wrote:
> With a set of releases out the door, I set to look at upgrading our > (Atlassian) usage of felix from a forked 1.2.1 to 1.8.0. These seem > to be the issues remaining: > * Strange issue with WebLogic 9.2 - > https://issues.apache.org/jira/browse/FELIX-1158 I just commented on the issue as well but please retry with the latest version of felix (or even better, on trunk) as I think this should be fixed already. > * Ability to disable "helpful" boot delegation - > https://issues.apache.org/jira/browse/FELIX-712 > * Memory leak when restarting Felix - > https://issues.apache.org/jira/browse/FELIX-1170 This one has been applied to trunk (as you mention below). We are planning a bugfix release so we might be able to look into backporting. > * Occasional concurrency issue with the filter cache - > https://issues.apache.org/jira/browse/FELIX-765 Please try it under load and see whether it is fixed. Reopen if not. > FELIX-1170 was fixed, but only in trunk. Any chance I could get it > backported to 1.8? FELIX-765 was reported fixed, but I won't know > until we run it under load for a while. Yes, FELIX-1158 makes no > sense, but it is the only way we could get it working in WebLogic 9.2 Again, I don't think it is strange (the urlhandlers are a minefield) but I have high hopes that it should be fixed by now. Please retry and let me know. > Since FELIX-712, if accepted, would involve a new feature, am I right > in guessing I'll need to wait till Felix 2.0 to upgrade? The reason > it is more important now is the behavior seems to exist for resources > as well as classes, which will definitely cause issues for us. We are planning a bugfix release and will look into your issues and whether we can port them back or not. I don't think FELIX-712 would need to wait for 2.0 but I have to discuss this with richard first. Please try to look into verifying the issues I commented on asap so that we know what to include or not. regards, Karl > Don > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@... > For additional commands, e-mail: users-help@... > > -- Karl Pauls karlpauls@... --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
Re: Issues holding us back from upgrading to 1.8.0
by Don Brown-5
::
Rate this Message:
On Fri, Jun 19, 2009 at 6:55 PM, Karl Pauls <karlpauls@...> wrote:
> > * Strange issue with WebLogic 9.2 - > > https://issues.apache.org/jira/browse/FELIX-1158 > > I just commented on the issue as well but please retry with the latest > version of felix (or even better, on trunk) as I think this should be > fixed already. Yep, this looks good. I didn't yet test it with WebLogic, but I looked through the code and it looks like it'll do the trick. > We are planning a bugfix release and will look into your issues and > whether we can port them back or not. I don't think FELIX-712 would > need to wait for 2.0 but I have to discuss this with richard first. > Please try to look into verifying the issues I commented on asap so > that we know what to include or not. Also, I uncommented the parent classloading code in ModuleImpl and my tests passed like expected. Looking through the comments, it says something about the code needing to be there because of how the system can export packages, which worries me a bit. All my unit tests passed, though, so maybe I'm misunderstanding the comment. If it is indeed necessary, maybe the fix can just be to not support loading resources from the parent classloader that way. The resources loading is actually the bug that is biting me in 1.8.0, as the classloading is more an annoyance. In summary, if we get some sort of resolution to FELIX-712 and a backporting of the memory leak fix, I'd be happy to upgrade to 1.8.1. I'm really looking forward to bundle fragments, as I keep hitting reasons to use them every day. Today's reason was to workaround the super annoying jaxp issues that have me doing ugly stuff like boot delegating weblogic.* and xerces. Would love to have a bundle fragment automatically attached to every bundle that has META-INF/services files and package imports to ensure the lookups happen cleanly. Thanks for the help! Don |
|
|
Re: Issues holding us back from upgrading to 1.8.0
by Karl Pauls
::
Rate this Message:
We won't make 1.8.1 but I can cut a 1.8.2 quickly if need be.
regards, Karl On Mon, Jun 22, 2009 at 11:53 AM, Don Brown<donald.brown@...> wrote: > On Fri, Jun 19, 2009 at 6:55 PM, Karl Pauls <karlpauls@...> wrote: > >> > * Strange issue with WebLogic 9.2 - >> > https://issues.apache.org/jira/browse/FELIX-1158 >> >> I just commented on the issue as well but please retry with the latest >> version of felix (or even better, on trunk) as I think this should be >> fixed already. > > > Yep, this looks good. I didn't yet test it with WebLogic, but I looked > through the code and it looks like it'll do the trick. > > >> We are planning a bugfix release and will look into your issues and >> whether we can port them back or not. I don't think FELIX-712 would >> need to wait for 2.0 but I have to discuss this with richard first. >> Please try to look into verifying the issues I commented on asap so >> that we know what to include or not. > > > Also, I uncommented the parent classloading code in ModuleImpl and my tests > passed like expected. Looking through the comments, it says something about > the code needing to be there because of how the system can export packages, > which worries me a bit. All my unit tests passed, though, so maybe I'm > misunderstanding the comment. If it is indeed necessary, maybe the fix can > just be to not support loading resources from the parent classloader that > way. The resources loading is actually the bug that is biting me in 1.8.0, > as the classloading is more an annoyance. > > In summary, if we get some sort of resolution to FELIX-712 and a backporting > of the memory leak fix, I'd be happy to upgrade to 1.8.1. I'm really > looking forward to bundle fragments, as I keep hitting reasons to use them > every day. Today's reason was to workaround the super annoying jaxp issues > that have me doing ugly stuff like boot delegating weblogic.* and xerces. > Would love to have a bundle fragment automatically attached to every bundle > that has META-INF/services files and package imports to ensure the lookups > happen cleanly. > > Thanks for the help! > > Don > -- Karl Pauls karlpauls@... --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
Re: Issues holding us back from upgrading to 1.8.0
by Richard S. Hall
::
Rate this Message:
Don,
On 6/19/09 3:55 AM, Don Brown wrote: > With a set of releases out the door, I set to look at upgrading our > (Atlassian) usage of felix from a forked 1.2.1 to 1.8.0. These seem > to be the issues remaining: > * Strange issue with WebLogic 9.2 - > https://issues.apache.org/jira/browse/FELIX-1158 > * Ability to disable "helpful" boot delegation - > https://issues.apache.org/jira/browse/FELIX-712 > I just found a bug that could be related...check the notes on the above issue, thanks! -> richard > * Memory leak when restarting Felix - > https://issues.apache.org/jira/browse/FELIX-1170 > * Occasional concurrency issue with the filter cache - > https://issues.apache.org/jira/browse/FELIX-765 > > FELIX-1170 was fixed, but only in trunk. Any chance I could get it > backported to 1.8? FELIX-765 was reported fixed, but I won't know > until we run it under load for a while. Yes, FELIX-1158 makes no > sense, but it is the only way we could get it working in WebLogic 9.2 > > Since FELIX-712, if accepted, would involve a new feature, am I right > in guessing I'll need to wait till Felix 2.0 to upgrade? The reason > it is more important now is the behavior seems to exist for resources > as well as classes, which will definitely cause issues for us. > > Don > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@... > For additional commands, e-mail: users-help@... > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
| Free embeddable forum powered by Nabble | Forum Help |
