Re: Issues holding us back from upgrading to 1.8.0

["Richard S. Hall" <he...@ungoverned.org>]

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@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
>    

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org