AppServer Startup

[ConvertFromOldNGs]

by Michael Hill >> Wed, 15 Aug 2007 21:07:57 GMT

Morning,

In the last couple of days we have had two of our clients have the same problem where last week they were running fine. There have been no changes to the servers.

The problem is that AppServer (Database and App Servers are running as services) is taking more that 30 seconds to start up and timing out. This (service timeout) has now been changed to 2 minutes and it looks just the same and times out.

Does anyone have any idea what might be going on, or what we need to look at.

Cheers

Michael

[ConvertFromOldNGs]

by BeeJay >> Thu, 16 Aug 2007 0:33:56 GMT

Are you using sharedMemory or TcpIp for your connection to the DbServer?

I've had sites in the past where starting up a TcpIp connection resulted in their system having their modem dial-up an internet connection, resulting in a very long startup time - due to problems with their DNS and router rules.

Changing over to sharedMemory instead of TcpIp for the AppServer to DbServer connection prevented the long startups and also had the added benefit of improved performance.

If you're currently using TcpIp perhaps try changing over to sharedMemory for your AppServer to DbServer connections and see if that helps.

Cheers,
BeeJay.

[ConvertFromOldNGs]

by BeeJay >> Thu, 16 Aug 2007 1:13:29 GMT

I meant to say if you have other connections into your DbServer, such as ODBC or server side applications running as Jade.exe fat clients, then you'll still need to have a TcpIp connection available as well as a sharedMemory connection in your DbServer.

Cheers,
BeeJay.

[torrie]

Hi

We've encountered this issue on a site. Windows reports in the event log that it cannot start up the application server but there appears to be no entries in the jommsg log to say that it's started.

Did you manage to resolve the issue?

Thanks

Torrie

[swishy]

Hi

We've encountered this issue on a site. Windows reports in the event log that it cannot start up the application server but there appears to be no entries in the jommsg log to say that it's started.

Did you manage to resolve the issue?

Thanks

Torrie

Hi torrie,

This would more likely indicate an issue around permissions, jade service account issue, or potentially c++ redist installation problem, can you provide any more info regarding whether this is an existing installation that just stopped working or a fresh installation, is the app server being launched as a windows service etc?

Cheers
Dale.

[torrie]

I don't believe that this is related to permissions, C++ redistribution etc. Once the server has booted, the app server service can be started manually. It's just when the server boots that we have the issue.

The database server and the application server are both configured as services and the application server depends on the database server.

Thanks

Torrie

[BeeJay]

I've had issues in the past where even with the dependency setup at the service definition level the AppServer can be started just a little bit to soon after the DbServer is started. I have solved this by marking the AppServer service(s) as non-auto-start and having another non-gui server application that issues the necessary NET START commands and then immediately terminates. This allows for the situation where a restart recovery is required, or the DbServer service takes a little longer than expected to startup.

Cheers,
BeeJay.

[ghosttie]

Yeah, I agree with BeeJay - I think the App Server's starting before the DB server has got all the way up

I think in recent versions of Windows you can set a service to start late - maybe someone has some experience with this?

[torrie]

Thanks, we'll give the non gui app a try.

Unfortunately we are running on Windows Server 2003 and I believe that the last start features came in with Vista.

Torrie

[swishy]

Thanks, we'll give the non gui app a try.

Unfortunately we are running on Windows Server 2003 and I believe that the last start features came in with Vista.

Torrie

You could at a pinch set a dependency on windows messenging service or similar that starts near the end of the service startup sequence. ( if it is enabled of course )

Dale.