Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The attempted blocking write is not allowed because the non-blocking I/O has already been started by the application registering the WriteListener #304

Open
xring opened this issue Mar 1, 2016 · 3 comments

Comments

@xring
Copy link

xring commented Mar 1, 2016

I'm using Play2.4 with Scala2.11 and play2war on IBM Bluemix with Liberty.

It seems that IBM updated their Bluemix platform on 9 Feb 2016, then my app do not work anymore.

I search the logs, there only one error message:

[ERROR ] SRVE0918E: The attempted blocking write is not allowed because the non-blocking I/O has already been started by the application registering the WriteListener [play.core.server.servlet31.Play2Servlet31RequestHandler$ResultWriteListener@15bfa0fc].

I want to know this happened due to my codes or due to the play2-war-plugin?

@yanns
Copy link
Member

yanns commented Mar 1, 2016

Just a guess: it seems that they are more than one application deployed in the container.
One application is the play app, using async IO, and the other app is using blocking IO.

@yespeebala
Copy link

I'm also facing same issue. It is working in WAS Liberty profile 8.5.5.7. But, When I deployed in WAS Liberty profile 8.5.5.9 or upgraded version. got same error like below.
[ERROR ] "SRVE0918E: The attempted blocking write is not allowed because the non-blocking I/O has already been started by the application registering the WriteListener [play.core.server.servlet31.Play2Servlet31RequestHandler$ResultWriteListener@38beb71d].”

@xring Have you found solution?

@xring
Copy link
Author

xring commented Mar 17, 2017

@yespeebala No, I still can not run Play2.4(or above) on Bluemix(Liberty based runtime). I used Akka-HTTP instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants