Can anyone help us?
We have an nw2004s portal and a mssql 2000 server containing some data. We have a couple of webdynpro's which get some data from mssql when they are called in an iview. The portal connects through jdbc with the mssql server. We are using dataservices and get the connection via jndi lookup. We are using connection pooling on Microsoft's driver.
We have made these settings in the datasource;
logintimeout: 2
initial connections: 4
maximum connections: 30
maximum time to wait for connection: 2
expiration: unchecked
sql engine: vendor sql.
We are trying to get the portal to gracefully degradate when the connection to this server is lost (pull the plug). What happens now is that it takes a really long time for the portal to find out that there is no more connection and everything comes to a grinding halt. When trying to stop the datasource, the visual admin hangs.
we are astounded that failure of the connection causes such a horrid application hang. Our question is: can we somehow fix this so that our portal resource manager quits after a predefined number of seconds (30 for instance).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.