Daylight Savings Time patches failing

[rich.leach]

Hi All-

We're having some challenges when attempting to apply the DST patches to our
system. Our plan was to apply the CF 7.0.2 updater first (we need it now
anyway since we're running with some Flex functionality) and then apply the JVM
update as suggested in a recently posted Adobe.com Technote. We're also running
JRUN4.0 version 106363, and serving our pages with Apache (httpd-2.0.52-19.ent)

After applying the CF 7.0.2 Updater to our existing CF installation (CF7.0.1
Enterprise, RedHat Linux AS release 4 (Nahant Update 2) 2.6.9-22.ELsmp) Java
Version 1.4.2_05, when we try to access any ColdFusion page we get the
following error. Has anyone else experienced similar issues? How did you
resolve them? We've verified that the web server is working as we can call
..htm, .css pages, etc. but none of the .CFM pages work:

500

java.lang.NullPointerException
at
coldfusion.runtime.TemplateClassLoader.newInstance (TemplateClassLoader.java:393)
at
coldfusion.runtime.TemplateClassLoader.newInstance (TemplateClassLoader.java:374)
at
coldfusion.runtime.TemplateProxyFactory.resolveNam e(TemplateProxyFactory.java:11
9)
at
coldfusion.runtime.TemplateProxyFactory.resolveNam e(TemplateProxyFactory.java:25
1)
at
coldfusion.runtime.TemplateProxyFactory.resolveNam e(TemplateProxyFactory.java:23
5)
at
coldfusion.runtime.TemplateProxyFactory.resolveNam e(TemplateProxyFactory.java:10
0)
at
coldfusion.runtime.TemplateProxyFactory.resolveNam e(TemplateProxyFactory.java:94
)
at
coldfusion.runtime.TemplateProxyFactory.resolveNam e(TemplateProxyFactory.java:62
7)
at coldfusion.runtime.CFPage.createObject(CFPage.java :5704)
at coldfusion.runtime.CFPage.CreateObject(CFPage.java :5673)
at coldfusion.runtime.CFPage.CreateObject(CFPage.java :5638)
at
cfApplication2ecfm1144146628.runPage(C:\blackstone _updates\cfusion\wwwroot\CFIDE
\administrator\Application.cfm:113)
at coldfusion.runtime.CfJspPage.invoke(CfJspPage.java :152)
at coldfusion.tagext.lang.IncludeTag.doStartTag(Inclu deTag.java:349)
at coldfusion.filter.CfincludeFilter.invoke(Cfinclude Filter.java:65)
at coldfusion.filter.CfincludeFilter.include(Cfinclud eFilter.java:33)
at coldfusion.filter.ApplicationFilter.invoke(Applica tionFilter.java:172)
at coldfusion.filter.RequestMonitorFilter.invoke(Requ estMonitorFilter.java:51)
at coldfusion.filter.PathFilter.invoke(PathFilter.jav a:86)
at coldfusion.filter.ExceptionFilter.invoke(Exception Filter.java:69)
at coldfusion.filter.BrowserDebugFilter.invoke(Browse rDebugFilter.java:52)
at
coldfusion.filter.ClientScopePersistenceFilter.inv oke(ClientScopePersistenceFilt
er.java:28)
at coldfusion.filter.BrowserFilter.invoke(BrowserFilt er.java:38)
at coldfusion.filter.GlobalsFilter.invoke(GlobalsFilt er.java:38)
at coldfusion.filter.DatasourceFilter.invoke(Datasour ceFilter.java:22)
at
coldfusion.filter.RequestThrottleFilter.invoke(Req uestThrottleFilter.java:115)
at coldfusion.CfmServlet.service(CfmServlet.java:107)
at coldfusion.bootstrap.BootstrapServlet.service(Boot strapServlet.java:78)
at jrun.servlet.ServletInvoker.invoke(ServletInvoker. java:91)
at jrun.servlet.JRunInvokerChain.invokeNext(JRunInvok erChain.java:42)
at jrun.servlet.JRunRequestDispatcher.invoke(JRunRequ estDispatcher.java:259)
at jrun.servlet.ServletEngineService.dispatch(Servlet EngineService.java:541)
at
jrun.servlet.jrpp.JRunProxyService.invokeRunnable( JRunProxyService.java:204)
at
jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRu nnable(ThreadPool.java:428)
at jrunx.scheduler.WorkerThread.run(WorkerThread.java :66)


ColdFusion Info:

System Information
Server Details
Server Product ColdFusion MX
Version 7,0,1,116466
Edition Enterprise
Serial Number CED700-54662-XXXXX-XXXXX
Operating System UNIX
OS Version 2.6.9-22.ELsmp
JVM Details
Java Version 1.4.2_05
Java Vendor Sun Microsystems Inc.
Java Vendor URL [url]http://java.sun.com/[/url]
Java Home /var/opt/jrun4/jre
Java File Encoding ASCII
Java Default Locale en_US
File Separator /
Path Separator :
Line Separator Chr(10)
User Name cfusion
User Home /home/cfusion
User Dir /var/opt/jrun4/bin
Java VM Specification Version 1.0
Java VM Specification Vendor Sun Microsystems Inc.
Java VM Specification Name Java Virtual Machine Specification
Java VM Version 1.4.2_05-b04
Java VM Vendor Sun Microsystems Inc.
Java VM Name Java HotSpot(TM) Server VM
Java Specification Version 1.4
Java Specification Vendor Sun Microsystems Inc.
Java Specification Name Java Platform API Specification
Java Class Version 48.0

Java Class Path info available upon request - it's rather lengthy!

[QuietObserver]

I believe that your java version needs to be update to at le 1.4.2_11 or higher. We had a similar issue on our servers and updating to the latest java version fixed this...

[Snickher]

I've attempted this already. The updater has it's own JVM update build inside
of it. Upgrading the JVM according to the DST docs yeilds the same end-result,
null pointer when trying to get to the CF Administrator.

TOm

[QuietObserver]

I also used the updater, however it didn't update the java source to above 1.4.2__11.

Yours displays: Java Version 1.4.2_05

I had to do this manually myself, inorder to get it to work!

[QuietObserver]

Here is the KB article from Adobe...
[url]http://www.adobe.com/cfusion/knowledgebase/index.cfm?id=d2ab4470[/url]

I hope this helps.

[Snickher]

The 1.4.2_05 is the 7.0.1 JVM. After installing the patch, it's upgraded to
1.4.2_09-b05.

I'm pretty sure I remember replacing this with the other JVM (1.4.2_11), and
had the same result, but i can try again just to be sure.

Also...

after trying this the first time, I mucked things up and didn't back up the
dir. I tried to install the base version, and the 7.0.1 updater, and have
exactly the same problem as the 7.0.2 updater! i had to copy from another web
server.

Tom

[rich.leach]

I think it would prudent to start asking around if anyone knows of any
contingency plans; alternatives to this DST patch and/or Updater 7.0.2
patch.... unless someone from Adobe can step up and advise us on what else we
could try we'll need to deal with at least DST on our own, and if the Updater
7.0.2 patch contains required functionality that we can't simply work without,
we may be forced down a different road, even a different technology.

Is anyone planning to NOT install the DST patch (for whatever reason(s)), and
if so, how are you mitigating the potential negative results?

Does anyone know where Adobe has listed all (or as much that they'll let be
known) of the enhancements/changes/updates that the 7.0.2 effects? I'm pretty
sure it was required for Flash/Flex integration, which we were planning on
using, but without some clarity we may be rethinking this part of our
initiative.....

Many thanks in advance,

Rich

[Ronsweb]

Rich,

Did you get it to work? I just tried to install the DST patch on one of our
6.1 servers and it did not work. I had
to reinstall a backup of the jvm.config file to get it working again. What
worries me is that I have to update 4 coldfusion servers.
One CFMX 7.02 multiserver, One CFMX 7.02 Server, and two CFMX 6.1 Servers.

[rich.leach]

No, we're actually putting on all of the latest patches for the OS as of this
posting, then we'll go ahead and try to apply the CF 7.0.2 patch and the DST
patch for the JVM.... will post when we have results....

Rich

[Brad]

In my test environment (Fedora Core 6/ CF 7.02) it failed badly. I'm
wondering if we are going to be able to apply this to our production
environments (RH ES4/CF 7.02). I know one other state agency that says they
just aren't going to apply the patch.

"rich.leach" <webforumsuser@macromedia.com> wrote in message
news:eskbl4$c4i$1@forums.macromedia.com...
No, we're actually putting on all of the latest patches for the OS as of
this
posting, then we'll go ahead and try to apply the CF 7.0.2 patch and the DST
patch for the JVM.... will post when we have results....

Rich

[LinuxInductee]

Additionally, two things need to be copied ...

1. First, I installed 1.4.2_11 in new directory, so I have a \jrun4\jre
\ and \jrun\jre.1.4.2_11\ folders.
2. Next I made backups of \bin\jvm.config and \bin\wsconfig_jvm.config
3. Then updated the java.home variable in each of the above config
files to use the new JRE folder
4. Next, I copied:
\JRun4\jre\bin\server\*.* to \JRun4\jre.1.4.2_11\bin\server
and
\JRun4\jre\lib\charsets.jar to \JRun4\jre.1.4.2_11\lib
5. Stop and Start the CFusion service and it should come online.

[rich.leach]

..... we finally got the patches to work.... with no thanks to Adobe, which I'll
go into in a minute....

We discovered (the hard way, numerous attempt failures) that evidently, 2
different 7.0.2 patches exist; one that simply applies the 7.0.2 code
differences to the 7.0.1 existing code base, and a second code base that is a
full version install that applies the 7.0.2 at install time. We couldn't find
anything anywhere that spoke to the differences of getting to 7.0.2 by either
either means; the docs all suggested that you'd have the same end result if you
went with the patches or if you went with the brand new install. This is not
the case, as the 7.0.1 to 7.0.2 patches simply did not work.

I ended up reaching out to Adobe and opened a Customer Service Case (number
#200175243 in case anyone from Adobe ever reads this) on 3/7/2007. The
automated response I received said "...You can expect a response within 1
business day. ...." By 3/9/2007 we were getting anxious as we still had not
heard back from Adobe, so I called, got into the que for support, and after 14
minutes on hold was told it would cost $499 for an engineer to help, since my
manager was out of town and we didn't have access to support contract info.
Now, we've got at least half a dozen CF licenses in house, and with no mention
of $499 anywhere in the Customer Service Case information I felt like we were
baited by Adobe. As of this forum posting, I still have not heard back from
Adobe on this case.

It's rather difficult to be an outspoken evangelist (I even got certified in
CF) for a company's product when they pull the ol' bait and switch for
something they should support in the first place. At best, post and reveal
upfront that your patches aren't tested, may not work and you'll get charged
for support when you need it from Adobe. And remove the "... response within 1
business day...." from your communications as it's unprofessional to mislead
your customers.

Rich

[LinuxInductee]

I'm finding that level of poor support across the spectrum, not just
Adobe. One could start a blog about how 'the customer is no longer
central' in any business. It's just getting ugly.

BTW, I had installed 7.0.2 on a test server but quickly decided to
skip that one. Apparently it's full of bugs, even in innocuous tags
like cflocation, which simply quit working.

On the other hand, 7.0.1 has been running flawlessly for us. Perhaps
you could evaluate that version on a test server and determine it's
viability for your apps.

The DST patch installation instructions did omit the \servers\ folder
and charsets.jar, which seems like whomever created the instructions
did not ever perform the task. On the other hand, we have a multi-
server configuration, using JRun, which has never been clearly
documented, except by Bob Purcell himself. The single server
installation always gets the full attention and clarity.

Good luck,
Len