Category Archives: Errors

Playframework CRUD module error [admin module:crud]

Posted by on March 21, 2013 No comments

Including the playframework CRUD module but getting the error -

~ Invalid route definition : * admin module:crud

Solution:
The Controller objects has to be plural (must end with ‘s’). The controller’s class name has to be the model class name with a final ‘s’.

For example,  If we have Customer.java model object, the controller object extending CRUD must be Customer*s*.java

package controllers;

public class Customers extends CRUD {

}


Share|

RootCause for – java.io.IOException: Async IO operation failed, reason: RC: 76 A socket must be already connected

Posted by on June 10, 2012 No comments

API Webservice Error:

The below error occurs intermittently for you? Check the resolution given below

WebServicesFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
faultString: java.io.IOException: Async IO operation failed, reason: RC: 76 A socket must be already connected.
faultActor: null
faultDetail:

java.io.IOException: Async IO operation failed, reason: RC: 76 A socket must be already connected.

Resolution:

Set the com.ibm.websphere.webservices.http.connectionKeepAlive to false resolves the error messages

The client now honors the CLOSED value and will not attempt to re-use the connection.

RootCause:

The JAX-WS client was not honoring the CONNECTION HTTP header value of CLOSED and attempting to re-use the connection.

There could be some other causes for this.  If you know them. Please comment bel

Share|