The server will start fine on its own, but will not start with the JSC. It claims to be starting but never actually does. I’ve tried starting with both the *YES and *ONLY parameters. I can even connect to the server controller with the Domino Console, but cannot manage to start the server…the controller job never spawns any tasks. I’ve included a screen shot of the log for the controller task. Not being particularly versed on the iSeries, I can’t infer much from the messages, other than that a particular attribute isn’t set somewhere. If anyone can shed some light on the situation, I’d certainly appreciate it.
I applied the 6.01CF1 update and was still unable to start with the server controller–is it just as simple as needing to apply a PTF?
Subject: Java Server Controller won’t start domino server
I don’t think the message you’re seeing in the CONTROLLER job log is affecting the startup of the Domino Server. I just verified this by creating a SystemDefault.properties file in /home/qnotes and then setting public access to *exclude and removing qnotes from the authorization list. My controller job log had the same error message as yours, but the server started up just fine. You might want to check the ACLs on SystemDefault.properties though if there’s JVM properties in there you want to use.
As to the server not starting, were there any other job logs generated for QNOTES? Like a QPRINT entry, instead of CONTROLLER? Is there a job log for the SERVER job itself or does it not get that far? I’m wondering if the SERVER job starts, but then exits due to some problem. The name of the job log file would be QJVAEXEC as that’s the name the OS/400 gives jobs that are started from java code.
One thing to check quick is the owner and authorities on the SERVER program in library QNOTES. It should be owned by qnotes.
Subject: RE: Java Server Controller won’t start domino server
Thanks for your suggestions. I checked the work log and it looks like QJVAEXEC never starts, much less ends abruptly. I also checked the ownership and all the programs are owned by QNOTES. I think the SystemDefault.properties file error message occurs because the file doesn’t exist…but your experiment shows that the server should start whether it can read the file or not.
We’re going to do an IPL tomorrow morning, so I’ll see if that has any effect. I know we haven’t done one since before we upgraded to R6 and installed a newer version of the JVM. I vaguely remember reading that this may need to be done to ensure all new libraries are actually loaded properly…or maybe I’m just grasping. In the meantime, the server runs fine without the controller so it’s not a major issue. If it persists, I’ll probably have to break down and call for product support.
Subject: RE: Java Server Controller won’t start domino server
If the SystemDefault.properties file doesn’t exist, you shouldn’t get a message about it. The file doesn’t need to be there.
One last thing to check is the ownership of LIBCNTRLR service program in the qnotes library. We had an issue with that being owned by QSYS, but if that’s the case, I don’t think the controller would even start.