[
http://jira.jboss.com/jira/browse/JBWS-1324?page=all ]
Thomas Diesler updated JBWS-1324:
---------------------------------
Fix Version/s: jbossws-2.0.3
(was: jbossws community contributions)
Darran sais:
At the moment the Jira issue has been deferred to 'jbossws community
contributions' but it is a recurring issue for customers.
I think we either need to fix this properly and make sure delivery to
the MDB is delayed until after the endpoint is fully deployed - or we
can put in a small fix to check the status of the endpoint and add code
to sleep while the endpoint status is 'CREATED' before letting the
message through.
JMS Endpoint - Message delivery starts before endpoint is ready.
----------------------------------------------------------------
Key: JBWS-1324
URL:
http://jira.jboss.com/jira/browse/JBWS-1324
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-jaxws
Affects Versions: jbossws-1.0.3
Reporter: Darran Lofthouse
Assigned To: Alejandro Guizar
Fix For: jbossws-2.0.3
For most endpoints we need the EJB to be initialised before we initialise the web
service, this way we know the session bean will be ready to process requests before the
first request from a client is received.
For message driven beans we need the web service to be initialised before the first
message is processed by the MDB, however the same logic is used as is used for session
beans so it is possible that the first message will be received while the web service is
still being initialised.
12:53:51,277 ERROR [SOAPFaultHelperJAXRPC] SOAP request exception
javax.xml.rpc.soap.SOAPFaultException: Endpoint cannot handle requests in state: CREATED
at
org.jboss.ws.core.server.ServiceEndpoint.processRequest(ServiceEndpoint.java:176)
at
org.jboss.ws.integration.jboss42.jms.JMSMessageDispatcher.dipatchMessage(JMSMessageDispatcher.java:94)
at
org.jboss.ws.integration.jboss42.jms.JMSTransportSupport.processSOAPMessage(JMSTransportSupport.java:139)
at
org.jboss.ws.integration.jboss42.jms.JMSTransportSupport.onMessage(JMSTransportSupport.java:101)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.invocation.Invocation.performCall(Invocation.java:359)
at
org.jboss.ejb.MessageDrivenContainer$ContainerInterceptor.invoke(MessageDrivenContainer.java:495)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira