Opened 19 years ago

Closed 19 years ago

#1056 closed defect (later)

Perl/Mapscript LayerObj->close() doesn't close connection

Reported by: ivano.picco@… Owned by: hobu
Priority: high Milestone:
Component: Input - Native SDE Support Version: unspecified
Severity: normal Keywords:
Cc:

Description

Hi!,
I try to use mapscript to get data from different ArcSDE layer using only one
layerObj and changing only data attribute (see also bug #1055):
[...CUT...]
#connection 1
$layer->close();
$layer->{data}="ctr.regione,SHAPE";
$layer->open();
#connection 2
[...CUT...]
Well, after close() connection from my perl script and SDE is still active, when
 I open the second connection SDE reports two connection that reach from the
same one script. The same thing using Oracle Spatial, so I think this is a bug
related mapscript  or mapserver C library.
Could you confirm this bug?
Thanks for your help,
Ivano Picco

Change History (3)

comment:1 by ivano.picco@…, 19 years ago

Ahem, sorry!, this is a connection pooling, isn't it?
But, why the second open() opens a new connection? 

comment:2 by sdlime, 19 years ago

Component: MapScriptInput - Native SDE Support
Owner: changed from sdlime to hobu@…
Howard, this may be a more general issue, but since SDE was mentioned
specifically I'm reassigning (for the moment) to that component.

There was connection pooling before all of the fast-cgi mods and so on. Is that
still in place or was it ripped out?

Steve

comment:3 by hobu, 19 years ago

Resolution: later
Status: newclosed
This is expected behavior.  Connection pooling will probably be exposed to
MapScript in a future release to deal with this situation
Note: See TracTickets for help on using tickets.