[
https://jira.jboss.org/browse/JGRP-1218?page=com.atlassian.jira.plugin.sy...
]
Bela Ban resolved JGRP-1218.
----------------------------
Resolution: Done
The reason this failed was that the S3_PING code was using a stricter bucket name check
than the one in the AWS S3 console
S3_PING fails to create a bucket
--------------------------------
Key: JGRP-1218
URL:
https://jira.jboss.org/browse/JGRP-1218
Project: JGroups
Issue Type: Bug
Affects Versions: 2.6.15
Reporter: Brian Stansberry
Assignee: Bela Ban
Fix For: 2.6.16, 2.10
I tried to use S3_PING with a non-existent bucket configured, and channel creation
failed:
Caused by: java.lang.IllegalArgumentException: Invalid Bucket Name:
brian.stansberry-redhat.com_S3_PING
at org.jgroups.protocols.S3_PING$AWSAuthConnection.createBucket(S3_PING.java:248)
at org.jgroups.protocols.S3_PING.init(S3_PING.java:71)
at org.jgroups.stack.Configurator.initProtocolStack(Configurator.java:72)
at org.jgroups.stack.ProtocolStack.setup(ProtocolStack.java:299)
at org.jgroups.JChannel.init(JChannel.java:1578)
... 67 more
Saw this with 2.6.15 and with the 2.6.16 snapshot you gave me.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira