Datasources: JNDI name allowed to change, but does not work afterwards.
-----------------------------------------------------------------------
Key: EMBJOPR-335
URL: https://jira.jboss.org/browse/EMBJOPR-335
Project: Embedded Jopr
Issue Type: Bug
Affects Versions: 1.3.4
Environment: EAP 510 CR3.5
Reporter: Ondrej Zizka
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Better description of connection factory metrics
------------------------------------------------
Key: EMBJOPR-334
URL: https://jira.jboss.org/browse/EMBJOPR-334
Project: Embedded Jopr
Issue Type: Bug
Affects Versions: 1.3.4
Reporter: Ondrej Zizka
Priority: Minor
Connection factory's Metrics tab shows "Min size" and "Max size". It's not exactly clear what do these values mean - a maximum during whole life of the factory?
Pls add some better description.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
JMS dest removal ignored if JNDI name is invalid
------------------------------------------------
Key: EMBJOPR-333
URL: https://jira.jboss.org/browse/EMBJOPR-333
Project: Embedded Jopr
Issue Type: Bug
Affects Versions: 1.3.4
Environment: EAP 5.1.0 CR3.5
Reporter: Ondrej Zizka
Priority: Minor
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
JMS tools - Send message, show message (text ones)
--------------------------------------------------
Key: EMBJOPR-332
URL: https://jira.jboss.org/browse/EMBJOPR-332
Project: Embedded Jopr
Issue Type: Feature Request
Affects Versions: 1.3.3
Reporter: Ondrej Zizka
Priority: Minor
It would be nice to have a way to send and view text messages from the admin console. WDYT.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
EJB3 Restart operation -> org.jboss.seam.ConcurrentRequestTimeoutException: Concurrent call to conversation
-----------------------------------------------------------------------------------------------------------
Key: EMBJOPR-330
URL: https://jira.jboss.org/browse/EMBJOPR-330
Project: Embedded Jopr
Issue Type: Bug
Affects Versions: 1.3.4
Reporter: Ondrej Zizka
STR (or, better said, happened after this was done):
1) Install and run EAP 5.1.0.CR3.5 -c default
2) Deploy some EJB3 (attached)
3) Run it's Stop operation
4) Run it's Restart operation
5) That caused the attached exception to be thrown. From the nature of the bug, it's not easily reproducible.
Similar to EMBJOPR-236, if not the same.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Execute Script operation's return value trimmed to 2000 chars
-------------------------------------------------------------
Key: EMBJOPR-328
URL: https://jira.jboss.org/browse/EMBJOPR-328
Project: Embedded Jopr
Issue Type: Bug
Reporter: Ondrej Žižka
Priority: Minor
STR:
1) Navigate to classpath.sh script
2) Execute Script
3) Fill "-c" as params
4) See the classpath in the textarea - it's trimmed to 2k chars.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
RHQ-related description of script's Execute operation
------------------------------------------------------
Key: EMBJOPR-327
URL: https://jira.jboss.org/browse/EMBJOPR-327
Project: Embedded Jopr
Issue Type: Bug
Affects Versions: 1.3.4
Reporter: Ondrej Žižka
Assignee: Charles Crouch
Priority: Minor
Scripts' Execute Script op has this desc:
"execute the script; NOTE: environment variables to be passed to the script can be configured via this Script service's connection properties (under its Inventory tab)"
which is related to RHQ/JON and is misleading in Admin Console.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Round decimal numbers
---------------------
Key: EMBJOPR-326
URL: https://jira.jboss.org/browse/EMBJOPR-326
Project: Embedded Jopr
Issue Type: Bug
Reporter: Ondrej Žižka
Priority: Optional
I'd suggest to round decimal numbers to, say, two digits not to get values like
JVM Free Memory 982.7939453125 MB
JVM Total Memory 1.21002197265625 GB
Average Response Time 222.07692307692307 ms
etc. I suppose there's no need for precise decimals for any resource / app metrics.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Hide server's operations Start and Restart
------------------------------------------
Key: EMBJOPR-325
URL: https://jira.jboss.org/browse/EMBJOPR-325
Project: Embedded Jopr
Issue Type: Bug
Reporter: Ondrej Žižka
Start and Restart ops make no sense for Admin Console, do they?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Datasource: Test Connection operation's "Successful" status may be confusing
----------------------------------------------------------------------------
Key: EMBJOPR-322
URL: https://jira.jboss.org/browse/EMBJOPR-322
Project: Embedded Jopr
Issue Type: Feature Request
Affects Versions: 1.3.4
Reporter: Ondrej Žižka
Priority: Minor
See the picture attached.
Users may be mislead by the "Success" operation status to think that the datasource returned a connection.
I suggest to show Failure for both cases when the connection was not returned and the operation failed (which is quite improbable) - that would be much more intuitive (although it might not fit RHQ's operations doctrine).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira