Making application live HELP!

[Carl Howarth]

Sorry to repost, but I am fairly desparate to get this issue resolved!

Please see below, when it hangs if I leave it long enough I get a 'General
Network Error', or something similar. Could this be down to the web servers
being on the DMZ, or perhaps some configuration value in the web.config
file?

Any help would really be appreciated as I am due to put the system live
ASAP.

Many thanks, Carl Howarth


Hi,

We have developed a system using VS.NET 2003 in ASP.NET (vb). The system
runs absolutely fine on my own and my colleague's machine. We are running
Win XP Pro. We have 2 web servers, each of which have been upgraded to .net
1.1, and have all the latest updates from windows update.

When we deploy the application to either web server the performance is
ridiculous (the servers run asp3 systems fine). Sometimes the system will
work like a dream, moving from page to page in an instant, others it will
just hang when a link is selected (even to pages that are not accessing our
database). It's nothing to do with connections being left open and it's
bizarre how the issues are completely unpredictable. The systems are
transferred simply by copying the contents of the web site folder on our
machines to the web site folder on the server(s).

Has anybody come across this kind of situation and if so, please please let
me know how to get around it!

Thanks very much,

Carl Howarth
(e-mail address removed)

 

[Carl Howarth]

Hi Gregory,

Thanks for coming back to me. I am at a loss with this but will run some
checks as you have suggested. The network issue really is confusing,
certainly since the 'classic' asp applications that we are running do not
experience this problem at all.

Whilst testing, I have noticed that if I log into the system and jump
between pages at frequent intervals it seems to work perfectly. It seems
that if I leave a page displayed for any length of time then choose another
lin k that is when the system freezes up - I don't know if that gives you
any further clues. I have altered the web.config file to say debug="false",
which has made no difference and have checked the code and I certainly
believe that all objects used are being destroyed after use.

Another clue that may help is that part of the system is 'upgraded' classic
asp, ie we have simply converted the existing asp pages and got rid of the
'set' commands, used isdbnull instead of isnull, and have set aspcompat
accordingly (only on converted pages), I cannot see this as being an issue
due to the fact that these all work wonderfully on my machine.

If you have any other ideas (or not!) in relation to this please let me
know.

Many thanks again, Carl

 

[Carl Howarth]

Eric,

The connections in the current activity show as 'sleeping', which suggests
to me that the connections have been closed.

I am using a component to access the database, based on the following:
Public ReadOnly Property ConnectionString()

Get

ConnectionString = "Data Source=10.200.20.2; Initial Catalog=ClientCAS;User
ID=sa;Password=password; Network Library=dbmssocn;"

End Get

End Property


Public Function GetReader(ByVal strSQL As String) As SqlDataReader

Dim tmpConn As New SqlConnection(Me.ConnectionString)

Dim objCmd As New SqlCommand(strSQL, tmpConn)

objCmd.Connection.Open()



objCmd.CommandTimeout = 300

GetReader = objCmd.ExecuteReader(CommandBehavior.CloseConnection)

objCmd = Nothing



End Function


And then within my pages' back end code I would do something along these
lines to fill, say, a datagrid:

dim obj as new cpData
dim dr as sqldatareader = obj.GetReader("spStoredProc " & id)
dg.datasource = dr
dg.databind
dr.close
dr = nothing
obj = nothing

Does this all look acceptable to you? It certainly works fine on the
development machine!

Many thanks, Carl