Endpoint cannot handle requests in state: CREATED

[elmosca2]

Hi,

I am using a recent jboss-head build (last week), JDK5.0 and EJB3.

I am testing jbossws for the first time using jsr-181. I've created an EJB3 stateless bean with the corresponding annotations and its remote interface.

The service:

@WebService(name = "AdminService", targetNamespace = "http://this.test.com/service/AdminWebService", serviceName = "AdminWebService")
@PortComponent(contextRoot="/adminws", urlPattern="/*")
@Remote(AdminWebServiceRemote.class)
@RemoteBinding(jndiBinding = "/ejb3/AdminEJB3EndpointInterface")
@Stateless
public class AdminWebService implements AdminWebServiceRemote
{
 // some simple methods here

 @WebMethod
 public void method1() {
 // ...
 }

}

To test this I have a client and I generate the stubs using axis-wsdl2java. But, when I execute the test I get this axisFault:

Endpoint cannot handle requests in state: CREATED

Any ideas there?

[elmosca2]

I forgot to attach the exception from JBoss:

20:38:25,888 ERROR [ServiceEndpoint] SOAP request exception
javax.xml.rpc.soap.SOAPFaultException: Endpoint cannot handle requests in state: CREATED
 at org.jboss.ws.server.ServiceEndpoint.handleRequest(ServiceEndpoint.java:172)
 at org.jboss.ws.server.ServiceEndpointServlet.doPost(ServiceEndpointServlet.java:81)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
 at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:75)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
 at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
 at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
 at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:39)
 at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:156)
 at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:53)
 at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
 at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
 at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
 at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
 at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:868)
 at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744)
 at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
 at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
 at java.lang.Thread.run(Thread.java:595)

[thomas.diesler]

Have you looked at the server log to find out why the endpoint is not started?