We currently have a machine in our environment that's running Server 2003 with IBM websphere installed. We recently found that when rebooting the server, the websphere services "spin" for about 30 mins and never actually start (they are set to automatic). This ultimately requires someone to go in and cycle the service manually, at which point they come up fine. We've looked at the WAS logs, ran procmon against Java, etc and can't come up with a cause.
I know there A LOT of variables that can come into play here, but I was just wondering if you guys might know anything in general that might be causing this /where I can concentrate troubleshooting?