Note that there are some explanatory texts on larger screens.

plurals
  1. PO503 error while connecting to my ec2 elastic beanstalk deployment
    primarykey
    data
    text
    <p>i deployed my war onto elastic beanstalk and I am running many connections from an outside pc onto the service trying to load test. </p> <p>I am getting this error</p> <pre><code>[ERROR] 2011-08-09 07:03:52,134 could not process CompanyBridgePromoResult </code></pre> <p>com.sun.jersey.api.client.UniformInterfaceException: POST [url] returned a response status of 503 at com.sun.jersey.api.client.WebResource.handle(WebResource.java:576) at com.sun.jersey.api.client.WebResource.access$300(WebResource.java:72) at com.sun.jersey.api.client.WebResource$Builder.post(WebResource.java:506) at com.icon.sa.ac.JerseyAdminClient.itemSearch(JerseyAdminClient.java:507) at com.icon.sa.bridge.google.GoogleShoppingFtpCompanyBridge.handle(GoogleShoppingFtpCompanyBridge.java:1) at com.icon.sa.bridge.BasicCompanyBridge$1.run(BasicCompanyBridge.java:86) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)</p> <p>I am running c3p0 as my connection pool. I cannot see any errors on the server and its healthy. </p> <p>Does amazon have a service to block out certain connections after too many connections from the same host? I tested locally I did not have any of these problems. </p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload