Type: Feature Request
Status: Open (View Workflow)
Affects Version/s: 1.3.4
Fix Version/s: None
Similar Issues:Show 10 results
EMBJOPR-328 Execute Script operation's return value trimmed to 2000 chars EMBJOPR-223 results of Display Bindings operation are displayed briefly, but when page AJAX-refreshes, the results are lost (i.e. empty results are displayed) EMBJOPR-114 AS5 plugin: The "List All Subscriptions" operation for a Topic fails due to a NullPointerException EMBJOPR-327 RHQ-related description of script's Execute operation EMBJOPR-322 Datasource: Test Connection operation's "Successful" status may be confusing EMBJOPR-230 Operation Results screen looses the results table when automatically refreshed after 10s EMBJOPR-52 Viewing details after executing a JVM thread dump operation doesn't work EMBJOPR-367 subtype=QueueManage temporarily disappears from ManagementView compByCompType resulting in "There are currently no numeric metrics available." being displayed on JMS Manager/JMS Queues/* metric page EMBJOPR-113 AS5 plugin: When invoking the "List All Messages" operation for a Topic or Queue, "Arg#0" gets displayed as the operation parameter name instead of the actual parameter name EMBJOPR-236 executing a Stop operation on a started EAR/WAR or a Start operation on a stopped EAR/WAR, and then clicking on another tab or a node in the left nav tree, causes "org.jboss.seam.ConcurrentRequestTimeoutException: Concurrent call to conversation" error
If some shell script returns something else than 0, embjopr operation only says "Exit code was '1', see operation results for details", but there are no op results - that applies for JON.
The admin console should show some info about how to use the script, not fail with this generic message.
This might apply to all scripts which do not behave so by default (like classpath.sh).
1) run the wsprovide.sh with no arguments .
java.lang.Exception: Exit code was '1', see operation results for details