4 ms·

As indicated in the article it's not still "out to get you" since it was fixed in March 2011. From the bug report: Submit Date: 2010-12-22 Resolved Date: 2011-

As indicated in the article it's not still "out to get you" since it was fixed in March 2011. From the bug report: Submit Date: 2010-12-22 Resolved Date: 2011-03-10 That's less than 3 months.

jtymes 14y ago
>Luckily the new patches to Java 7 no longer have this problem. But as the different statistics show – vast majority of the applications out there have not migrated to Java 7 as we speak. So most often than not, your application at hand has got the very same problem waiting to surface. It's a tad misleading, but it's "still out there waiting to bite you" because of Java 6 still being widely used.
- thebluesky 14y ago
  JDK 6 is EOL 2 months from now: https://blogs.oracle.com/henrik/entry/java_6_eol_h_h https://blogs.oracle.com/henrik/entry/java_6_eol_h_h It's also pretty rare for folks to use that http client. It's normally the case that an apache commons or netty http client is used.
  - smackfu 14y ago
    We'll see if that EOL actually happens. It's pretty irresponsible to discontinue security updates for a version that is used by half of your customers (even if you don't want them to use it anymore.) Very similar to Microsoft and XP support.
ivom2gi 14y ago
As we speak, then according to this http://zeroturnaround.com/labs/devprod-report-redux-java-versions-thoughts-for-2013-with-martijn-verburg/ http://zeroturnaround.com/labs/devprod-report-redux-java-ver... Java 7 only has up to 20% of market share. This means that most of the apps out there are still affected ...
sgt 14y ago
I'm using 1.6 for development purposes (I will change to JDK 7 very shortly, but it hasn't been possible until now for other reasons), and I am literally plagued by the PermGen problem every single day, perhaps up to 3 times an hour. Increasing PermGen space is not a solution, as it only means that - yes, it'll take longer for PermGen space to run out, but the Application Server (e.g. Glassfish) will become incredibly slow before it breaks.
- brown9-2 14y ago
  Are you doing lots of redeploys? Can you alter your workflow to just restart the server process instead?
  - sgt 14y ago
    Yes, doing a lot of redeploys. Restarting the server process takes a bit too long. E.g. if I have 50 EJB's and 20-30 JAX-RS type web services, it does take the application about 15-20 seconds to load each time. Sometimes even longer. So incremental redeploys are really great, as it usually takes 2-3 seconds instead.

As indicated in the article it's not still "out to get you" since it was fixed in March 2011. From the bug report: Submit Date: 2010-12-22 Resolved Date: 2011-03-10 That's less than 3 months.

jtymes 14y ago

>Luckily the new patches to Java 7 no longer have this problem. But as the different statistics show – vast majority of the applications out there have not migrated to Java 7 as we speak. So most often than not, your application at hand has got the very same problem waiting to surface. It's a tad misleading, but it's "still out there waiting to bite you" because of Java 6 still being widely used.

thebluesky 14y ago
JDK 6 is EOL 2 months from now: https://blogs.oracle.com/henrik/entry/java_6_eol_h_h https://blogs.oracle.com/henrik/entry/java_6_eol_h_h It's also pretty rare for folks to use that http client. It's normally the case that an apache commons or netty http client is used.
- smackfu 14y ago
  We'll see if that EOL actually happens. It's pretty irresponsible to discontinue security updates for a version that is used by half of your customers (even if you don't want them to use it anymore.) Very similar to Microsoft and XP support.

ivom2gi 14y ago

As we speak, then according to this http://zeroturnaround.com/labs/devprod-report-redux-java-versions-thoughts-for-2013-with-martijn-verburg/ http://zeroturnaround.com/labs/devprod-report-redux-java-ver... Java 7 only has up to 20% of market share. This means that most of the apps out there are still affected ...

sgt 14y ago

I'm using 1.6 for development purposes (I will change to JDK 7 very shortly, but it hasn't been possible until now for other reasons), and I am literally plagued by the PermGen problem every single day, perhaps up to 3 times an hour. Increasing PermGen space is not a solution, as it only means that - yes, it'll take longer for PermGen space to run out, but the Application Server (e.g. Glassfish) will become incredibly slow before it breaks.

brown9-2 14y ago
Are you doing lots of redeploys? Can you alter your workflow to just restart the server process instead?
- sgt 14y ago
  Yes, doing a lot of redeploys. Restarting the server process takes a bit too long. E.g. if I have 50 EJB's and 20-30 JAX-RS type web services, it does take the application about 15-20 seconds to load each time. Sometimes even longer. So incremental redeploys are really great, as it usually takes 2-3 seconds instead.