wildfly 8.0.0.cr1 s3ping doesnt create files in aws s3 bucket

[raghava.karthik.reddy.samireddy]

Am trying to get s3ping discovery method working in wildfly 8.0.0.cr1. I am using default Amazon Linux AMI and using chef to launch instances in ec2 based on this tutorial http://aws.typepad.com/awsaktuell/tutorial/. I have deployed a sample web app which is clustered. As of now i have a single node. But in the near future i'll be adding more nodes to the cluster..

I have modified the file standalone-full-ha.xml with the required s3 credentials(with "jboss" as IAM user and its secret and access keys ) and bucket details(manually created the bucket with full access permissions).

<subsystem xmlns="urn:jboss:domain:jgroups:2.0" default-stack="s3ping">
......
<stack name="s3ping">
   <transport type="TCP" socket-binding="jgroups-tcp" diagnostics-socket-binding="jgroups-diagnostics"/>
   <protocol type="S3_PING">
   <property name="access_key">
  XXXXXXXXXXXXXXXXXXX
   </property>
   <property name="secret_access_key">
  XXXXXXXXXXXXXXXXXXXXXXXX
   </property>
   <property name="prefix">
  jboss-config
   </property>
   <property name="timeout">
  60000
   </property>
   </protocol>
   <protocol type="MERGE2"/>
   <protocol type="FD_SOCK" socket-binding="jgroups-tcp-fd"/>
   <protocol type="FD"/>
   <protocol type="VERIFY_SUSPECT"/>
   <protocol type="BARRIER"/>
   <protocol type="pbcast.NAKACK"/>
   <protocol type="UNICAST2"/>
   <protocol type="pbcast.STABLE"/>
   <protocol type="pbcast.GMS"/>
   <protocol type="UFC"/>
   <protocol type="MFC"/>
   <protocol type="FRAG2"/>
   </stack>

Its getting started successfully and i can access the application. but am unable to see any node information file created inside this s3 bucket. All firewalls are off. Is there any other configuration i need to add to get it work?

[ctomc]

Did you try with anything newer? like 8.2.0.Final?

[raghava.karthik.reddy.samireddy]

update: I have manually launched wildfly 8.2.0.Final , i am able to use he admin console but still no luck, no file is created in s3 bucket.  Relevant part in standalone-ec2-full-ha.xml

<subsystem xmlns="urn:jboss:domain:jgroups:2.0" default-stack="tcp">

            <stack name="tcp">

                <transport type="TCP" socket-binding="jgroups-tcp"/>

                <protocol type="S3_PING">

                    <property name="access_key">xxxxxxxxxxxxx</property>

                    <property name="secret_access_key">xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx</property>

                    <property name="location">jboss-config</property>

                </protocol>

                <protocol type="MERGE2"/>

                <protocol type="FD_SOCK" socket-binding="jgroups-tcp-fd"/>

                <protocol type="FD"/>

                <protocol type="VERIFY_SUSPECT"/>

                <protocol type="pbcast.NAKACK2">

                    <property name="use_mcast_xmit">false</property>

                    <property name="use_mcast_xmit_req">false</property>

                </protocol>

                <protocol type="UNICAST3"/>

                <protocol type="pbcast.STABLE"/>

                <protocol type="pbcast.GMS"/>

                <protocol type="MFC"/>

                <protocol type="FRAG2"/>

                <protocol type="RSVP"/>

            </stack>

launched with ./standalone.sh -c standalone-ec2-full-ha.xml -Djboss.bind.address=0.0.0.0 -Djboss.bind.address.management=0.0.0.0&

[raghava.karthik.reddy.samireddy]

I was Successfully able to create use wildfly with s3 ping in domain controller mode and i'm able to see file created in s3 bucket.
I created a page here to describe the procedure in detail  >> Jboss Clustering in AWS – Karthik Reddy