[Glass] a InternalError occurred (error 2261), The object with object ID 20 is corrupt. Reason: 'process switch not in critial state'
Locked
12
12
Re: [Glass] a InternalError occurred (error 2261), The object with object ID 20 is corrupt. Reason: 'process switch not in critial state'
 
|
From: "John McIntosh" <[hidden email]>It was just a guess:) Anyway, I'm curious why the upgrade script is loading GLASS 1.0-beta.8.7.3? The default version of GLASS in the BootstrapApplicationLoadSpecs is 1.0-beta.9: UserGlobals at: #BootstrapApplicationLoadSpecs ifAbsent: [. UserGlobals. at: #BootstrapApplicationLoadSpecs. put: { {'ConfigurationOfGLASS'. '1.0-beta.9'. #('default'). BootstrapRepositoryDirectory. }. }. and your script is loading 1.0-beta.8.7.3. Did you set BootstrapApplicationLoadSpecs? If so, what does it look like? It is not required that you upgrade to GLASS 1.0-beta.9 before the upgrade, however, it is prudent to ensure that your application will function correctly on GLASS 1.0-beta.9. In fact it is prudent to load and test your application in any new version of GemStone just to ensure that none of the bugfixes negatively impact your application... At the moment the upgradeSeasideImage is designed to allow you to tell the system which versions of projects to load and which cache repository to use based on decisions that you've made after doing testing and validation of your application on the target version of GemStone. I think that there are way too many variables in the upgrade process to expect that an automated script can make all the right decisions without feedback from the developer:) We expect you to have created a disk-based repository (BootstrapRepositoryDirectory or the repository slot in the BootstrapApplicationLoadSpecs) with all of your required packages for the express purpose of avoiding network during an upgrade ...
_______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
|
|
8.7.3? Yes because I did this setup via http://gemstonesoup.wordpress.com/2012/09/21/gemstones-3-1-0-1-is-shipping UserGlobals at: #BootstrapApplicationLoadSpecs put: { { 'ConfigurationOfGLASS'. '1.0-beta.8.7.3'. #('default'). BootstrapRepositoryDirectory. } . { 'ConfigurationOfSeaside30'. '3.0.7.1'. #('default'). '/opt/gemstone/product/seaside/monticello/repository'. } . }. After carefully confirming yes my production system is using the above configuration versions. If I had loaded 1.0-beta-9 into my production system then I would have coded up different values based on what MC said I had loaded into production. Still I see you are doing the UserGlobal>at:ifAbsent: check on BootstrapApplicationLoadSpecs in the updateSeasideImage, so I don't need to in future mess
with a custom one, unless I've a need for other MC packages to be loaded? As for> "We expect you to have created a disk-based repository" I'm not sure if anyone directly answered if GsPackageLibrary getMonticelloRepositoryDirectory could be the seaside cache repository?
On Wed, Aug 21, 2013 at 12:05 PM, Dale K. Henrichs <[hidden email]> wrote:
=========================================================================== John M. McIntosh <[hidden email]> Corporate Smalltalk Consulting Ltd. Twitter: squeaker68882 =========================================================================== _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Re: [Glass] a InternalError occurred (error 2261), The object with object ID 20 is corrupt. Reason: 'process switch not in critial state'
|
|
From: "John McIntosh" <[hidden email]>Okay. This explains the source of GLASS 1.0-beta.8.7.3 and the source of the error about the missing package: the monticello repository (BootstrapRepositoryDirectory) shipped with the 3.1.0.4 release does not include the package versions for earlier versions of GLASS. So you probably should port you application to GLASS 1.0-beta.9 before attempting to upgrade to 3.1.0.5 (when it becomes available). To do that I would recommend that you load your application code into a fresh 3.10.4 seaside extent and verify that your app runs correctly there. If no application changes are required, then you can change the upgrade script to load GLASS 1.0-beta.9. Now I notice that you don't seem to have included instructions for reloading your application code in your upgrade script. You need to do that as well... Well, I would think that you will always need to specify the configurations for your application code and dependent projects ... you must include the GLASS configuration first, then the list of configurations that are needed for your application I would think that it is cleaner to keep your application packages separate from the set of packages shipped with GemStone/S ... with that said, you certainly could use `GsPackageLibrary getMonticelloRepositoryDirectory` as the cache repository...
_______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
«
Return to GLASS
|
1 view|%1 views
| Free forum by Nabble | Edit this page |