Java Server Problem

Question

I am using Secure Global Desktop Enterprise Edition (4.0) on Fedora Core 3
Linux.
Sometime, the system shows the following error message when I click the
application.
Starting...
Locating session...
Couldn't start application. Please inform an Administrator.
Error code: 17
Details: javax.naming.NoPermissionException [Root exception is
java.lang.SecurityException: Cannot list directory.]
I had checked the Server log and I found the error message in
jserver20936_error.log as follow:
2005/07/31 04:51:03.756     (pid 20936)     audit/license/error     #1122756663756
Tarantella Secure Global Desktop Enterprise Edition (4.0) ERROR:
An exception occurred writing to the file
/opt/tarantella/var/info/licenseuse/namestamp
java.io.FileNotFoundException:
/opt/tarantella/var/info/licenseuse/new.namestamp (Too many open files)
     at java.io.RandomAccessFile.open(Native Method)
     at java.io.RandomAccessFile.<init>(RandomAccessFile.java:204)
     at com.sco.tta.server.license.LicenseFile.newFile(LicenseFile.java:362)
     at
com.sco.tta.server.license.UsagePersister.writeUsageToDisk(UsagePersister.java:642)
     at
com.sco.tta.server.license.UsagePersister$1.run(UsagePersister.java:851)
     at java.lang.Thread.run(Thread.java:534)
The information written to this file will be invalid. This may cause
more licenses to be consumed than should be.
Check there is enough free disk space, and that the file exists.
If the file does not exist, restart the server.
2005/07/31 04:52:05.929     (pid 20936)     server/server/error     #1122756725929
Tarantella Secure Global Desktop Enterprise Edition (4.0) ERROR:
A server socket accepting connections has encountered an unexpected error.
The Exception was: java.net.SocketException: Too many open files
     at java.net.PlainSocketImpl.socketAccept(Native Method)
     at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:353)
     at java.net.ServerSocket.implAccept(ServerSocket.java:448)
     at
com.sco.cid.net.BufferedServerSocket.accept(BufferedServerSocket.java:37)
     at com.sco.cid.net.MultiServerSocket.accept(MultiServerSocket.java:265)
     at com.sco.tta.server.server.ServerTask.runTask(ServerTask.java:396)
     at com.sco.tta.server.server.Task.run(Task.java:122)
     at com.sco.cid.common.WorkerPool$Worker.run(WorkerPool.java:524)
     at java.lang.Thread.run(Thread.java:534)
The server will attempt to create a new socket to handle new connections.
If this happens frequently it may indicate a problem with resources on the
server.
2005/08/01 08:19:11.491     (pid 20936)     server/server/fatalerror     #1122855551496
Tarantella Secure Global Desktop Enterprise Edition (4.0) FATAL ERROR:
JServer error: java.lang.NoClassDefFoundError:
com/sco/tta/common/jndi/auth/ResourceMapper
     at com.sco.tta.server.glue.BaseCtx.setExtendedError(BaseCtx.java:109)
     at
com.sco.tta.server.glue.SearchAsadOp.handleResults(SearchAsadOp.java:518)
     at
com.sco.tta.server.glue.SearchAsadOp.doDownSearch(SearchAsadOp.java:273)
     at com.sco.tta.server.glue.SearchAsadOp.search(SearchAsadOp.java:130)
     at com.sco.tta.server.glue.AsadOpHandler.search(AsadOpHandler.java:212)
     at
com.sco.tta.server.server.asad.AsadCalcTask.search(AsadCalcTask.java:910)
     at
com.sco.tta.server.server.asad.AsadCalcTask.processEnvelope(AsadCalcTask.java:198)
     at com.sco.tta.server.server.CalcTask.runTask(CalcTask.java:125)
     at com.sco.tta.server.server.Task.run(Task.java:122)
     at com.sco.cid.common.WorkerPool$Worker.run(WorkerPool.java:524)
     at java.lang.Thread.run(Thread.java:534)
