Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Marshalling error on a method never called

2 posts in General Discussion (old) Last posting was on 2000-03-31 01:17:38.0Z
Brian P. Surratt Posted on 2000-03-31 00:28:28.0Z
Newsgroups: sybase.public.easerver
From: "Brian P. Surratt" <brian.surratt@bigfoot.com>
Subject: Marshalling error on a method never called
Date: Thu, 30 Mar 2000 19:28:28 -0500
Lines: 44
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2314.1300
X-Mimeole: Produced By Microsoft MimeOLE V5.00.2314.1300
NNTP-Posting-Host: surratt88.ft89.upmc.edu 128.147.89.88
Message-ID: <347_EOlC4jqm$GA.307@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:25162
Article PK: 154261

After making a component call, I receive the following error in the srv.log

SystemException: MARSHAL
(fax_interface/monitoring_services/get_interface_data -
mylogin@nnn.nnn.nnn.nnn)

where
fax_interface is the package
monitoring_services is the component
get_interface_data is the function

What has me confused is that the method reported in the log is not the
method that is called when the error occurs. The method I'm calling
completes processing successfully and when it returns control to client
application, the marshalling error occurs.

The offending method is never called. Other methods on the monitoring
component are being called, but the get_interface_data method is not. This
component is written in PB,

The IDL for the offending is as follows:

short get_interface_data
(
inout ::fax_interface::interface_monitoring interface_data
)
raises (::CTS::PBUserException);

and the fax_interface::interface_monitoring is a struct made up of
approximately 20 attributes all being short and MJD::TimeStamp types.

In the PB object that implements the component, the struct is an instance
variable that is passed back in the reference argument:

interface_data = istr_interface_monitoring

I added debug code to this function and redeployed the component. After
stopping and start jaguar just for good luck, I walked through my entire
business process and the marshalling still occured. However, the debug
code never showed up in my log.

To summariaze, I'm stumped. Any ideas on where to look next....


Brian P. Surratt Posted on 2000-03-31 01:17:38.0Z
Newsgroups: sybase.public.easerver
From: "Brian P. Surratt" <brian.surratt@bigfoot.com>
Subject: Re: Marshalling error on a method never called
Date: Thu, 30 Mar 2000 20:17:38 -0500
Lines: 60
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2314.1300
X-Mimeole: Produced By Microsoft MimeOLE V5.00.2314.1300
NNTP-Posting-Host: surratt88.ft89.upmc.edu 128.147.89.88
Message-ID: <347_GVZqX$qm$GA.307@forums.sybase.com>
References: <347_EOlC4jqm$GA.307@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:25160
Article PK: 154259

Some more oddness..... I started poking around in some of the other
functions on the offending component, specifically the methods that are
being called during the process I'm working on.

The function I'm working on makes an intercomponent call to the monitoring
component, but the method I'm calling never gets executed. The activate
event completes, but the method itself never fires.

Don't know if this helps or just makes things worse....

Brian P. Surratt <brian.surratt@bigfoot.com> wrote in message
news:EOlC4jqm$GA.307@forums.sybase.com...
> After making a component call, I receive the following error in the
srv.log
>
> SystemException: MARSHAL
> (fax_interface/monitoring_services/get_interface_data -
> mylogin@nnn.nnn.nnn.nnn)
>
> where
> fax_interface is the package
> monitoring_services is the component
> get_interface_data is the function
>
> What has me confused is that the method reported in the log is not the
> method that is called when the error occurs. The method I'm calling
> completes processing successfully and when it returns control to client
> application, the marshalling error occurs.
>
> The offending method is never called. Other methods on the monitoring
> component are being called, but the get_interface_data method is not.
This
> component is written in PB,
>
> The IDL for the offending is as follows:
>
> short get_interface_data
> (
> inout ::fax_interface::interface_monitoring interface_data
> )
> raises (::CTS::PBUserException);
>
> and the fax_interface::interface_monitoring is a struct made up of
> approximately 20 attributes all being short and MJD::TimeStamp types.
>
> In the PB object that implements the component, the struct is an instance
> variable that is passed back in the reference argument:
>
> interface_data = istr_interface_monitoring
>
> I added debug code to this function and redeployed the component. After
> stopping and start jaguar just for good luck, I walked through my entire
> business process and the marshalling still occured. However, the debug
> code never showed up in my log.
>
> To summariaze, I'm stumped. Any ideas on where to look next....
>
>