Adam Warski

I think these attributes are not supported yet, hence the exception. Maybe unsupported attributes should be silently ignored even when setting, though this might be against the SQS spec. So...

@Drozenbo not yet, but maybe you'd like to try fixing the problem? If you'd have problems with the codebase I'll be happy to help

I assume that port is free?

It would be good to have some more logging :) Can you try running the server with `-Dlogback.configurationFile=custom.xml` where `custom.xml` is sth like this: ``` %d{HH:mm:ss.SSS} [%thread] %-5level %logger{36} -...

10s waiting for bind to complete is quite a long time ... is this happening when you frequently start/stop the server? Though the port should be freed quickly after being...

Yeah that looks correct ... btw there's a `PurgeQueue` method to remove all messages from a queue. I don't really have any ideas about the causes

Could you check 0.9.0-beta1? (https://s3-eu-west-1.amazonaws.com/softwaremill-public/elasticmq-server-0.9.0-beta1.jar) It uses a new HTTP backend so maybe something will change here.

@st9x3st9 Are you still seeing this also with 0.9.0-beta1?

@pliuchkin which version, and how are you exactly starting elasticmq?

@Kreinoee I think that's a separate issue, so please open a new one :)