Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 342332 - Will not run
Summary: Will not run
Status: RESOLVED NOT_ECLIPSE
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.7   Edit
Hardware: Other other
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 356303 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-04-08 16:26 EDT by Roger CLA
Modified: 2011-09-09 10:06 EDT (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Roger CLA 2011-04-08 16:26:06 EDT
Build Identifier: swt-3.6.2-gtk-aix-ppc64

Running a java app that calls SWT on an AIX OS v6.1 (64bit) against a WebSphere Applciation Server v7.0.0.13 (JVM 64bit)..

Error I'm getting:
Exception in thread "main" java.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons:
        swt-pi-gtk-3659 (Not found in java.library.path)
        swt-pi-gtk (Not found in java.library.path)
        /tmp/swtlib-64/libswt-pi-gtk-3659.a (A file or directory in the path name does not exist.)
        /tmp/swtlib-64/libswt-pi-gtk.a (A file or directory in the path name does not exist.)

        at org.eclipse.swt.internal.Library.loadLibrary(Unknown Source)
        at org.eclipse.swt.internal.Library.loadLibrary(Unknown Source)
        at org.eclipse.swt.internal.gtk.OS.<clinit>(Unknown Source)
        at java.lang.J9VMInternals.initializeImpl(Native Method)
        at java.lang.J9VMInternals.initialize(J9VMInternals.java:200)
        at org.eclipse.swt.internal.Converter.wcsToMbcs(Unknown Source)
        at org.eclipse.swt.internal.Converter.wcsToMbcs(Unknown Source)
        at org.eclipse.swt.widgets.Display.<clinit>(Unknown Source)
        at java.lang.J9VMInternals.initializeImpl(Native Method)
        at java.lang.J9VMInternals.initialize(J9VMInternals.java:200)
        at com.ibm.ws.sib.tools.explorer.SIBExplorer.go(SIBExplorer.java:192)
        at com.ibm.ws.sib.tools.explorer.SIBExplorer.main(SIBExplorer.java:87)

sibexplorer.sh sources in a file called env.sh which is comprised of the following:
WAS=/usr/WebSphere/7.0/DMGR
SWTJARS=/usr/WebSphere/CNA/SWT
CUR=/usr/WebSphere/7.0/DMGR/scripts/WorkInProgress/SIBExplorer




Reproducible: Always

Steps to Reproduce:
1.SWT library location:  /usr/WebSphere/CNA/SWT
2.Java application location: /usr/WebSphere/7.0/DMGR/scripts/WorkInProgress/SIBExplorer
3.
Comment 1 Michael Rennie CLA 2011-04-11 09:48:22 EDT
Looks like a configuration problem not a bug.

Roger, are either of the mentioned missing libraries available to the program?

i.e. are swt-pi-gtk-3659 / swt-pi-gtk / SWTJARS on your PATH, LD_LIBRARY, java.library.path or the working directory (for example)? 

What kind of launch configuration is this? is it a Java Application type, or some type provided by com.ibm.ws.sib.tools?
Comment 2 Michael Rennie CLA 2011-04-18 11:17:25 EDT
marking not_eclipse without more information
Comment 3 Roger CLA 2011-04-25 16:28:15 EDT
What kind of launch configuration is this? is it a Java Application type, or
some type provided by com.ibm.ws.sib.tools?  -->  I'm supposedly using a Java App called sibexplorer  from IBM.

These are the steps:

 1.   Download and unzip the SWT libraries from Eclipse into a directory.

 2.   Download and unzip the SI Bus Explorer client code into a directory.

 3.   On Windows® platforms, edit the file env.bat in your favorite text editor.
    On UNIX®-based platforms, edit the file env.sh.

    This file contains three environment varibables that must be tailored to your particular system's configuration:
        The WAS variable should point to your WebSphere installation directory.
        The SWTJARS variable should point to the directory containting the downloaded SWT JARs.
        The CUR variable should point to the directory containing the SI Bus Explorer client code.

 4.   On some UNIX-based systems, it may be necessary to ensure that the sibexplorer.sh has the executable flag set on it. This can be done with the command chmod a+x sibexplorer.sh.

My gut tells me multiple things?
A)  Where do the SWT libraries need to reside when using WebSphere ND v 7.x  (DMGR, AppServer, WAS direstory, standalone directory, etc...) ?

B)  What else is needed beside the SWT libraries from this location:  http://www.eclipse.org/downloads/download.php?file=/eclipse/downloads/drops/R-3.6.2-201102101200/swt-3.6.2-gtk-aix-ppc64.zip
Comment 4 Roger CLA 2011-04-25 16:29:27 EDT
Refer to the additional notes...
Comment 5 Michael Rennie CLA 2011-04-25 16:55:37 EDT
(In reply to comment #4)
> Refer to the additional notes...

I have no idea what sibexplorer is, it is not part of Eclipse. 

Roger, I would suggest filing a bug against RAD \ Websphere or contacting whomever provides support for your IBM products.

Re-marking not_eclipse.
Comment 6 Dani Megert CLA 2011-04-26 03:53:30 EDT
Why do you try to mix SWT with SI Bus Explorer? Is this recommended / supported by IBM at all?
Comment 7 Michael Rennie CLA 2011-09-09 10:06:24 EDT
*** Bug 356303 has been marked as a duplicate of this bug. ***