S3_PING does not work with JBoss EAP 7
Issue
The following message is logged in server.log
when starting JBoss EAP 7 with S3_PING
settings and unable to join the cluster.
07:05:53,222 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 78) MSC000001: Failed to start service org.wildfly.clustering.jgroups.channel.ee: org.jboss.msc.service.StartException in service org.wildfly.clustering.jgroups.channel.ee: java.lang.IllegalStateException: java.io.IOException: bucket 'https://<my-backet-name>.s3.ap-northeast-1.amazonaws.com' could not be accessed (rsp=400 (Bad Request). Maybe the bucket is owned by somebody else or the authentication failed
at org.wildfly.clustering.service.FunctionalService.start(FunctionalService.java:66)
at org.wildfly.clustering.service.AsyncServiceConfigurator$AsyncService.lambda$start$0(AsyncServiceConfigurator.java:117)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
at java.lang.Thread.run(Thread.java:750)
at org.jboss.threads.JBossThread.run(JBossThread.java:513)
Caused by: java.lang.IllegalStateException: java.io.IOException: bucket 'https://<my-backet-name>.s3.ap-northeast-1.amazonaws.com' could not be accessed (rsp=400 (Bad Request). Maybe the bucket is owned by somebody else or the authentication failed
at org.jboss.as.clustering.jgroups.subsystem.ChannelServiceConfigurator.get(ChannelServiceConfigurator.java:116)
at org.jboss.as.clustering.jgroups.subsystem.ChannelServiceConfigurator.get(ChannelServiceConfigurator.java:58)
at org.wildfly.clustering.service.FunctionalService.start(FunctionalService.java:63)
... 7 more
Caused by: java.io.IOException: bucket 'https://<my-backet-name>.s3.ap-northeast-1.amazonaws.com' could not be accessed (rsp=400 (Bad Request). Maybe the bucket is owned by somebody else or the authentication failed
at org.jgroups.protocols.S3_PING$AWSAuthConnection.checkBucketExists(S3_PING.java:494)
at org.jgroups.protocols.S3_PING.init(S3_PING.java:100)
at org.jgroups.stack.ProtocolStack.initProtocolStack(ProtocolStack.java:854)
at org.jgroups.stack.ProtocolStack.init(ProtocolStack.java:842)
at org.jgroups.JChannel.<init>(JChannel.java:164)
at org.jboss.as.clustering.jgroups.JChannelFactory.createChannel(JChannelFactory.java:116)
at org.jboss.as.clustering.jgroups.subsystem.ChannelServiceConfigurator.get(ChannelServiceConfigurator.java:96)
... 9 more
Environment
- Red Hat JBoss Enterprise Application Platform (EAP)
- 7
- S3_PING
- AWS
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.