Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[WFLY-12255 ][WFLY-951] adjustment of the fix for expiry scanner definition #12382

Merged
merged 1 commit into from Jul 11, 2019

Conversation

ochaloup
Copy link
Contributor

@ochaloup ochaloup commented Jun 24, 2019

https://issues.jboss.org/browse/WFLY-12255 (follow-up to https://issues.jboss.org/browse/WFLY-951)

By Narayana functionality the expiry scanner class name can be defined with shortened version of the property name or with property qualified with full class name.

@wildfly-ci wildfly-ci added the deps-ok Dependencies have been checked, and there are no significant changes label Jun 24, 2019
@kabir
Copy link
Contributor

kabir commented Jun 27, 2019

@ochaloup I see "RecoveryEnvironmentBean.expiryScannerClassNames shows up in the testsuite. Does it make sense to do a similar test for com.arjuna.ats.arjuna.common.RecoveryEnvironmentBean.expiryScannerClassNames?

https://issues.jboss.org/browse/WFLY-951 is very old, I think you should create a new issue following up on that one

@ochaloup
Copy link
Contributor Author

@kabir thanks for your points. I created a new jira and changed the commit description.
But I'm not sure about the testsuite. It's a Narayana specific feature which is tested in the Narayana testsuite. There is no test in WildFly testsuite that would touch this functionality. There is only one place where I can see the name and that's under {{iiop}} testsuite module but that configuration value has no influence on any test there.
If you don't mind I would leave this as functionality for Narayana unit testing. But if you think differently, please, let me know and I will create some.

@ochaloup ochaloup changed the title [WFLY-951] adjustment of the fix for expiry scanner definition [WFLY-12255 ][WFLY-951] adjustment of the fix for expiry scanner definition Jun 28, 2019
@bstansberry
Copy link
Contributor

@chengfang @tadamski Does the failure in https://ci.wildfly.org/viewLog.html?buildId=156858&buildTypeId=WF_PullRequest_LinuxSm indicate a problem in the EJB timer service handling? The stack trace looks like the code trying to persist the timer is failing.

I'm not sure why that only fails intermittently. Started failing on June 10.

https://ci.wildfly.org/project.html?projectId=WF_PullRequest&buildTypeId=&tab=testDetails&testNameId=-2932164008050579664&order=TEST_STATUS_DESC&branch_WF_PullRequest=__all_branches__&itemsCount=50

Not related to this PR.

@bstansberry bstansberry added the ready-for-merge Only for use by those with merge permissions! label Jun 28, 2019
@chengfang
Copy link
Contributor

@bstansberry the failure doesn't look like from ejb timer processing. It's failure to get timer db connection, which was in turn casued by security permission check. I guess it will pass if running without security manager. Not sure if it always fails with sm on. I'll create a separate issue to track it.

@ochaloup
Copy link
Contributor Author

ochaloup commented Jul 3, 2019

@kabir just by interest, is there something more to provide for this could be merged?

@darranl darranl merged commit 3c90841 into wildfly:master Jul 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
deps-ok Dependencies have been checked, and there are no significant changes ready-for-merge Only for use by those with merge permissions!
Projects
None yet
6 participants