This behaviour has not changed in the Witango 5.0.1.065 server. This is an info message which we added after being asked many times by many people how to tell when a db connection is established by the witango server. In previous versions the same events occurred without a notification.
It occurs when the witango server opens a new data source connection. The connection is then held open for DATASOURCELIFE minutes and shared with subsequent query requests to the same data source (matching DS name, DS type, username, password). This will not occur every time a data source is used to execute a query, only when the connection to a new data source is opened.
What you are seeing is normal when multiple connections are need to connect to the database. The Witango 5 Server does not share a connection with multiple simultaneously queries like T2K did. The Witango 5 Server uses one connection to the db per active query. i.e. if you have 5 active db requests hit the data source pool the witango server will open 5 connections to the db and run them all at the same time each with their own connection. The order in which the db returns the results is the order in which you will see the results returned to the witango server from the db. This order will differ between each dbms depending on how the dbms schedules the queries.
If the dba looks at the oracle connections it should see that there are 4 connections open.
Witango Support
On 22/07/2004, at 5:20 AM, MJPinckard wrote:
Fergal, et al,
I upgraded to 5.0.1.065 yesterday, and in my logs today it looks like the database connection isn't sticking. This is slowing my site down, since every request has to open a new db connection. I checked the witango.ini file and the settings between the old and new versions are the same (DATASOURCELIFE=30).
I'm seeing (I've replaced the db name and user name with X's, but they were correct before replacement):
Jul 21 11:26:16 HES3 WitangoServer[1572]: RUNTIME INFO No existing connection to the data source found, creating a new connection. DSN: oracle.XXXXXX; User: XXXXXX;
Jul 21 11:26:26 HES3 WitangoServer[1572]: RUNTIME INFO No existing connection to the data source found, creating a new connection. DSN: oracle.XXXXXX; User: XXXXXX;
Jul 21 11:26:26 HES3 WitangoServer[1572]: RUNTIME INFO No existing connection to the data source found, creating a new connection. DSN: oracle.XXXXXX; User: XXXXXX;
Jul 21 11:27:09 HES3 WitangoServer[1572]: RUNTIME INFO No existing connection to the data source found, creating a new connection. DSN: oracle.XXXXXX; User: XXXXXX;
This wasn't happening before the upgrade, any suggestions to correct.
Maggie
Fergal Donlon wrote:
...snip...Hi Maggie,
Firstly can I suggest you download the latest production version of the
Witango Server - 5.0.1.065. There were number of issues fixed between .062
and .065 and some did cause crashes.
_______________________________________________________________________ _
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
