There is an Eclipse RCP project developed by sun jdk, and when running on
AIX, bug happened.
!ENTRY org.eclipse.core.filesystem 1 1 2009-07-07 03:36:32.194
!MESSAGE Could not load library: liblocalfile_1_0_0.a. This library
provides platform-specific optimizations for certain file system
operations. This library is not present on all platforms, so this may not
be an error. The resources plug-in will safely fall back to using
java.io.File functionality.
!STACK 0
java.lang.UnsatisfiedLinkError: localfile_1_0_0 (Not found in
java.library.path)
at java.lang.ClassLoader.loadLibraryWithPath(ClassLoa der.java:979)
at java.lang.ClassLoader.loadLibraryWithClassLoader(C lassLoader.java:948)
at java.lang.System.loadLibrary(System.java:453)
at org.eclipse.core.internal.filesystem.local.LocalFi
leNatives.<clinit>(LocalFileNatives.java:32)
at java.lang.J9VMInternals.initializeImpl(Native Method)
at java.lang.J9VMInternals.initialize(J9VMInternals.j ava:194)
at org.eclipse.core.internal.filesystem.local.LocalFi
le.fetchInfo(LocalFile.java:141)
at org.eclipse.core.filesystem.provider.FileStore.fet
chInfo(FileStore.java:277)
at org.eclipse.core.internal.localstore.BlobStore.<in
it>(BlobStore.java:45)
at org.eclipse.core.internal.localstore.HistoryStore2
<init>(HistoryStore2.java:77)
at org.eclipse.core.internal.resources.ResourcesCompa
tibility.createHistoryStore(ResourcesCompatibility .java:45)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Native
MethodAccessorImpl.java:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(De
legatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at org.eclipse.core.internal.resources.ResourcesCompa
tibilityHelper.createHistoryStore(ResourcesCompati bilityHelper.java:73)
at org.eclipse.core.internal.resources.ResourcesCompa
tibilityHelper.createHistoryStore(ResourcesCompati bilityHelper.java:47)
at org.eclipse.core.internal.localstore.FileSystemRes
ourceManager.getHistoryStore(FileSystemResourceMan ager.java:338)
at org.eclipse.core.internal.resources.SaveManager.sa
ve(SaveManager.java:1012)
at org.eclipse.core.internal.resources.Workspace.save (Workspace.java:1827)
at org.talend.commandline.CommandLineApplication.star t(Unknown Source)
at org.eclipse.equinox.internal.app.EclipseAppHandle.
run(EclipseAppHandle.java:193)
at org.eclipse.core.runtime.internal.adaptor.EclipseA
ppLauncher.runApplication(EclipseAppLauncher.java: 110)
at org.eclipse.core.runtime.internal.adaptor.EclipseA
ppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.ru
n(EclipseStarter.java:382)
at org.eclipse.core.runtime.adaptor.EclipseStarter.ru
n(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Native
MethodAccessorImpl.java:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(De
legatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at org.eclipse.equinox.launcher.Main.invokeFramework( Main.java:549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.ja va:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:12 36)
at org.eclipse.equinox.launcher.Main.main(Main.java:1 212)
This happens on a few platforms, including AIX, where the localfile_1_0_0
library is not included. Though I'm not sure exactly which IO functionality
is unavailable in the absence of this library, it cannot be anything
significant, otherwise this library would be included.
Grant
"nma " <maning915@gmail.com> wrote in message
news:296e6bc1b18341d21d2b6ddafa6d7d53$1@www.eclipse.org...
> There is an Eclipse RCP project developed by sun jdk, and when running on
> AIX, bug happened.
>
> !ENTRY org.eclipse.core.filesystem 1 1 2009-07-07 03:36:32.194
> !MESSAGE Could not load library: liblocalfile_1_0_0.a. This library
> provides platform-specific optimizations for certain file system
> operations. This library is not present on all platforms, so this may not
> be an error. The resources plug-in will safely fall back to using
> java.io.File functionality.
> !STACK 0
> java.lang.UnsatisfiedLinkError: localfile_1_0_0 (Not found in
> java.library.path)
> at java.lang.ClassLoader.loadLibraryWithPath(ClassLoa der.java:979)
> at java.lang.ClassLoader.loadLibraryWithClassLoader(C lassLoader.java:948)
> at java.lang.System.loadLibrary(System.java:453)
> at org.eclipse.core.internal.filesystem.local.LocalFi
> leNatives.<clinit>(LocalFileNatives.java:32)
> at java.lang.J9VMInternals.initializeImpl(Native Method)
> at java.lang.J9VMInternals.initialize(J9VMInternals.j ava:194)
> at org.eclipse.core.internal.filesystem.local.LocalFi
> le.fetchInfo(LocalFile.java:141)
> at org.eclipse.core.filesystem.provider.FileStore.fet
> chInfo(FileStore.java:277)
> at org.eclipse.core.internal.localstore.BlobStore.<in
> it>(BlobStore.java:45)
> at org.eclipse.core.internal.localstore.HistoryStore2
> <init>(HistoryStore2.java:77)
> at org.eclipse.core.internal.resources.ResourcesCompa
> tibility.createHistoryStore(ResourcesCompatibility .java:45)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Native
> MethodAccessorImpl.java:79)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(De
> legatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:618)
> at org.eclipse.core.internal.resources.ResourcesCompa
> tibilityHelper.createHistoryStore(ResourcesCompati bilityHelper.java:73)
> at org.eclipse.core.internal.resources.ResourcesCompa
> tibilityHelper.createHistoryStore(ResourcesCompati bilityHelper.java:47)
> at org.eclipse.core.internal.localstore.FileSystemRes
> ourceManager.getHistoryStore(FileSystemResourceMan ager.java:338)
> at org.eclipse.core.internal.resources.SaveManager.sa
> ve(SaveManager.java:1012)
> at org.eclipse.core.internal.resources.Workspace.save
(Workspace.java:1827)
> at org.talend.commandline.CommandLineApplication.star t(Unknown Source)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.
> run(EclipseAppHandle.java:193)
> at org.eclipse.core.runtime.internal.adaptor.EclipseA
> ppLauncher.runApplication(EclipseAppLauncher.java: 110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseA
> ppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.ru
> n(EclipseStarter.java:382)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.ru
> n(EclipseStarter.java:179)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Native
> MethodAccessorImpl.java:79)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(De
> legatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:618)
> at org.eclipse.equinox.launcher.Main.invokeFramework( Main.java:549)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.ja va:504)
> at org.eclipse.equinox.launcher.Main.run(Main.java:12 36)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1 212)
>
What I'm saying is, this is expected behaviour on AIX, there is no fix
required on your end. Part of the warning message reads "This library is
not present on all platforms, so this may not be an error." This has been
logged as https://bugs.eclipse.org/bugs/show_bug.cgi?id=176470 . If you
want to know of future progress on this then you should CC yourself to this
bug's resolved duplicate bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=12358 .
Is this causing you an actual loss of functionality?
Grant
"nma " <maning915@gmail.com> wrote in message
news:88407d3779ba36d18a1bdf6f9d87eb22$1@www.eclipse.org...
> Grant, it's very kind-hearted of you to reply.
>
> The problem still have not been fixed. Could you tell me what should I go
> on to do to fix this problem, or do which test to try to see the problem ?
>
> Thanks very much for your help.
>
> nma
>
Yes, this problem is quite serious for me, as after this exception
happened, it seemed that my product did not fall back to use java.io.File
behaviour but exited.
Perhaps you should ping the bug report and indicate that it's actually
causing a problem for you that's worse than just a warning message.
Grant
"nma " <maning915@gmail.com> wrote in message
news:793ba1fe39f6c07cb844568edda9e2f9$1@www.eclipse.org...
> Yes, this problem is quite serious for me, as after this exception
> happened, it seemed that my product did not fall back to use java.io.File
> behaviour but exited.
>
> Thx.
>
> nma.
>
>