Free ibm websphere software for linux

Escher is a Java X11 library.

Escher is a collection of libraries for X Window System written purely in Java.

It consists of an X11 protocol implementation (similar to Xlib for C/C++), and its extensions including GLX, and the OpenGL rendering protocol.

How To Run

Install JDK 1.3 (http://www.ibm.com/java/jdk/linux130/).
Inside the directory "escher-0.1.0" (or later version),

$ xhost +localhost $ java gnu.x11.test.Hello --help
$ java gnu.x11.test.Hello It will pop up an X window which says "Hello World!".
$ etc/bin/jdemo gnu

You will see a list of X applications and test suits you can run.

Linux Test Project is a joint project with SGI, IBM, OSDL, Bull, and Wipro Technologies with a goal to deliver test suites to the open source community that validate the reliability, robustness, and stability of Linux.

The project consists of well over 2000 individual testcases and a test driver to automate execution of the tests.

Whats New in This Release:

1) Log Message: lcov: preparations for new release by "oberpapr@users.sourceforge.net"
- updated CHANGES file
- added compat-libtool + no-compat-libtool option
- changed libtool default to on (due to popular request)
- added checksum option
- changed checksum default to off (to reduce cpu time + file size)
- added geninfo_checksum option to lcovrc, deprecated geninfo_no_checksum
- added geninfo_compat_libtool option to lcovrc
- minor update of README file
File(s) Affected:
ltp/utils/analysis/lcov/CHANGES
ltp/utils/analysis/lcov/README
ltp/utils/analysis/lcov/lcovrc
ltp/utils/analysis/lcov/bin/geninfo
ltp/utils/analysis/lcov/bin/lcov

2) Log Message: update manpage by "oberpapr@users.sourceforge.net"
File(s) Affected:
ltp/utils/analysis/lcov/man/lcov.1

3) Log Message: "sachinp@in.ibm.com" has fixed a probe point definition from ll_rw_lock to ll_rw_block
File(s) Affected:
ltp/testcases/kdump/susetools/lkdtm_mod/lkdtm.c

4) Log Message: man page update by "oberpapr@users.sourceforge.net"
File(s) Affected:
ltp/utils/analysis/lcov/man/genhtml.1
ltp/utils/analysis/lcov/man/geninfo.1
ltp/utils/analysis/lcov/man/lcov.1

5) Log Message: lcov: another update in preparation for a new release by "oberpapr@users.sourceforge.net"
File(s) Affected:
ltp/utils/analysis/lcov/bin/lcov
ltp/utils/analysis/lcov/man/lcovrc.5
ltp/utils/analysis/lcov/CHANGES
ltp/utils/analysis/lcov/lcovrc

6) Log Message: fixed bug that would not delete .gcda files when using -z, by "oberpapr@users.sourceforge.net"
File(s) Affected:
ltp/utils/analysis/lcov/CHANGES
ltp/utils/analysis/lcov/bin/lcov

7) Log Message: lcov: - add new option --initial to get zero coverage data from graph files by "oberpapr@users.sourceforge.net"
File(s) Affected:
ltp/utils/analysis/lcov/CHANGES
ltp/utils/analysis/lcov/bin/geninfo
ltp/utils/analysis/lcov/bin/lcov
ltp/utils/analysis/lcov/man/geninfo.1
ltp/utils/analysis/lcov/man/lcov.1

8) Log Message: "carmelo.amoroso@st.com" fixed the anomaly when "SHLBA != getpagesize()", like in SH architecture
File(s) Affected:
ltp/testcases/kernel/mem/shmt/shmt09.c

9) Log Message: "hdeller@users.sf.net" fixed unitialized variable useage in "lseek09" testcase
File(s) Affected:
ltp/testcases/kernel/syscalls/lseek/lseek09.c

10) Log Message: "naveenspen@gmail.com" pointed out that syslog_cmd="/etc/init.d/syslog" should be used irrespective of any Distro
File(s) Affected:
ltp/testcases/kernel/syscalls/syslog/syslog01
ltp/testcases/kernel/syscalls/syslog/syslog02
ltp/testcases/kernel/syscalls/syslog/syslog03
ltp/testcases/kernel/syscalls/syslog/syslog04
ltp/testcases/kernel/syscalls/syslog/syslog05
ltp/testcases/kernel/syscalls/syslog/syslog06
ltp/testcases/kernel/syscalls/syslog/syslog07
ltp/testcases/kernel/syscalls/syslog/syslog08
ltp/testcases/kernel/syscalls/syslog/syslog09
ltp/testcases/kernel/syscalls/syslog/syslog10

