Upgrading to Java 7u65 breaks my Deployment Rule Set for Oracle applications
- by Don Atreides
My company uses an older version of an Oracle application that requires Java 6u45. Naturally we want to be secure, so we use a Deployment Rule Set to specify 6u45 for that internal application and let other applications use 7u60. Now that we're ready to upgrade the Java 7 half to 7u67, the Oracle application breaks with "Deployment Rule Set required version 1.6.0_45 not available." Of course it is available, it just can't find it for some reason. As a test, I specified that JavaTester.org should use 6u45 also and it works fine with no issues. But when I try to use the same configuration (7u67 and 6u45) against the Oracle application it fails every time. If I downgrade to 7u60, it works. 7u65 or higher, it breaks. The Oracle application hasn't changed so it must be something different in how 7u65+ is handling Deployment Rule Sets or pathing or something. I'm at a complete loss.
ruleset.xml:
<?xml version="1.0"?>
-<ruleset version="1.0+">
-<rule>
<id location="*.mycorp.com"/>
<action version="1.6.0_45" permission="run"/>
</rule>
-<rule>
<id location="http://javatester.org"/>
<action version="1.6.0_45" permission="run"/>
</rule>
</ruleset>