Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
We need some consistency in our functional test cases.
The best we can do currently is to wait for an estimated time before the Java EE timers in the product should have been triggered. It would be much more predictable if the test cases could trigger the timers programmatically, probably with JMX.
How can this be done? Is there a JMX interface to the Glassfish Timer facility which we can use?
Its apparently impossible, since the question remain unanswered for almost three months.
However, I realized that for testing purposes it is enough to be notified when the triggering has actually occured. (Triggering it actively will only buy me time at the trade for quality)
I’m adding monitoring for event completions instead, but thanks for letting me know that it’s actually impossible;)