We Keep Coding

Java AsyncContext start Runnable

I've created a Java servlet which does the following:
final AsyncContext aContext = request.startAsync();
aContext.start(new Runnable() {
public void run() {
HttpServletResponse response = (HttpServletResponse) aContext.getResponse();
try {
performRequest(proxyRequest, response);
} catch (IOException e) {
LOGGER.debug("IO Exception: " + e.getLocalizedMessage());
} catch (ServletException e) {
jsonResponse.append("ERROR", "Servlet Exception: " + e.getLocalizedMessage());
}
aContext.complete();
responseWriter.print(jsonResponse);
}
});
This servlet is called by a front-end UI which performs an AJAX call passing on some huge dataset.
The java servlet runs the method performRequest which can take up to a few minutes (on huge dataset).
I would like the servlet to return fast (the asynch process is triggered right away) otherwise the AJAX promise fails after 30 seconds wait.
What can I do?

Wait and notify on an object not working as I expected

I have a java servlet and am using jetty. On receiving a POST request, I am trying to send out another request to a different service. Upon receiving a response from the other service, I want to wake up my thread and continue sending the response. I am trying to use an object 'lock' to wait and notify. Can anyone tell why my thread doesn't wake up on lock.wait()?
#Override
protected void doPost(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {
response.setContentType("application/json");
response.setStatus(HttpServletResponse.SC_OK);
Object lock = new Object();
client.newRequest("http://localhost:3699/create")
.method(HttpMethod.POST)
.content(new StringContentProvider(ServletUtils.extractRequestBody(request)))
.send(new BufferingResponseListener() {
#Override
public void onComplete(Result result) {
ServletUtils.forwardResponse(response, result, getContentAsString());
System.out.println("NOTIFY");
synchronized (lock) {
lock.notifyAll();
}
System.out.println("DONE NOTIFICATION");
}
});
try {
System.out.println("WAIT");
lock.wait();
System.out.println("DONE WAITING");
} catch (InterruptedException e) {
ServletUtils.badRequest(response);
}
}
My print statements say
WAIT
WAIT
NOTIFY
DONE NOTIFICATION
a) I'm not sure why I get 2 WAIT
b) I don't get to DONE WAITING

HTML5 Server Sent Event Servlet on Tomcat 7 buffers events until socket close

I'm trying to add a server side event servlet to my web application. Below is the code for my servlet: ( Several different versions )
Using getOutputStream():
#WebServlet(urlPatterns = {"/hello"}, asyncSupported = true)
public class HelloServlet extends HttpServlet
{
private static final long serialVersionUID = 2889150327892593198L;
public void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException
{
response.setContentType("text/event-stream");
response.setHeader("Cache-Control", "no-cache");
response.setHeader("Connection", "keep-alive");
response.setCharacterEncoding("UTF-8");
ServletOutputStream out = response.getOutputStream();
try{
for(int i=0; i<10; i++) {
out.print("id: "+ i +"\n");
out.print("data: "+ System.currentTimeMillis() +"\n\n");
out.flush();
response.flushBuffer();
System.out.println("time sent:"+ System.currentTimeMillis());
System.out.println("IsCommitted:" + response.isCommitted() );
Thread.sleep(1000);
}
}
catch(Exception e)
{
e.printStackTrace();
}
out.close();
}
}
Using PrintStream:
public void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException
{
response.setContentType("text/event-stream");
response.setHeader("Cache-Control", "no-cache");
response.setHeader("Connection", "keep-alive");
response.setCharacterEncoding("UTF-8");
PrintWriter writer = response.getWriter();
try{
for(int i=0; i<10; i++) {
writer.write("id: "+ i +"\n");
writer.write("data: "+ System.currentTimeMillis() +"\n\n");
writer.flush();
response.flushBuffer();
System.out.println("time sent:"+ System.currentTimeMillis());
System.out.println("IsCommitted:" + response.isCommitted() );
Thread.sleep(1000);
}
}
catch(Exception e)
{
e.printStackTrace();
}
writer.close();
}
An Async Version using https://github.com/mariomac/jeasse
SseDispatcher dispatcher = null;
#Override
protected void doGet(HttpServletRequest req, HttpServletResponse resp) throws ServletException, IOException
{
System.out.println("test started. Async mode.");
startThread();
dispatcher = new SseDispatcher(req).ok().open();
}
private void startThread()
{
Thread thread = new Thread()
{
#Override public void run()
{
System.out.println("Thread started");
try {
for(int i=0; i<10; i++)
{
System.out.println("Sending message " + i);
onGivenEvent("message"+1, System.currentTimeMillis()+"" ) ;
Thread.sleep(1000);
}
} catch (Exception e) {
e.printStackTrace();
}
dispatcher.close();
System.out.println("Thread ending");
}
};
thread.setDaemon(true);
thread.setName("testsse");
thread.start();
System.out.println("Starting thread");
}
public void onGivenEvent(String eventName, String data) throws IOException
{
if( dispatcher != null)
{
dispatcher.send(eventName, data);
}
}
For all version I'm using curl to validate it:
curl -i -H "Accept: application/json" -X GET http://localhost:8080/testsse/hello
The output only comes at the end when the connection is closed by the server. If the servlet does not close the connection you never get the output.
I need the events to arrive after the server sends them, and not when the connection is closed. What am I doing wrong? This cannot be the way its supposed to work.
I've googled and tried many examples and they all suffer from this same issue.
I've tried many different versions of tomcat 7.0.67, 7.0.34, 7.0.62. I'm using 64 bit version of JDK 8.0.65 on Windows or JDK 8.0.45 on Linux.
Does anyone have this working? What am I doing wrong?

