Skip to main content
B
bmuzzy
Participating Frequently
June 13, 2013
Question

java update 1.7.0_21 deleted jrunsvc.exe. what replaces it?

  • June 13, 2013
  • 1 reply
  • 4838 views

I have CF 9.0.0.0 and tried to update from java 1.6.0_14 to java 1.7.0_21 at the request of my security department.  CF 9 Application Server used to run with "C:\ColdFusion9\runtime\bin\jrunsvc.exe" but now there's no jrunsvc.exe on the system.  What replaced jrunsvc.exe or was the error mine in trying to update java?

thanks,

Bob

    This topic has been closed for replies.

    1 reply

    Carl Von Stetten
    Carl Von Stetten
    Legend
    June 13, 2013

    Updating the Java JDK should not have any effect on stuff in C:\ColdFusion9\runtime\bin, unless you have done some manual replacement of the files.  The safest way to upgrade the JVM from the version delivered with ColdFusion to another version is to install the JDK in a separate directory from ColdFusion (usually in C:\Program Files\Java or C:\Program Files (x86)\Java depending on whether you are running a 32-bit or 64-bit version and the OS version), then update the JVM path settings in ColdFusion administrator to point to the newer JDK.  Alternatively, you can edit manually edit the JVM path in the jvm.config file buried in C:\ColdFusion9\ (can't remember exactly where, and I'm on CF10 now so I can't check it easily).

    If you deleted the JVM from inside the ColdFusion directory and replaced it with the Java 7 one, you may be out of luck unless you can restore the folder structure from a backup or the Recycle Bin.  Otherwise, you may have to reinstall ColdFusion and then configure it as I outlined above.

    -Carl V.

    Charlie Arehart
    Community Expert
    Charlie ArehartCommunity Expert
    Community Expert
    June 13, 2013

    In addition to Carl’s sage observations, I’ll note as well, Bob, that unless you have applied 9.0 CHF3, then your CF 9.0 deployment does not formally support Java 1.7. It might work, but some things might not. (Still, as Carl said, just updating the JVM should not affect the operations of files like jrunsvc.) To get the CHF, see http://helpx.adobe.com/coldfusion/kb/cumulative-hotfix-3-coldfusion-900.html.

    As for your seeming problem with jrunsvc, I’m curious what you mean. You say, that CF “used to run with "C:\ColdFusion9\runtime\bin\jrunsvc.exe" but now there's no jrunsvc.exe on the system”.

    So are you saying that when you try to start the CF service, it doesn’t stop, but gives an error saying that the jrunsvc does not exist? To be clear, the service runs that jrunsvc, and that in turns starts the instance, so that we see jrun.exe listed as the running process for CF9 and earlier. Assuming you’re running CF Standard or the Enterprise Server edition, you’ll find If you look in the services panel that the properties for the CF service show it listed as trying to execute C:\ColdFusion9\runtime\bin\jrunsvc.exe. If you’re running an Enterprise Multiserver deployment, the location for the service executable is C:\JRun4\bin\jrunsvc.exe.

    Are you saying you see the CF service pointing to one of those files, but you don’t find the file to exist?

    /charlie

    /Charlie (troubleshooter, carehart. org)
    B
    bmuzzyAuthor
    Participating Frequently
    June 14, 2013

    Bob, there could be any number of things amiss, given what you’ve said in your past 4 messages today. I’ll try to share what I can based on them.

    First, you said in one of them that you are running on 32-bit Windows 2003, and that you got the 32-bit JVM. Fair enough. But had you installed also a 32-bit version of CF? I suppose so, since you say that you had it running. But the errors you’re getting seem to suggest you are having some conflict like that. But maybe that’s not the issue.

    Second, to go back to your first note today, your mistake then was installing the JDK into the CF directory. As Carl said yesterday, the solution is to put it elsewhere, and then point CF to it. But I see in your second note you reverted your VM and did it that way the second time.

    Then in your 3rd note today, you refer to there being “4 jvm.cfg files”, and I realize that’s because one of the errors refers to it, but that’s not what CF uses to hold the JVM config files. Rather, it’s jvm.config. In your case, specifically c:\coldfusion9\runtime\bin\jvm.config.

    But then you say that in your second note today, when you said “I edited jvm.config to read:  java.home=C:\\Program Files\\java\\jdk1.7.0_21\\jre”.

    Indeed, when you make the changes you do to change the JVM location, do edit that jvm.config, rather than use the CF Admin, because if CF can’t come up, then you can’t see the admin any more to see if you made a mistake, or to correct it. Instead, one should edit that file directly, as you did.

    But then finally, in your last note today, you report that you get an error:

    Error Loading: C:/java/jdk1.7.0_21/jre\bin\server\jvm.dll

    So that’s yet another location. Are you saying you reinstalled it, this time not in  C:\Program Files\java\jdk1.7.0_21\jre as you mentioned earlier today, but now in C:\java\jdk1.7.0_21\jre? Note the missing “Program Files” the 2nd time. And can you confirm that the files are there, as you did with the earlier path?

    Finally, assuming that is the path, you would in fact want (in the jvm.config java.home line) to point to that path not as the windows path, C:\java\jdk1.7.0_21\jre, but rather with the “java way” of referring to that path, which would be either C:/java/jdk1.7.0_21/jre or c:\\java\\jdk1.7.0_21\\jre (or add in the Program Files, if needed).

    Hopefully this will sort you out. I also share some tips on this, and point to other resources with still more, in a blog entry that was written when we were told in 2011 that we could update the JVM in CF 8 and 9 to 1.6.0_24:

    http://www.carehart.org/blog/client/index.cfm/2011/10/28/CF911-Have-you-updated-your-ColdFusion-JVM-to-24-yet-Important-security-fix-for-CF-89

    That info would still apply with your attempt to update to 1.7 (given that you have added the CHF 3). That said, while you say you “very carefully installed“ it, still it’s easy to make a mistake, which could be contributing to your problems. I did a blog entry also that year on that problem and some tips to avoid mistakes:

    http://www.carehart.org/blog/client/index.cfm/2011/10/21/why_chfs_may_break

    Hope all that helps. If things still don’t work, we may be able to help you with back and forth, but if it becomes time-sensitive for you, it may be better to enlist the help of someone to assist you remotely and online. I do that sort or work, as do some others. See cf411.com/cfconsult for a list of alternatives.

    /charlie


    First, thanks to all of you for your help.

    Charlie, I reverted to a previous snapshot of the VM several times that had

    a working CF9 w/ Java 1.6, and reinstalled the JDK each time, and re-edited

    jvm.config appropriately each time. The only reason I mentioned jvm.cfg

    was because I saw the error ""Error: no known VMs. (check for corrupt

    jvm.cfg file)" referencing it in coldfusion-out.log.

    I'll take a look at your links, including that for the consultant. Thanks

    again, all!

    On Thu, Jun 13, 2013 at 7:19 PM, Charlie Arehart

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices