I have just started learning Java and have so far had no problems compiling or running programs in a Windows OS at home. However, at work we use a Unix based OS. Whenever I try to run a program in the Unix environment that maintains an on-screen presence (such as a GUI) I keep getting the following notifications in the command prompt, even though the GUI window seems to be working as intended:
"WARNING: Could not create system preferences.directory.System preferences are unusable. java.util.prefs.FileSystemPreferences checkLockFile()ErrorCode"
Then a few seconds later I'll get a second message that says
"WARNING: Could not lock System prefs. Unix error code -263713896"
This second warning message will continue to spawn in the command window until I kill the GUI process that's running. Whatever the problem is it also seems to eat a lot of computing power as Unix said the process was using about 20% of the CPU before I killed it. The program I was running was the sample temperature conversion program from the Sun Java Tutorial website whose source code is at:
If you're using an Network File System (NFS) mounted resource, then bug 4673298 looks like a possibility. Is this bug description consistent with what you're seeing? (Click on the "related" bugs for more information.)
Also, this was reported against Java 1.4. What version are you running? (At the command prompt, type "java -version" without the quotation marks.) [ April 14, 2007: Message edited by: marc weber ]
"We're kind of on the level of crossword puzzle writers... And no one ever goes to them and gives them an award." ~Joe Strummer sscce.org
Which version of java are you using on the UNIX system?
I think there was a problem a while back with the java.util.(some preference stuff??) code where in case of some sort of failure (failure to lock a preferences file?) java didn't close the file. Thus, with every failure, a new open file was left on the unsuspecting system. This can hog resources pretty quickly!
As far as I know, UNIX error codes are fickle at best, and completely unreliable at worst. Seems all systems generate different error codes. So unless someone at your work knows what the number is referring to, you might have to resort to prayer :/
Best of luck (and keep us posted), Katrina [ April 14, 2007: Message edited by: Katrina Owen ]