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

connection-timeout-seconds command rejected #33

Closed
OmpahDev opened this issue Jul 26, 2017 · 6 comments
Closed

connection-timeout-seconds command rejected #33

OmpahDev opened this issue Jul 26, 2017 · 6 comments

Comments

@OmpahDev
Copy link

Attempting to start up hazelcast has resulted in this error:
Caused by: com.hazelcast.config.InvalidConfigurationException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'connection-timeout-seconds'. One of '{"http://www.hazelcast.com/schema/config":iam-role, "http://www.hazelcast.com/schema/config":host-header, "http://www.hazelcast.com/schema/config":tag-key, "http://www.hazelcast.com/schema/config":tag-value}' is expected.

@mesutcelik
Copy link
Contributor

Hi @sshorkey ,

Can you please share your hazelcast.xml config?

@OmpahDev
Copy link
Author

            <aws enabled="true">
                <access-key>(redacted)</access-key>
                <secret-key>(redacted)</secret-key>
                <!--optional, default is us-east-1 -->
                <region>us-east-1</region>
                <security-group-name>(redacted)</security-group-name>
                <connection-timeout-seconds>60</connection-timeout-seconds>
            </aws>

@mesutcelik
Copy link
Contributor

mesutcelik commented Jul 26, 2017

Thx for the quick feedback. Can you please try as an attribute to aws tag?
<aws enabled="true" connection-timeout-seconds="60" >

@OmpahDev
Copy link
Author

Solved the problem. Thanks.

@mesutcelik
Copy link
Contributor

good to hear that!

We highly recommend to use Discovery SPI based configuration for future. please see the README
We will remove the support for the old configuration in future. cc: @mmedenjak

@mmedenjak
Copy link
Contributor

The old aws element will definitely be removed in hazelcast 4.0, I suggest you try out the discovery SPI version until then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants