Did you start this ‘as administrator’ ?
Logged in as local admin (and running on 2003), so no "as administrator" option.
This is usually because of :
1. Permissions issue on the cache packages directory - you have rules out this case already
2. Make sure Cache packages directory is not readonly by any means
3. Try setting python cache dir by incudling -Dpython.cachedir="path to alternate directory" in the jython.bat file.
I already checked these 3 points. Bear in mind all other packages cache without a problem - it's only the vim25-1.0.jar that's causing issues.
What version of Jython is this ?
What is the size of this jar vim25-1.0.jar ?
There was a bug in Jython fixed in 2.5.2 b1
This is it vim25.jar is one of the "offending jars"
May be the case.
You may choose to ignore these.
I have not experienced any problems after ignoring caching errors in Jython
I beleive this is an optimization.
I'll discuss this with my client - thanks. My only concern is that we're working with the Jython version that ships with BladeLogic...!
Also, the error you're pointing to appears to relate to JAR's over 64k - this one is 6,408k, but is by no means the biggest.
Also, FYI, if you use Jython for extended objects and you experience one of these cache errors, the whole XO fails with an error dialog!
1 of 1 people found this helpful
Try to raise a Support Ticket with BMC
Forward them the Jython bug you are facing.
I think people will get this as this jar is related to Vmware vsphere is a part of BladeLogic stdlib and it will be hit by many people.
And then You can get official advise from BMC support to upgrade your Jython.
From my expeirience I dont see any problem if you upgrade your Jython version.
This jar is one of the jars reported in the bug report. I think it has to do with the lenghth of utf strings greater than 64K and not the size.
You were right - upgrading Jython to 2.5.2 fixed the issue!