I figured out a solution to this. I switched to using Jersey SSE and it functions as expected.
I could never get the above solution to function correctly. The Server buffered all the IO until the connection closed. I tried all kinds of flushing and manipulating the buffer size.
Hopefully this helps... Start with another framework such as Jersey SSE.

Android Okhttp asynchronous calls

I am attempting to use the Okhttp library to connect my android app to my server via API.
My API call is happening on a button click and I am receiving the following android.os.NetworkOnMainThreadException. I understand that this is due the fact I am attempting network calls on the main thread but I am also struggling to find a clean solution on Android as to how make this code use another thread (async calls).
#Override
public void onClick(View v) {
switch (v.getId()){
//if login button is clicked
case R.id.btLogin:
try {
String getResponse = doGetRequest("http://myurl/api/");
} catch (IOException e) {
e.printStackTrace();
}
break;
}
}
String doGetRequest(String url) throws IOException{
Request request = new Request.Builder()
.url(url)
.build();
Response response = client.newCall(request).execute();
return response.body().string();
}
Above is my code, and the exception is being thrown on the line
Response response = client.newCall(request).execute();
I've also read that Okhhtp supports Async requests but I really can't find a clean solution for Android as most seem to use a new class that uses AsyncTask<>?

To send an asynchronous request, use this:
void doGetRequest(String url) throws IOException{
Request request = new Request.Builder()
.url(url)
.build();
client.newCall(request)
.enqueue(new Callback() {
#Override
public void onFailure(final Call call, IOException e) {
// Error
runOnUiThread(new Runnable() {
#Override
public void run() {
// For the example, you can show an error dialog or a toast
// on the main UI thread
}
});
}
#Override
public void onResponse(Call call, final Response response) throws IOException {
String res = response.body().string();
// Do something with the response
}
});
}
& call it this way:
case R.id.btLogin:
try {
doGetRequest("http://myurl/api/");
} catch (IOException e) {
e.printStackTrace();
}
break;

When response is delivered to client in asynchronous Servlets?

