Storable in a mixed environment

Hi,

I am running Interchange 5.4.1 in LVS cluster with the
session files  
stored on NFS mounted partitions. I recently added a couple
of 64-bit  
real servers to the cluster. I am now receiving "Byte
order is not  
compatible" errors from Storable. The existing hosts
are all 32-bit  
systems.

Any general strategies for dealing with this? I'm not
married to  
Storable. I've just always used it without much thought.

Bill Carr
Bottlenose - Wine & Spirits eBusiness Specialists
http://www.bottlenose-
wine.com

_______________________________________________
interchange-users mailing list
interchange-usersicdevgroup.org
http://www.icdevgroup.org/mailman/listinfo/interchan
ge-users

On Wed, 11 Apr 2007, Bill Carr wrote:

> I am running Interchange 5.4.1 in LVS cluster with the
session files 
> stored on NFS mounted partitions. I recently added a
couple of 64-bit 
> real servers to the cluster. I am now receiving
"Byte order is not 
> compatible" errors from Storable. The existing
hosts are all 32-bit 
> systems.
>
> Any general strategies for dealing with this? I'm not
married to 
> Storable. I've just always used it without much
thought.

I always make sure all app servers in a cluster are using
the same 
architecture; running 32-bit Perl on 64-bit operating
systems works well 
and avoids these kind of interoperability problems until you
migrate to 
64-bit only.

Jon

-- 
Jon Jensen
End Point Corporation
http://www.endpoint.com/

_______________________________________________
interchange-users mailing list
interchange-usersicdevgroup.org
http://www.icdevgroup.org/mailman/listinfo/interchan
ge-users

Quoting Jon Jensen (jonendpoint.com):
> On Wed, 11 Apr 2007, Bill Carr wrote:
> 
> >I am running Interchange 5.4.1 in LVS cluster with
the session files 
> >stored on NFS mounted partitions. I recently added
a couple of 64-bit 
> >real servers to the cluster. I am now receiving
"Byte order is not 
> >compatible" errors from Storable. The existing
hosts are all 32-bit 
> >systems.
> >
> >Any general strategies for dealing with this? I'm
not married to 
> >Storable. I've just always used it without much
thought.
> 
> I always make sure all app servers in a cluster are
using the same 
> architecture; running 32-bit Perl on 64-bit operating
systems works well 
> and avoids these kind of interoperability problems
until you migrate to 
> 64-bit only.

If this is not an option, you can also just move to
Data:umper.
It
gives up about 30-50% more CPU in session creation, but
otherwise
shouldn't be too much of a drag.

Using it can be as easy as removing the _session_storable
file in your
interchange root -- and removing all your old session files,
of course.

-- 
Mike Heins
Perusion -- Expert Interchange Consulting    http://www.perusion.com/

phone +1.765.647.1295  tollfree 800-949-1889 <mikeperusion.com>

I am convinced that life is 10% what happens to me and 90%
how I react to it. And so it is for you... we are in charge
of our attitudes. -- Charles Swindoll
_______________________________________________
interchange-users mailing list
interchange-usersicdevgroup.org
http://www.icdevgroup.org/mailman/listinfo/interchan
ge-users

On Apr 11, 2007, at 10:37 AM, Mike Heins wrote:

> Quoting Jon Jensen (jonendpoint.com):
>> On Wed, 11 Apr 2007, Bill Carr wrote:
>>
>>> I am running Interchange 5.4.1 in LVS cluster
with the session files
>>> stored on NFS mounted partitions. I recently
added a couple of 64- 
>>> bit
>>> real servers to the cluster. I am now receiving
"Byte order is not
>>> compatible" errors from Storable. The
existing hosts are all 32-bit
>>> systems.
>>>
>>> Any general strategies for dealing with this?
I'm not married to
>>> Storable. I've just always used it without much
thought.
>>
>> I always make sure all app servers in a cluster are
using the same
>> architecture; running 32-bit Perl on 64-bit
operating systems  
>> works well
>> and avoids these kind of interoperability problems
until you  
>> migrate to
>> 64-bit only.
>
> If this is not an option, you can also just move to
Data:umper.
It
> gives up about 30-50% more CPU in session creation, but
otherwise
> shouldn't be too much of a drag.
>
> Using it can be as easy as removing the
_session_storable file in your
> interchange root -- and removing all your old session
files, of  
> course.
Thanks for the help. I removed the _session_storable and
wrote a  
script to convert the sessions with shopping carts to
Data:umper. 

It's working fine.

Bill Carr
Bottlenose - Wine & Spirits eBusiness Specialists
(877) 857-6700
http://www.bottlenose-
wine.com

_______________________________________________
interchange-users mailing list
interchange-usersicdevgroup.org
http://www.icdevgroup.org/mailman/listinfo/interchan
ge-users