CreateQueue is not a valid action

143 views
Skip to first unread message

Chris

unread,
Dec 20, 2012, 4:55:25 PM12/20/12
to cmb-use...@googlegroups.com
I am getting this error both in the cns-worker and with the RESTful interface calls. Any ideas on what it might be or what I should check? I think I followed the github instructions well.

Software:
Redis-2.6.7
Cassandra 1.0.12
CMB versions 2.2.11 binary distributions
Oracle JRE 1.7.03
Apache tomcat 7.0.34

Below is the traceback from running the cns-worker:
...
2012-12-20 16:49:50,357 [cms] [main] [021dbac2-5da9-472c-a049-9a996d28f289] WARN  ValueAccumulator - Must initialize Accumulator before adding to counter with key=CassandraTime, not adding to the counter the new ammount=1
2012-12-20 16:49:50,357 [cms] [main] [021dbac2-5da9-472c-a049-9a996d28f289] WARN  ValueAccumulator - Must initialize Accumulator before adding to counter with key=CassandraTime, not adding to the counter the new ammount=0
2012-12-20 16:49:50,372 [cms] [main] [021dbac2-5da9-472c-a049-9a996d28f289] WARN  ValueAccumulator - Must initialize Accumulator before adding to counter with key=CassandraTime, not adding to the counter the new ammount=0
2012-12-20 16:49:50,372 [cms] [main] [021dbac2-5da9-472c-a049-9a996d28f289] INFO  RedisCachedCassandraPersistence - event=initializeInstance payloadCacheEnabled=true
2012-12-20 16:49:50,383 [cms] [main] [021dbac2-5da9-472c-a049-9a996d28f289] INFO  RedisCachedCassandraPersistence - event=redisInitializePool status=succesfull poolSize=1 maxActive=50
2012-12-20 16:49:50,432 [cms] [main] [021dbac2-5da9-472c-a049-9a996d28f289] WARN  ValueAccumulator - Must initialize Accumulator before adding to counter with key=CassandraWrite, not adding to the counter the new ammount=1
2012-12-20 16:49:50,436 [cms] [main] [021dbac2-5da9-472c-a049-9a996d28f289] WARN  ValueAccumulator - Must initialize Accumulator before adding to counter with key=CassandraTime, not adding to the counter the new ammount=53
2012-12-20 16:49:50,985 [cms] [main] [021dbac2-5da9-472c-a049-9a996d28f289] INFO  CNSEndpointPublisherJobProducer - event=initialize info=creating_missing_queue name=PublishJobQ_0
Exception in thread "main" Status Code: 400, AWS Service: AmazonSQS, AWS Request ID: 0794c712-50b2-4e23-91a5-761f2fc9601e, AWS Error Code: InvalidAction, AWS Error Message: CreateQueue is not a valid action
        at com.amazonaws.http.AmazonHttpClient.handleErrorResponse(AmazonHttpClient.java:583)
        at com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:317)
        at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:167)
        at com.amazonaws.services.sqs.AmazonSQSClient.invoke(AmazonSQSClient.java:812)
        at com.amazonaws.services.sqs.AmazonSQSClient.createQueue(AmazonSQSClient.java:678)
        at com.comcast.cns.tools.CNSEndpointPublisherJobProducer.initialize(CNSEndpointPublisherJobProducer.java:132)
        at com.comcast.cns.tools.CNSPublisher.main(CNSPublisher.java:90)

boriwo

unread,
Dec 20, 2012, 8:40:36 PM12/20/12
to cmb-use...@googlegroups.com
Are you using one or two instances of tomcat to host the cns and cqs service endpoints?
Typically you see this type of error message if you send cqs requests to the cns endpoint or vice versa (in this case CreateQueue is unknown to the cns service endpoint, only a cqs endpoint can handle this request). This can happen for one of the following reasons:

- you are trying to host both cns and cqs on the same tomcat instance and cqs "eats up" all requests (two distinct instances are much easier to configure)
- your cns worker is pointing to an incorrectly configured cmb.properties file (the cns and cqs service endpoints are configured near the top of the file)
- your cns/cqs service endpoints are pointing to an incorrectly configured cmb.properties file

Chris

unread,
Dec 21, 2012, 12:23:25 PM12/21/12
to cmb-use...@googlegroups.com
Thank you for the help. I had the ports reversed in the server.xml files of each tomcat instance. There are a few configuration files to juggle. The worker started up correctly now. Now time to test it all out.
Reply all
Reply to author
Forward
0 new messages