One of the reason I can image (yet I didn't see it in practice) is
when you use object-by-reference on server side. In this case instead
of returning REAL DBI::st object (it can't be properly serialized
because of tied elements and database handlers) SOAP::Lite returns
small stub that has ID of object on server side, so when you send is
back server will access teh real object. This stub is blessed into
the real class (DBI::st in this case) and if use have 'use DBI' on
client side THEN perl will try to call a destructor for your object,
which is not a real object in terms of DBI structure and destructor
How to solve this? Do NOT do 'use DBI' if possible. If you do have
logic in your client that require to work with real DBI handler and
fake handler returned by SOAP client there is not much you can do
except ignoring this message. Again, that's how I understand the
situation, but I didn't have it in practice and might be wrong in my
explanation. Hope it helps.
Best wishes, Paul.
--- Nate Mueller <nmueller@...
> Any of you know the solution?
> -------- Original Message --------
> Subject: Re: Error with SOAP::Lite
> Date: Sat, 30 Jun 2001 09:44:27 -0500 (CDT)
> From: Dave Rolsky <autarch@...>
> To: Nate Mueller <nmueller@...>
> CC: <dbi-users@...>
> On Fri, 29 Jun 2001, Nate Mueller wrote:
> > (in cleanup) dbih_getcom handle 'DBI::st=HASH(0x880e950)' is not
> a DBI
> > handle (has no magic)
> This happens when a DBI handle is serialized (or if you try to use
> previously valid DBI handle after a fork). SOAP is somehow
> your handle. There is a way to make it not do that but I forgot
> what it
> To unsubscribe from this group, send an email to:
> Your use of Yahoo! Groups is subject to
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail