On Fri, Jun 19, 2009 at 9:55 AM, Don Brown<[email protected]> 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: [email protected]
> For additional commands, e-mail: [email protected]
>
>



-- 
Karl Pauls
[email protected]

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to