After many days of fiddling I managed to get the Object Browser for JBoss 5.0.1 running (JBossTS 4.6.1.GA). The conclusions I came to are:
* The bat-scripts are broken in the freestanding tools. run-tools.bat overwrites env variables from setup-env.bat
* Jacorb.jar is a required dependency of the tools, but this jar is not included in the sar, so you cannot run the jboss-tools.sar in the 'default' jboss
config without adding the jar to the lib or to the sar.
* When starting the tools, there is no mentioning in the scripts of that you have to set "-Dcom.arjuna.ats.arjuna.objectstore.objectStoreDir" and "...localOsRoot". Could be nice to have in the README. If you are not supposed to do this, it would be great to have a summary of what you could do instead to connect to the ondisk stores.
* The freestanding tools start recovery as well! This was a surprise and quite scary!
* It is confusing that the perf tools connect to JMX, while the OS browser partly connects via JMX and partly via filesystem. This could be explained better.
* The tool doesn't work on Windows - it uses a FS path as a key to load view plugins. Since file.separator in win is not '/', only the "default" view plugin is loaded (getType() doesn't match), which in principle causes silent failure - you can view no transactions. A very hacky workaround is to reset "file.separator" and to reflection-patch BrowserFrame.GROUP_DELIMITER.
* The "Applet" in the sar is in fact no Applet (even though it extends JApplet)! Instead, it tries to open a JFrame on the server, causing headaches trying to forward the gui with X forwarding or similar.
* The class loading mechanisms of JBoss 5.0.1 doesn't like the GUI trying to load the dialog classes lazily once you click on a button in the gui. A workaround is to eagerly load these classes before starting the sar.
* Clicking 'forget' on TX:es in the persistent store seems to work well, but 'rollback' and 'commit' have no apparent feedback once confirmed. In my examples, they remain in the list with the same status.
* There is very little information generally on what the different stores are and what you are *supposed* to see in the GUI, so it's very hard to confirm that it in fact is working the way is is supposed to.
All in all, although I know this isn't officially supported software, it seems to be in a quite non-stable state. And I am now left asking myself how to go from here. Are there any other tools available for manually controlling failed (heuristic) TX:es? Is the idea that this GUI is not needed at all? Has everyone got this tool up and running, or what are you doing?