Bug 1090762 - Increase default value of default orphanSafetyInterval periodic
Summary: Increase default value of default orphanSafetyInterval periodic
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Transaction Manager
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: tom.jenkinson
QA Contact: Ondrej Chaloupka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-24 06:25 UTC by Ondrej Chaloupka
Modified: 2017-10-10 00:07 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-05-07 14:00:16 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Ondrej Chaloupka 2014-04-24 06:25:07 UTC
Please, increase the default value of backoff period for recovery (PeriodicRecovery.java). Current value is 10 seconds.

The thing is that for the a bit more loaded app server (e.g. one MDB processing a bigger bunch of the messages) the log contains the errors from periodic recovery.

The symptoms are described here:
https://bugzilla.redhat.com/show_bug.cgi?id=1009981

The mentioned bugzilla added possibility to change the default value via system property. But the default property should be bigger to not getting the errors as "normal" behaviour. Maybe 30 seconds would be fine? (Not sure what is ok from your point of view).

We have some points from community forum that we are not only ones hitting this time to time. See https://community.jboss.org/thread/238152

Comment 1 tom.jenkinson 2014-04-24 16:48:40 UTC
Hi Ondra,

I think you need to increase the orphan safety threshold, rather than the backoff period. And I thought we had already increased that? If you have a log that fails let me take a look and make sure it is the same thing. Let me know the config you are using.

Thanks,
Tom

Comment 2 Ondrej Chaloupka 2014-05-05 09:22:30 UTC
Hi Tom,

sorry for the error.
The bz is aimed to increase the default orphan safety period.

We are still hitting that nasty log message during our tests. Do you think that the default timeout could be increased? Or you would not recommend it?

I know and I remember that we had quite a long discussion about these errors for last release but if you don't mind I want to ask once more is there some chance to get rid of them for good? I mean e.g for Narayana 6.0.0? Do we have some jira about it or may I create one?

Thanks
Ondra

Comment 3 tom.jenkinson 2014-05-07 13:57:10 UTC
Just adding a comment here so I remember I answered you on irc. You could increase that timeout to say 1 minute and that should be sufficient except under extreme load. If you still have the issue send me the logs and I can take a look at the timestamps to make sure I didn't miss anything.

Thanks!

Comment 4 Ondrej Chaloupka 2014-05-07 14:00:16 UTC
We (EAP QE) agreed that the default value of 20 seconds is reasonable so I'm closeing this as not a bug.

Just adding that the argument for EAP to redefine this is:
com.arjuna.ats.jta.orphanSafetyInterval


Note You need to log in before you can comment on or make changes to this bug.