AR #22365 - 7.1.2 EDK - SDK will not start on 32- and 64-bit linux OSs

All Recent Answers

Search Answers Database

7.1.2 EDK - SDK will not start on 32- and 64-bit linux OSs

AR#	22365
Part	EDK-SDK
Last Modified	2007-04-17 00:00:00.0
Status	Archive
Keywords	SDK, sdk_xps, launch, linux, java, ioexception, lock, locks, runtime, eclipse

Description

Keywords: SDK, sdk_xps, launch, linux, java, ioexception, lock, locks, runtime, eclipse

General Description: Attempting to launch SDK from the command line via 'xps_sdk' on an NFS-mounted drive fails with the message:

Caused by: java.io.IOException: An error occurred while locking file "/home/hoochie_mamma/EDK_SDK_workspace/.config/org.eclipse.core.runtime/.manager/.fileTableLock": "No locks available". A probable reason is that the file system or Runtime Environment does not support file locking. You may want to choose a different location, or disable file locking (using the osgi.locking property), but this can cause data corruption. at org.eclipse.core.runtime.adaptor.Locker_JavaNio.lock(Locker_JavaNio.java:42).

Solution 1

1. When xps_sdk starts up, it displays the complete launch command. Please copy this and append any additional vmargs. This can be written to a script and executed in subsequent launches.

For example:
-vmargs -Dorg.eclipse.core.runtime.ignoreLockFile

Solution 2

Create a $XILINX_EDK/eclipse/bin/lin/configuration/config.ini file and add the following line to it:

osgi.locking = java.io

Other options are:

osgi.locking = none
osgi.locking = java.nio

Solution 3

This problem has been fixed in the latest EDK 8.1i Service Pack available at:
<http://www.xilinx.com/xlnx/xil_sw_updates_home.jsp>
The first service pack containing the fix is EDK 8.1i Service Pack 1.