There may be a problem with the JVM.
The server will exit.
Check the logs for more information.
What happen? How could I fix the error?

Answer 1

Dear Barrie,
I am using Fedora Core 3 Linux.
The Tarantella Secure Global Desktop Enterprise Edition(4.0) have 20
concurrent user license.
Normally, about 10 users would access the application through Secure
Global Desktop Enterprise Edition.
Could I use the license of Tarantella EE 4 to upgrade to Tarantella EE 4.1
PW Ng
barrie wrote:
Hi Ng
Sorry, I forgot to ask whether you are using Solaris or Linux? I don't
think Solaris has an upper limit for this value but I'm less sure about
Linux. I would make sure all tta processes have been terminated and try
again.
My feeling is that you shouldn't really be using 4096 files in a single
process -- not unless you're system is very very large. In 4.0 there is
a problem with the 1.5 JVM holding on to references that keep files open for
longer than is necessary and potentially leads to a loss of service by
keeping too many files open. 4.1 has a fix for this. I think there is a
good chance this may be your problem aswell.
Barrie
On 2005-08-09, Ng Ping Wah <[email protected]> wrote:
Dear Barrie,
When i set the file descriptor to 8192 and restart the server, I found the
error log has follow error message:
2005/08/09 08:13:46.265     (pid 31540)     pem/circuit     #24
Tarantella Secure Global Desktop Enterprise Edition(4.0) ERROR:
An error occurred reading on circuit fdcircuit. Reason: (9) Bad file
descriptor.
The current operation has failed.
If persistent, restart the server.
2005/08/09 08:13:46.266     (pid 31540)     pem/circuit     #26
Tarantella Secure Global Desktop Enterprise Edition (4.0) FATAL ERROR:
The program has encountered an error that means it cannot continue.
It will now exit. A technical description is given below to help
establish the cause.
Error/EOF on file descriptor circuit. Killing PE Manager.
Services unavailable.
Restart the server.
Is the value '8192' too large ?
What is the Suitable value ?
best regards
PW Ng
barrie wrote:
Hi Ng,
Yes, you've run out of files. But, this ulimit thing is already done by
the SGD EE start up files. What you can do is edit the tuning properties
of the server in ArrayManager. By default, this should be 4096 but you
can try increasing this here. You may also change the value of
rlim_fd_max in /etc/system on Solaris, although the value given in the
arraymanager should override the setting in /etc/system.
It's unusual to use this many files, you may be seeing a file descriptor
leak that was in 4.0 and may be causing this problem, the problem is
subtle and doesn't necessarily effect all users. I recommend you upgrade
to 4.1 though.
Regards
Barrie
On 2005-08-04, Rob <[email protected]> wrote:
PW Ng wrote:
I am using Secure Global Desktop Enterprise Edition (4.0) on Fedora
Core 3
Linux.
Sometime, the system shows the following error message when I click the
application.
Starting...
Locating session...
Couldn't start application. Please inform an Administrator.
Error code: 17
Details: javax.naming.NoPermissionException [Root exception is
java.lang.SecurityException: Cannot list directory.]
I had checked the Server log and I found the error message in
jserver20936_error.log as follow:
2005/07/31 04:51:03.756     (pid 20936)     audit/license/error     #1122756663756
Tarantella Secure Global Desktop Enterprise Edition (4.0) ERROR:
An exception occurred writing to the file
/opt/tarantella/var/info/licenseuse/namestamp
java.io.FileNotFoundException:
/opt/tarantella/var/info/licenseuse/new.namestamp (Too many open files)[snip]
I think the "Too many open files" may give you a clue.
Try by editing the SGD EE startup files (either under /etc/init.d or in
the /opt/tarantella/bin/scripts folder) and adding the
     ulimit -n 4096
statement. Of course, 4096 is just an example; find your "maximum number
of open file descriptors" limit and raise it accordingly.
Best,
Rob