If you have a question that you want a response from Sybase, please open a
technical support case. Remember that the newsgroups are an user community
not a communication channel to Sybase.
"Grant Spencer" <firstname.lastname@example.org> wrote in message
> Sybase, can you please respond to my earlier posting. Your documentation
> advises against our solution, but does not explain the potential
> We are using Jaguar 3.6.1 ESD 3 (Build 36112) and PB 7.0.3 build 10108,
> using Oracle 8.1.6 database and OCI.
> Earlier post follows...
> We have/had a problem in the disconnect event of an NVO which was deployed
> on Jaguar. The component uses instance Datastores - a frowned-upon action
> for said versions - but we are reluctant to change as the code will be
> replaced within the next 6 months with Java EJBs. Our problem is thus:
> When the auto-demarcate component has finished its processing, it logs a
> message to srv.log, then should return a blob to the client. Instead, we
> the following message in srv.log, and the client never receives the
> to its request:
> Oct 03 11:11:02 2002: OCI8: Exec Stmt Error: -2
> Oct 03 11:11:02 2002: OCI8: Get Server Attr Error: -2
> From the Oracle (8.1.6) documentation, it seems to be using an invalid
> handle - possibly statement handle, but any of 3, it a call to
> This should - guessing here - return a valid statement handle which is
> used in OCIAttrGet.
> This problem is intermittent - if one component is instantiated, it runs
> fine, but it will often fail on the last instance of the component when 2
> more are active at the same time.
> Our component properties are:
> Concurrency = TRUE
> Bind Object = FALSE
> Bind Thread = TRUE
> Pooling = FALSE
> Sharing = FALSE
> and the transaction attributes are set to "Not Supported"
> If we set Bind Object = TRUE (other properties unchanged), then our
> disappears. However the Jaguar documentation states "Applies to stateful
> components only (Automatic Demarcation/Deactivation must be disabled on
> Transactions tab or the component must be a stateful session EJB)." for
> Please can someone give a hint as to the cause and possible solution to
> problem, and/or explain the negative implications of setting the Bind
> property to TRUE for an auto-demarcate component.