[JBoss JIRA] (WFLY-12309) Need to include the schedule expression value in the toString() output of a calendar-based timer
by Cheng Fang (Jira)
[ https://issues.jboss.org/browse/WFLY-12309?page=com.atlassian.jira.plugin... ]
Cheng Fang updated WFLY-12309:
------------------------------
Description:
Currently the toString() output of a calendar-based timer contains the same info as that of a non-calendar-based timer. Need to enhance it to include schedule expression details to aid debug and monitoring.
The current output of a sample calendar-based timer:
{code}
timer [ID=FD3752D5-3D58-48AC-8E22-75A54BBF0C65 TIMEDOBJECTID=xxx AUTO-TIMER?:FALSE PERSISTENT?:FALSE TIMERSERVICE=ORG.JBOSS.AS.EJB3.TIMERSERVICE.TIMERSERVICEIMPL@49E567E4 INITIALEXPIRATION=NULL INTERVALDURATION(IN MILLI SEC)=0 NEXTEXPIRATION=NULL TIMERSTATE=ACTIVE INFO=TIMERINFO]
{code}
The desired output for a sample calendar-based timer:
{code}
timer: [id=07a989cf-e7d7-4dbc-ad66-75c54ad0d9fd timedObjectId=xxx auto-timer?:false persistent?:true timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl@204ac9fc initialExpiration=null intervalDuration(in milli sec)=0 nextExpiration=Sun Jul 21 09:06:21 CST 2019 timerState=ACTIVE info=null] ScheduleExpression[second=21 minute=6 hour=9 dayOfWeek=* dayOfMonth=21 month=7 year=2019 start=null end=null timezone=null]
{code}
> Need to include the schedule expression value in the toString() output of a calendar-based timer
> ------------------------------------------------------------------------------------------------
>
> Key: WFLY-12309
> URL: https://issues.jboss.org/browse/WFLY-12309
> Project: WildFly
> Issue Type: Enhancement
> Components: EJB
> Affects Versions: 17.0.1.Final
> Reporter: Cheng Fang
> Assignee: Cheng Fang
> Priority: Major
>
> Currently the toString() output of a calendar-based timer contains the same info as that of a non-calendar-based timer. Need to enhance it to include schedule expression details to aid debug and monitoring.
> The current output of a sample calendar-based timer:
> {code}
> timer [ID=FD3752D5-3D58-48AC-8E22-75A54BBF0C65 TIMEDOBJECTID=xxx AUTO-TIMER?:FALSE PERSISTENT?:FALSE TIMERSERVICE=ORG.JBOSS.AS.EJB3.TIMERSERVICE.TIMERSERVICEIMPL@49E567E4 INITIALEXPIRATION=NULL INTERVALDURATION(IN MILLI SEC)=0 NEXTEXPIRATION=NULL TIMERSTATE=ACTIVE INFO=TIMERINFO]
> {code}
> The desired output for a sample calendar-based timer:
> {code}
> timer: [id=07a989cf-e7d7-4dbc-ad66-75c54ad0d9fd timedObjectId=xxx auto-timer?:false persistent?:true timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl@204ac9fc initialExpiration=null intervalDuration(in milli sec)=0 nextExpiration=Sun Jul 21 09:06:21 CST 2019 timerState=ACTIVE info=null] ScheduleExpression[second=21 minute=6 hour=9 dayOfWeek=* dayOfMonth=21 month=7 year=2019 start=null end=null timezone=null]
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years
[JBoss JIRA] (WFCORE-4576) Managed dependency wildfly-core-vault-test-galleon-pack not deployed
by Eduardo Martins (Jira)
Eduardo Martins created WFCORE-4576:
---------------------------------------
Summary: Managed dependency wildfly-core-vault-test-galleon-pack not deployed
Key: WFCORE-4576
URL: https://issues.jboss.org/browse/WFCORE-4576
Project: WildFly Core
Issue Type: Bug
Components: Build System
Reporter: Eduardo Martins
Assignee: Eduardo Martins
wildfly-core-vault-test-galleon-pack is a wildfly-core-parent managed dependency, yet wildfly-core releases do not deploy it to remote Maven repositories. Any import, such as wildfly-parent or component matrix BOMs, of such dependency management than includes a non existent artifact...
There are two high level solutions for a fix:
a) deploy such artifact to remote maven repos
b) remove such artifact from WildFly-core-parent's dependency management
Please note that b) implies that either all dependants are updated to include <version/>, or such artifact version management is moved to testsuite/pom.xml (a non managed pom that is parent of all dependants).
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years
[JBoss JIRA] (WFCORE-4575) wildfly-self-contained still a managed dependency
by Eduardo Martins (Jira)
Eduardo Martins created WFCORE-4575:
---------------------------------------
Summary: wildfly-self-contained still a managed dependency
Key: WFCORE-4575
URL: https://issues.jboss.org/browse/WFCORE-4575
Project: WildFly Core
Issue Type: Bug
Components: Build System
Affects Versions: 10.0.0.Beta2
Reporter: Eduardo Martins
Assignee: Eduardo Martins
WildFly-core-parent's dependency management includes
{code}
<dependency>
<groupId>org.wildfly.core</groupId>
<artifactId>wildfly-self-contained</artifactId>
<version>${project.version}</version>
</dependency>
{code}
but such artifact does not exists anymore in the project.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years
[JBoss JIRA] (SWSQE-695) Map Jira Workflows To Tablue Graphs
by Matthew Mahoney (Jira)
[ https://issues.jboss.org/browse/SWSQE-695?page=com.atlassian.jira.plugin.... ]
Matthew Mahoney updated SWSQE-695:
----------------------------------
Sprint: Kiali Sprint #23, Kiali Sprint #26 (was: Kiali Sprint #23, Kiali Sprint #25)
> Map Jira Workflows To Tablue Graphs
> -----------------------------------
>
> Key: SWSQE-695
> URL: https://issues.jboss.org/browse/SWSQE-695
> Project: Kiali QE
> Issue Type: QE Task
> Reporter: Matthew Mahoney
> Assignee: Prachi Yadav
> Priority: Major
> Labels: pqi
>
> Two parts to this task:
> 1) Because only a couple team members have access to Tablue, generate Kiali metric graphs in Tablue and Paste them into a team accessablel doc so that we can analyze these metrics
> 2) Map Jira Workflow queries to Tablue graphs, so that we can better understand how each of the Tablue graphs are generated.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years