Removing extensions

[mark]

Lucee 5, 

I know someone else already asked this but how do you remove an extension completely?

After uninstalling extensions it still loads all the jars in lucee-server directory, tomcat temp directory

and in the felix cache, does tomcat still scan these jars causing more memory consumption?

Also wanted to point out that what used to be a 75 mb install bloats up to about 320 mb with felix cache

and tomcat temp...etc. 

Lucee 5 with osgi is hardly feeling like it has a lower memory footprint and improved performance

but that could be my lack of tomcat/java knowledge.

cfhttp cachedWithin does not seem to work yet and I assume the newest Postgres jdbc still has issues,

other than that is there a Lucee 5 without extensions installed?

thanks,

Mark.

[Michael Offner]

Tomcat should NEVER load the jars inside "/lucee-server/bundles", to avoid this we have moved the "lucee-server" directory out of the lib folder. So if Tomcat is loading this jars you need to change the classpath defintion to avoid this at any coast!

We even plan to make a warning in the admin overview page if this is happening.

Lucee normally should remove all jars used by an extension and no other extension is using when uninstalled, BUT if this jars are also loaded by tomcat it is possible (specially under windows) that Lucee is not able to remove this jars because they are blocked by tomcat.

Jars inside "/lucee-server/bundles" are loaded only on demand, so if the core and no extension is using them, they are not loaded, you can see which jars are loaded in the admin under info/bundles.

can you raise a ticket about cfhttp-cachedwithin, we will check.

we plan the possibility to customize a lucee bundle online, but like i said in a proper installation uninstalling an extension should be no problem, but we will run some tests. what OS are you using?

Micha

--
Love Lucee? Become a supporter and be part of the Lucee project today! - http://lucee.org/supporters/become-a-supporter.html
---
You received this message because you are subscribed to the Google Groups "Lucee" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lucee+un...@googlegroups.com.
To post to this group, send email to lu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/c87e2991-472c-4cf6-91a8-775761152acb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Michael Offner]

completely forget to answer the question about postgres.

We had problems with newer version of the postgres driver, because it contains some OSGi functionality that is specific to Karaf OSGi and breaks with Felix OSGi. so we decided to go back to an older version (8.3.0.jdbc4) and no longer provide the newer versions.

We have testcases in place that runs with every commit that are testing postgres:

https://github.com/lucee/Lucee/blob/master/test/datasource/PostgreSQL.cfc

https://github.com/lucee/Lucee/blob/master/test/jira/Jira2903.cfc

So postgres is working, otherwise we never could do a build.

So the question is, what version do you have in place and what exactly fails with postgres?Micha

Micha

On Fri, May 27, 2016 at 3:51 AM, mark <mgr...@gmail.com> wrote:

[Michael Offner]

FYI:

https://luceeserver.atlassian.net/browse/LDEV-859

On Fri, May 27, 2016 at 3:51 AM, mark <mgr...@gmail.com> wrote: