I have a very similar configuration but cannot replicate. But even i am now really up to date and all works good, i had previously many problems of screen refresh. I was suspecting a hard charge or RAM allocation (i allocated the cache max) of FileMaker Server but not shure.
But my problems were not specific to Java. Anyways what about your RAM allocation ?
was reported somewhere here before. Java problem, when driving the server without monitor with a remote app'. Can't find the corresponding post
This issue has been reported in the Technet forum in a number of discussions. https://fmdev.filemaker.com/message/108575#108575
My experience has been that if I connect a monitor to the server, I can connect to the server using screen share and Java displays everything. If the monitor is removed, Java can't display anything. This includes the Java app that is installed in the System Preferences.
This leads me to believe that it is really a Java issue. I have reported it to Oracle and had it accepted as a bug quite a while ago, Bug ID 9000009. They sent me link to track the bug, but it always comes up as not found. My guess is it will take pressure from someone much bigger then me to get Oracle to really look into the issue and fix it.
Java was originally developed by Sun and up through Snow Leopard, Apple distributed Java for the Macs. Under that setup, I think there was better quality control and more response when issues came up. There were still issues...
I'm hoping the FMI and maybe Apple can put some pressure on Oracle to address this.
Or maybe FileMaker should stop trying to use Java as the code base for their console app? It just hasn't been stable enough for such a "mission critical" application.
Please note that i agree the fact that using Java for FMS Admin Console is painful for us AND certainly for FMI too. As a Mac user, who is generally very demanding in terms of coherence, interface etc... i HATE Java. So, of course, it is only my opinion...
But to be accurate, i must precise that my Mac mini server never had a monitor connected on it.
Concerning Java bugs, sure, they must be billions, but concerning this precise case, it is not so easy to establish.
I have two Mac Mini servers. One runs Snow Leopard and Java 6. A side from some issues with Java under Snow Leopard it runs perfectly. The other runs Lion Server, and FMS 12.0v3. With Java 7 I get only blank screens. I have a client with a server under the same OS. Again Java doesn't display any information. Unfortunatly there are a lot of us out there that can't use the FMS console due to this bug.
It appears that the latest Java updates disable Java 6 if you have kept it running so you can use the Console. I have a client that had this happen and I have not found a way to re-enable Java 6. Although with all of the security issues, I'm not sure about doing that. The catch is he needs a functional FMS console. So I don't know what to do.
First, one question : are theses problems occuring exclusively when you are using the FMS Admin Console from the hosting machine ? If true, why using this way ? Generally it is more comfortable to use from a desktop computer. I think that is my better suggestion. But …
It seems you have right : Java 7 disable Java 6. So both may never work together. If i understand correctly (excuse my poor english) you think that Java v7 is clearly incriminated on your issue.
I have a client that had this happen and I have not found a way to re-enable Java 6
If you want to try it, and if you have not installed FMS 12.0.4 yet, you can apply theses processes : http://support.apple.com/kb/HT5559
Maybe you can also uninstall 12.0v4 and reinstall 12.0v3 server but it is a lot of work and potentially critical. If true, uninstall with actual software then install from your original copy and, if prior, apply the 12.0v3 update : http://help.filemaker.com/app/answers/detail/a_id/11287/kw/java%207 .See also :
Good luck Bruce !
why using this way ?
I'm not hosting with this version, but I find it VERY convenient to use Console from the host machine--I use Remote Desktop Access to access the server machine and then launch the console. This is convenient because I frequently need to do other management tasks on the machine not part of the Console's scope such as choosing when to apply an OS update or other "houskeeping".
So this way, I don't have to switch back and forth, I can do it all within one RDP session.
Ok, ok, i maybe sayed that because my server is a Mac and it doesn't need many maintenance. At contrary, i must use the FMS Console many times to update my database etc... Moreover, i am generally performing the developer's job and not the IT job's.
To be honnest, i don't know why it doesn't work on Bruce and others systems, even they seem very similar to mine.
Anyways, thank you for your answer. If you have other suggestions, you are welcome !
I suppose you don't answer me about memory allocation because no relevant ?
I thinked about more questions :
• What about your Monitor Preferences on Menu ? Because if resolution is too small, it also could create problems. For instance, you click on an item and then, another is selected (!). I recommend 1280x1024 minimum. Option Scaled ON.
• Do you use a VMWare system or something like this ?
• What is doing your servers except FileMaker service ?
Let us know…
You are correct, the memory allocation in FMS is not relavent to the Java issue. We are you 1280 X 1024. The FMS server has only one function, FMS. It is doing a fine job as an FMS server.
We have found that leaving a monitor connected to the server seems to resolve the issue. So it looks like we will do that.
AFAIK when the problem was reported earlier, it was nailed down to a java issue. Has nothing to do with the virtualisation-SW nor with user settings.
After the last few updates, it seems to be solved - at least here.
I've had one issue on one machine (OSX10.8.3) where I couldn't activate the latest java-7 because of an older java version that could not be removed, apparently. I've found an old java-6 control panel (google'd for that, was on an Apple support page) that let me remove it. After that, the latest java version became available. Was kind of strange - but worked. I'm not sure if it's related to Your problem