11) Log Message: "rsalveti@linux.vnet.ibm.com" pointed out to have same "fsx-linux" testcase for "fs", "ltp-aiodio" and "nfs"
File(s) Affected:
ltp/testcases/kernel/io/ltp-aiodio/fsx-linux.c
ltp/testcases/network/nfs/fsx-linux/fsx-linux.c

12) Log Message: Randy Dunlap writes: Fix printf format warnings
File(s) Affected:
ltp/testcases/network/stress/ns-tools/Makefile
ltp/testcases/network/stress/ns-tools/ns-igmp_querier.c
ltp/testcases/network/stress/ns-tools/ns-mcast_join.c
ltp/testcases/network/stress/ns-tools/ns-mcast_receiver.c
ltp/testcases/network/stress/ns-tools/ns-tcpserver.c

13) Log Message: getsockopt() takes a socklen_t, not an int, as its optlen
File(s) Affected:
ltp/testcases/network/stress/ns-tools/ns-tcpclient.c
ltp/testcases/network/stress/ns-tools/ns-tcpserver.c
ltp/testcases/network/stress/ns-tools/ns-udpserver.c

14) Log Message: cleanup file
File(s) Affected:
ltp/testcases/kernel/syscalls/gethostid/gethostid01.c

15) Log Message: back out uclinux changes to something that doesnt spit warnings as reported by Randy Dunlap
File(s) Affected:
ltp/testcases/kernel/syscalls/gethostid/gethostid01.c

16) Log Message: fixup gcc warnings by removing silly pieces of code
File(s) Affected:
ltp/testcases/kernel/mem/mtest06/mmap1.c
ltp/testcases/kernel/mem/mtest06/mmap2.c
ltp/testcases/kernel/mem/mtest06/mmap3.c
ltp/testcases/kernel/mem/mtest06/shmat1.c

17) Log Message: Randy Dunlap writes: Convert mmap1 to use standard test results output format. Correct several typos.
File(s) Affected:
ltp/testcases/kernel/mem/mtest06/Makefile
ltp/testcases/kernel/mem/mtest06/mmap1.c

18) Log Message: gcov-kernel: adding gcov-kernel patch for 2.6.22
File(s) Addes:
ltp/utils/analysis/gcov-kernel/linux-2.6.22-gcov-arm-hack.patch
ltp/utils/analysis/gcov-kernel/linux-2.6.22-gcov.patch

19) Log Message: [1754301] Helge Deller writes: mark hppa/parisc as expecting a segv as well
File(s) Affected:
ltp/testcases/kernel/syscalls/mmap/mmap03.c

20) Log Message: Randy Dunlap writes: convert output to match the standard LTP output
File(s) Affected:
ltp/testcases/kernel/fs/linktest/linktest.pl

21) Log Message: close stdout to remove noise
File(s) Affected:
ltp/testcases/kernel/mem/mtest05/dummy.c

22) Log Message: Randy Dunlap writes: Convert mmstress to use the standard results format
File(s) Affected:
ltp/testcases/kernel/mem/mtest05/Makefile
ltp/testcases/kernel/mem/mtest05/mmstress.c

23) Log Message: "rsalveti@linux.vnet.ibm.com" updated the contact information at ltp-howto doc
File(s) Affected:
ltp/doc/ltp-howto.lyx
ltp/doc/ltp-howto.txt

24) Log Message: "rsalveti@linux.vnet.ibm.com" wants to update this with kernel/fs/fsstress/fsstress.c
File(s) Affected:
ltp/testcases/network/nfs/nfs_fsstress/fsstress.c

25) Log Message: "suzuki@in.ibm.com" added SIGNAL and Address Fault handling capability for all architectures
File(s) Affected:
ltp/testcases/kernel/mem/mtest06/mmap1.c

26) Log Message: "rsalveti@linux.vnet.ibm.com" added more options to runltp
File(s) Affected:
ltp/runltp
ltp/doc/man1/pan.1
ltp/pan/pan.c

27) Log Message: Upgrade to Posix Testsuite 1.5.2
File(s) Affected/Added:
ltp/testcases/open_posix_testsuite

28) Log Message: Fixing Proper Freeing of Memory Chunks
File(s) Affected:
ltp/tools/genload/stress.c

