Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Atlassian JIRA by Martin Meinhold, 1 year ago
EC2 instance i-ea9ed400 in an unexpected state pending (0) for reason []
via Atlassian JIRA by Martin Meinhold, 2 years ago
EC2 instance i-ea9ed400 in an unexpected state pending (0) for reason []
com.atlassian.aws.AWSException: EC2 instance i-ea9ed400 in an unexpected state pending (0) for reason []	at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.unexpectedStateException(RemoteEC2InstanceImpl.java:360)	at com.atlassian.aws.ec2.EC2InstanceState.handleState(EC2InstanceState.java:207)	at com.atlassian.aws.ec2.EC2InstanceState.access$100(EC2InstanceState.java:7)	at com.atlassian.aws.ec2.EC2InstanceState$3.supervise(EC2InstanceState.java:75)	at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.backgroundSupervise(RemoteEC2InstanceImpl.java:503)	at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.access$300(RemoteEC2InstanceImpl.java:39)	at com.atlassian.aws.ec2.RemoteEC2InstanceImpl$2.run(RemoteEC2InstanceImpl.java:112)	at com.atlassian.aws.ec2.RemoteEC2InstanceImpl$CatchingRunnableDecorator.run(RemoteEC2InstanceImpl.java:83)	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)	at java.lang.Thread.run(Thread.java:745)