How your config might break from 7.0 to 7.1

hibernal Nov 18, 2011 3:40 PM

Annoying but to be expected, I guess, configuration schema changes from 7.0 to 7.1 and configurations that worked now blow up. Things that I've found so far:

validation-time-minutes in datasource no longer parses: change to validation-time-millis ( feedback: this is annoying )

useFastFail in datasource no longer parses: change to use-fast-fail ( feedback: helpful move toward consistency in element naming and an ok reason to blow me up )

protocol type='VIEW_SYNC' no longer parses ( protocol deprecated or renamed? i wasn't actively using it but hadn't pruned unused protocols out of my test config yet ) delete protocol entry

ditto protocol type='pbcast.STREAMING_STATE_TRANSFER'

my working-in-7.0 domain config is barfing with the following but I don't yet know why:

java.util.NoSuchElementException: No child 'server-group' exists

digging....

1. Re: How your config might break from 7.0 to 7.1

hibernal Nov 18, 2011 3:52 PM (in response to hibernal)

weird. I think that bit is still schema compliant. maybe alpha2 build 18 is bust for domain mode?
Actions
2. Re: How your config might break from 7.0 to 7.1

jaikiran Nov 18, 2011 9:53 PM (in response to hibernal)

Please post the entire exception stacktrace and also the config file.
Actions
3. Re: How your config might break from 7.0 to 7.1

hibernal Dec 5, 2011 4:38 PM (in response to jaikiran)

Was away for a bit and retried with Beta2 and that is happy.
Actions

Go to original post