Objective of this project to provide benchmarking toolset for all available multiplatform C/C++ (and some Java) XML parsers.
Main features:
Currently following parsers are supported:
- LibXML2 + GDome + LibXSLT + XML Security
- Apache Xerces for C + Apache Xalan for C + Apacge XML Security for C
- IBM XML4C + IBM Lotus XSL
- Expat + CenterPoint XML + Sablotron + Arabica
- RXP Parser
- Oracle XDK for C/C++
- Oracle XDK for Java
- QT XML Module
- Sun Crismon + Java WebServices Developer Pack 1.2 + Apache XML Security
Following separate benchmarks provided:
- Non-Validating Parsing with Native,SAX,DOM Engines Benchmark
- Creating + Serializing DOM treee Benchmark
- Schema Validation Benchmark
- XSL Transformation Benchmark
- XML Security (Signature, Encryption) Benchmark
Following XML sources supported:
- Any valid XML file (with optional XSL, XSD companions)
- Auto-generated random simple XML file (variable size)
- Auto-generated random XML OPC-DA message sequence (variable size and length
Enhancements:
- Support Apache XML Security for C++, Version: CVS 08.02.2004
- Experemental support for XML Encryption Benchmark for Apache XML Security for C++ from CVS tree.
- Tested againist latest libraries

JProfiler is an award-winning all-in-one Java profiler. JProfilers intuitive GUI helps you find performance bottlenecks, pin down memory leaks and resolve threading issues.
Even though JProfiler has a powerful feature set, its a Java profiler that is extremely easy to use! JProfilers user interface provides a unified view on the profiled application and puts all the information you need right at your fingertips with its intuitive hierarchy of views.
Configure your application for profiling
When starting up JProfiler, the start center is brought up. Here you can manage and start your profiling sessions. To configure your application for profiling, change to the "New session" tab and click on the New session button. Enter the required information into the session config dialog as described below and select Ok to start profiling. Thats all it takes. Note the Help button which appears on all of JProfilers dialogs displays a context sensitive explanation of all features.
While the configuration dialog displays numerous options that you will not want to miss after becoming familiar with JProfiler, entering the basic pieces of information is really very simple:
1. Enter a name for your session.
2. Enter the name of your main class.
3. Enter your class path.
4. Press Ok.
Before profiling is actually started, the profiling settings dialog is displayed where you can select the focus for your profiling run. Although profiling produces an overhead when running your application, you can minimize it by choosing a setting for which JProfiler only records information that is interesting for you.
If you want to fine-tune your profiling settings, the [Edit] button brings up a dialog with all available configuration options for profiling.
Observe classes and allocations
To find out what is going on the heap in terms of objects and classes, turn to the classes monitor. It gives you continuous updates and lets you set marks to observe changes over time. To see references, allocations and object data for your selection, you can take a snapshot by clicking on the camera in JProfilers toolbar.
If you want to know where your objects are allocated, you can go to the allocation monitor. Here, you can inspect the call tree and find out what method calls have caused the allocation of a selected class or package. Just like in the allocation monitor, you can display this data for live and garbage collected objects.
An cumulated overview on which methods are responsible for allocations is given by the allocation hot spots view. Each hot spot can be expanded and the backtraces that lead to the invocation of the hot spot are displayed. You can also mark the current values and view the differences in allocations over time.
Find memory leaks
JProfilers heap walker works like a browser: it displays a current set of objects that can be changed by adding selection steps with the [Use selected] button. You can inspect the current object set in the four views of the heap walker.
In the classes view, you can select one or several classes and add a selection step. The new object set will contain only the selected instances. This is often the first thing you want to do after taking a snapshot. You can perform this step automatically by invoking the heap walker from the classes monitor.
The allocations view of the heap walker shows the allocation tree and the allocation hot spot list of the current object set. You can add a selection step for one or multiple allocation spots or hot spots. The new object set will then be restricted to the selected instances only.
When youre looking for the cause of a memory leak, the reference view is the most important view in JProfiler. Here, you can find out why an object has not been garbage collected. Use the "Show path to GC root" function to show where the JVM hangs on to the selected instance.
Not only is the heap walker your first stop for finding memory leaks, it also makes for an excellent debugging facility. In the data view, you can inspect instances, arrays and classes in the current object set and navigate along references. There are many situations where the usual debugging approach will fail and JProfiler will help you find out.
Zoom in on performance bottlenecks
Controlling your applications performance may be driven by quality of service constraints or by general quality assurance, JProfilers CPU views lend themselves naturally to both approaches.
To record CPU data, you switch to the CPU section and click on the recording button in JProfilers tool bar. The first view in the CPU section shows the invocation tree, cumulated for all threads. To find performance related problem spots, just follow the big percentages when opening the tree nodes. Also, the absolute times and the number of invocations that are displayed for each node can help you in getting a feeling for the situation. Once you become familiar with JProfiler, you may want to customize this view to best fit your personal preferences.
The invocation tree is a top-down view on the method calls of your application. This viewpoint is most useful when you experience an actual performance bottleneck in your application. If you want to improve overall performance, a bottom-up view may be more applicable.
This kind of view - called hot spots view - shows the methods where most of the time is spent. By opening these nodes you get backtraces which show the various invocation paths together with the percentages of their contributions. Note that by default, method calls within Java core classes are not shown separately - each of your library calls is treated as opaque. You can change this behavior by deactivating the corresponding filter sets.
The method graph combines both viewpoints. Incoming and outgoing method calls are presented in the same way. For a number of situations, the method graph can give you more insight than the invocation tree and the hot spots view. The best strategy is to use the invocation and hot spots views first and switch to the method graph for detailed analysis.
Solve thread-related problems
Threads can be exceptionally difficult to debug, especially if you dont have sufficient information on the actual sequence and status of the threads in your application. JProfilers thread views provide you with exactly this knowledge.
The thread history view shows a continuous update of the lifelines of all threads on the horizontal axis. The names of the threads are displayed on the vertical axis in the order of their creation. Each color signifies a different thread status. Orange means that the thread was sleeping, green stands for a runnable thread while red is displayed if the thread was waiting for a monitor. You can zoom in and out to your desired detail level or have the time axis fit your windows size automatically.
If youre more interested in whats happening right now, the thread monitor view is the right place to look at. Here, you can sort threads, filter with respect to thread status and view additional information on each thread.
Should you ever have a deadlock in your application, the deadlock detection graph will help you analyze the involved threads and the locking situation. Simple deadlocks like the one shown could be worked out by hand from the other views, but for complicated deadlock involving a greater number of threads this view is indispensable.
Reducing general monitor contention and debugging locking sequences requires a detailed view of the current monitor usage and a history of all monitor-related events. JProfiler has both. Below you see the monitor usage history which shows a blocking event together with the stack trace of the waiting thread.
Keep an eye on your JVM
Monitoring cumulative parameters of the virtual machine can be a highly fruitful activity, even if everything seems to be all right. Measuring and observing parameters like heap size, object count, loaded classes and thread numbers can point to dangerous trends and problematic behavior to look out for. In its VM telemetry view section, JProfiler features various telemetry controls which provide you with the information you need to stay one step ahead.
The number of objects on the heap, split in arrays and non-arrays. This is your first stop if you are suspecting a memory leak. All objects with live references are included, as well as those which are unreferenced but the garbage collector hasnt had a chance to collect yet.
The garbage collector activity which displays freed and moved objects. If your application is thrashing the heap excessively, this will show up here. Moving large numbers of objects places a high burden on the virtual machine and can lead to temporary freezes. Mostly this occurs when the virtual machine is enlarging the heap.
The number of threads in the virtual machine, split in active and inactive threads. This is useful if you create a large number of threads and need information on changes in their total number and how many of them actually run.
Enhancements:
- New futures:
- rewritten eclipse 3.x integration
- rewritten IDEA 4.x integration
- IDE integration for JDeveloper
- IDE integration for Netbeans 4.0
- considerably reduced memory consumption
- improved long-term stability for profiling
- heap walker: in the cumulated incoming reference view, reference holders as well as referenced objects can be displayed and selected
- option to keep the profiled JVM alive
- support for Java Web Start 1.5
- CSV export for graphs
- enhancements in XML export for trees
- integration wizard for profiling servers in IBM WSAD
- integration wizards for Pramati 3.5 and Pramati 4.x application server
- integration wizard for Websphere 4.0 Advanced Edition
- integration wizard for Sun Java System Web Server
- integration wizard for Sun Java System Application Server
- integration wizard for Oracle 10g Application server
- integration wizard for Apple WebObjects Developer 5.x
- snapshot files (*.jps) can be opened from the command line and from the Windows explorer
- JBuilder IDE integration now supports JBuilder 2005
- much better appearance of the JProfiler GUI with Windows native look and feel
- JProfiler GUI now also runs under Java 1.5
- Bug fixes:
- monitor statistics were broken
- invalid class files caused a shutdown of the profiled application
- many bug fixes in the GUI

Xbox360 Controller Driver package contains the diabolixs compiled Xbox360 controller driver for Linux on the PS3.

Its been tested with Fedora Core 5 (PPC distribution) using Snes9x and Doom.

The Xbox 360 is the successor to Microsofts Xbox video game console, developed in cooperation with IBM, ATI, Samsung and SiS. Information on the console first came through viral marketing campaigns and it was officially unveiled on MTV on May 12, 2005, with detailed launch and game information divulged later that month at the Electronic Entertainment Expo.

The Xbox 360 is the first console to have a near-simultaneous launch across the three major regions, and the first to provide wireless controller support at launch. The console sold out completely at release and by the end of 2006 had sold 10.4 million worldwide.

The Xbox 360 was the first home console to be released in the seventh generation of game consoles and competes against Sonys PlayStation 3 and Nintendos Wii. Its Xbox Live service allows players to compete online as well as download games and additional content.