I'm having problems understanding how asynchronous servlets work, and in general how servlets deliver their response to the client.
What I'm trying to do is upload a video to a servlet via ajax. I thought that using an async servlet, I would obtain the response immediately in my browser and then the long task would be done in another thread.
I post my initial code here, before any code is written for file process, just an initial servlet to test asynchronism.
#WebServlet(name = "VideoUploader", urlPatterns = {"/VideoUploader"},
asyncSupported = true)
#MultipartConfig
public class VideoUploader extends HttpServlet {
#Override
protected void doGet(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {
doPost(request, response);
}
#Override
protected void doPost(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {
final PrintWriter pw = response.getWriter();
final AsyncContext ac = request.startAsync();
ac.setTimeout(80000);
ac.addListener(new AsyncListener() {
#Override
public void onComplete(AsyncEvent event) throws IOException {
System.out.println("On complete");
}
#Override
public void onTimeout(AsyncEvent event) throws IOException {
System.out.println("On timeout");
}
#Override
public void onError(AsyncEvent event) throws IOException {
System.out.println("On error");
}
#Override
public void onStartAsync(AsyncEvent event) throws IOException {
System.out.println("On start async");
}
});
ac.start(new Runnable() {
#Override
public void run() {
for (int i = 0; i <= 10; i++) {
System.out.println("Async task: "
+ Thread.currentThread().getName());
try {
Thread.sleep(1000);
} catch (InterruptedException e) {
}
}
ac.complete();
}
});
pw.write("end");
pw.close();
}
}
Then, the client part is:
<form id="formVideo">
<label for="videoFile">Vídeo:</label>
<input id="videoFile" name="videoFile" type="file" /> <br/>
<input id="uploadVideoBtn" type="button" value="Subir" onClick="uploadVideo();"/>
</form>
<div id="notificaciones"/>
<script type="text/javascript">
function uploadVideo() {
var file = document.getElementById("videoFile").files[0];
var formdata = new FormData();
formdata.append("file", file);
var xhr = new XMLHttpRequest();
xhr.open("POST","/webapp/VideoUploader", true);
xhr.send(formdata);
xhr.onload = function(e) {
if (this.status == 200) {
alert(this.responseText);
}
};
}
</script>
When I didn't attach a video to the file input, the process is done as I expected, the response is immediately received in the browser. But when I attached a file of any size, my browser doesn't receive the response until the other thread is over.
I was researching on non blocking IO, but I'm not sure if it has something to do with this behaviour or not.
I'm still not sure how I want to implement this, although I'll listen to any advice, but what I would like is to understand the behaviour of this asynchronous servlets.

it is obivious, your browser will wait until the other thread completes. The following steps involved
Client Sent Request to Server
Server allocates Thread (Servlet Container) from ThreadPool
Servlet container creates Servlet instance / reuse existisng Servlet instance and invoke Servcie method in (Servlet Thread)
With in Service method by calling startAsync() will start new thread and pass the request,response instances to the new Thread to process the request note** New Thread is not blocking the http connection , it is just a thread in the jvm which is not bliocking any IO at this moment
Servlet Thread exists service method and returned to thread pool Note** here Response not yet sent to Client / Browser
Once the Process started in step 4 completed that thread will request Servlet Container to allocate to new Servlet thread to send the respond back to Client.
Only the at Step 6 the response will return back to Client. So there is no difference between the normal request and with "asyncSupported = true" from client point of view. Servlet 3.0 supports Threads per request by using "asyncSupported = true" instead of Thread per connection. Thread per connection will cause Thread Starvation.
#WebServlet(name = "VideoUploader", urlPatterns = { "/VideoUploader" }, asyncSupported = true)
#MultipartConfig
public class VideoUploader extends HttpServlet {
#Override
protected void doGet(HttpServletRequest request,
HttpServletResponse response) throws ServletException, IOException {
doPost(request, response);
}
#Override
protected void doPost(HttpServletRequest request,
HttpServletResponse response) throws ServletException, IOException {
final AsyncContext ac = request.startAsync();
ac.setTimeout(80000);
ac.addListener(new AsyncListener() {
public void onComplete(AsyncEvent event) throws IOException {
System.out.println("On complete");
}
public void onTimeout(AsyncEvent event) throws IOException {
System.out.println("On timeout");
}
public void onError(AsyncEvent event) throws IOException {
System.out.println("On error");
}
public void onStartAsync(AsyncEvent event) throws IOException {
System.out.println("On start async");
}
});
ac.start(new Runnable() {
public void run() {
System.out.println("Async task: "
+ Thread.currentThread().getName());
try {
for (Part part : ((HttpServletRequest) ac.getRequest())
.getParts()) {
System.out.println("File received"); // You Should write
// file here
// like
// part.write("fileName");
}
} catch (IOException e1) {
e1.printStackTrace();
} catch (ServletException e1) {
e1.printStackTrace();
}
ac.complete();
PrintWriter pw = null;
try {
pw = ac.getResponse().getWriter();
} catch (IOException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
pw.write("end");
pw.close();
}
});
}
}

Asynchronous servlet hands over the long running server side job to a different server thread. Non-Blocking IO, a new feature in servlet 3.1, deals with situation when incoming data is blocking or streamed slower than the server can read. Both are solutions to avoid servlet thread starvation. They are not about returning response to client immediately.
Since you are using Ajax, not a regular browser file upload, it should be easily implemented at the Ajax side with even a synchronous servlet, if you do not care about servlet thread starvation. Ajax is asynchronous in nature. Here is an example tutorial
http://www.javabeat.net/asynchronous-file-upload-using-ajax-jquery-progress-bar-and-java/