Author Archives: Admin - Page 2

Eclipse internal Error – .fileTableLock access is denied

Error / Problem:
Eclipse internal Error – .fileTableLock access is denied

Stack Trace/Error Log:

!ENTRY org.eclipse.osgi 4 0 2013-08-21 15:00:19.904
!MESSAGE Error reading configuration: C:\Apps\IBM\SDP70\configuration\org.eclipse.osgi\.manager\.fileTableLock (Access is denied.)
!STACK 0 C:\Apps\IBM\SDP70\configuration\org.eclipse.osgi\.manager\.fileTableLock (Access is denied.)
at Method)
at<init>(Unknown Source)
at org.eclipse.core.runtime.internal.adaptor.Locker_JavaNio.lock(Unknown Source)
at org.eclipse.osgi.storagemanager.StorageManager.lock(Unknown Source)
at Source)
at org.eclipse.osgi.internal.baseadaptor.BaseStorage.initFileManager(Unknown Source)
at org.eclipse.osgi.internal.baseadaptor.BaseStorage.initialize(Unknown Source)
at org.eclipse.osgi.baseadaptor.BaseAdaptor.initializeStorage(Unknown Source)
at org.eclipse.osgi.framework.internal.core.Framework.initialize(Unknown Source)
at org.eclipse.osgi.framework.internal.core.Framework.<init>(Unknown Source)
at org.eclipse.osgi.framework.internal.core.OSGi.createFramework(Unknown Source)
at org.eclipse.osgi.framework.internal.core.OSGi.<init>(Unknown Source)
at org.eclipse.core.runtime.adaptor.EclipseStarter.startup(Unknown Source)
at Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.core.launcher.Main.invokeFramework(Unknown Source)
at org.eclipse.core.launcher.Main.basicRun(Unknown Source)
at Source)
at org.eclipse.core.launcher.Main.main(Unknown Source)

Solution: I solved this problem by modifying the parent directory “SDP70″ permissions, to allow all users read/write access.

Also, I found the below useful link on the IBM Support


Smell my Code. Code smell ? What’s code smell?

Code smell is any symptom in the source code of a program that possibly indicates a deeper problem. It is the process of identifying bad software program and altering in such a way that it does not alter the external behavior of the code, yet improves its internal structure. Code smell can even take a bad design and rework it into a good one.

Some common Coding smells:

  1. Duplicated code: identical or very similar code exists in more than one location.Long method: a method, function, or procedure that has grown too large.
  2. Large class: a class that has grown too large. See God object.
  3. Too many parameters: a long list of parameters in a procedure or function make readability and code quality worse.
  4. Feature envy: a class that uses methods of another class excessively.
  5. Inappropriate intimacy: a class that has dependencies on implementation details of another cclass.
  6. Lazy class / Freeloader: a class that does too little.
  7. Contrived complexity: forced usage of overly complicated design patterns where simpler design would suffice.
  8. Excessive use of literals: these should be coded as named constants, to improve readability and to avoid programming errors. Additionally, literals can and should be externalized into resource files/scripts where possible, to facilitate localization of software if it is intended to be deployed in different regions.
  9. Ubercallback: a callback that is trying to do everything

Determining what is and is not a code smell is often a subjective judgment, and will often vary by language, developer and development methodology.

There are some tools such as Checkstyle, PMD and FindBugs for Java, to automatically check for certain kinds of code smells.