Difference in use of connection pools from one server to another

Question

Hi all
we are running wl5.1 with sp9 against SQLServer 2000
On our performance test server (2 CPU) which has weblogic & sqlserver runnig
on it we run out out of connection pools when running a specific method,
having looked at it we noticed that it contained nested sql, so that each
client would actually hang onto multiple connections until finished. The
total number of connections used seemed approximately the same as the number
of SQL statements.
However we then ran the weblogic server on a different machine against the
same database, so it was now running over a network and everything worked ok
and the total number of client connections was just 1.
Can anyone shed any light onto this, I have a few ideas but nothing to back
them up as follows:
Multi CPU versus single CPU
Local connection rather than network connection between WLServer and
DBServer
WL Configuration
DBServer configuration
Is nested SQL valid ?
Any help much appreciated Paul Taylor
(An example of what I mean by nested sql is shown below, method1() creates
instances of class2 and calls c2.method which contains sql before releasing
its connection.)
class c1
public void method1()
try
rs=executesql(sqlString)
while rs.next()
new c2();
c2.method2()
finally
closeConnection()
class c2
public void method2()
try
rs=executesql(sqlString)
finally
closeConnection()

Answer 1

because when you are dealing with a remote server, your calls will be
serialized over one socket. and the connection is assigned to that socket
probably...or something like that...or not...shouldn't be important :)
Filip
~
Namaste - I bow to the divine in you
~
Filip Hanik
Software Architect
[email protected]
www.filip.net
"Paul taylor" <[email protected]> wrote in message
news:[email protected]...
The code has now been changed, but the real point was why are two server
dealing with the same code in a different way
"Filip Hanik" <[email protected]> wrote in message
news:[email protected]...
Any help much appreciated Paul Taylor
(An example of what I mean by nested sql is shown below, method1()creates
instances of class2 and calls c2.method which contains sql beforereleasing
its connection.)well this is obviously not a good way of doing it. you know that you are
obtaining multiple connections so why not code your software in a
smarter
way.
pass the connection object into c1 and c2 that way they both use thesame
connection. Or release in between.
Filip
~
Namaste - I bow to the divine in you
~
Filip Hanik
Software Architect
[email protected]
www.filip.net
<l> wrote in message news:[email protected]...
Hi all
we are running wl5.1 with sp9 against SQLServer 2000
On our performance test server (2 CPU) which has weblogic & sqlserverrunnig
on it we run out out of connection pools when running a specific
method,
having looked at it we noticed that it contained nested sql, so thateach
client would actually hang onto multiple connections until finished.
The
total number of connections used seemed approximately the same as thenumber
of SQL statements.
However we then ran the weblogic server on a different machine against
the
same database, so it was now running over a network and everythingworked
ok
and the total number of client connections was just 1.
Can anyone shed any light onto this, I have a few ideas but nothing
to
back
them up as follows:
Multi CPU versus single CPU
Local connection rather than network connection between WLServer and
DBServer
WL Configuration
DBServer configuration
Is nested SQL valid ?
Any help much appreciated Paul Taylor
(An example of what I mean by nested sql is shown below, method1()
creates
instances of class2 and calls c2.method which contains sql beforereleasing
its connection.)
class c1
public void method1()
try
rs=executesql(sqlString)
while rs.next()
new c2();
c2.method2()
finally
closeConnection()
class c2
public void method2()
try
rs=executesql(sqlString)
finally
closeConnection()