First call to JAX-WS web service is too slow

Question

Overview:

currently we have a web application with multiple module in it. We are using following technology stack

JAX-WS
Spring framework (except spring MVC)
JSF
Hibernate

Application Server: IBM Websphere 7.0 (Production), Apache Tomcat 7.0.X (Development) We are using JAX-WS annotations to mark a class as web service, beside this we don't use any JAXB annotation in Data Objects, we are leaving this task for ws runtime.

Problem statement:

Once we deploy application on Apache Tomcat, web service doesn't get published on AS. As a solution we need to add "org.springframework.remoting.jaxws.SimpleJaxWsServiceExporter" property in spring context file and then web service starts working perfectly. But when we deploy the application on WAS, web service gets publish without setting fore mentioned property. When we make first request to web service it respond slowly, during R&D of this issue we found following things;

IBM using AXIS2 Web service engine
JAXB implementation load classes like className_used_in_web_service_method$JaxbAccessorM_getFieldName_setFieldName_java_util_Set from: <unknown> for all the classes in hierarchy. This only happen first time. We were trying to load these at application start-up time, but couldn't succeeded. Can anyone please help us to tackle this issue?

rykhan · Answer 1 · 2013-01-19T10:36:37.243

0

try AxisServlet load-on-startup in web.xml

edited Jan 19 '13 at 10:36

answered Jan 07 '13 at 07:23

rykhan

309
4
15

3

this is more a comment than an answer to the question. – slfan Jan 07 '13 at 07:43
1

This does not provide an answer to the question. To critique or request clarification from an author, leave a comment below their post - you can always comment on your own posts, and once you have sufficient [reputation](http://stackoverflow.com/faq#reputation) you will be able to [comment on any post](http://stackoverflow.com/privileges/comment). – slfan Jan 07 '13 at 07:43
thanks slfan, it was infact a suggestion and question as well, but i didnot see any add comment option with post, so i added, but now i changed it, anyways thanks – rykhan Jan 19 '13 at 10:38

score 0 · Answer 2 · edited Jun 03 '13 at 20:45

0

Did you try using SimpleHttpServerJaxWsServiceExporter instead of SimpleJaxWsServiceExporter?

It seems that SimpleHttpServerJaxWsServiceExporter startup the webservice as soon as endpoint configurantion is fulfilled.

edited Jun 03 '13 at 20:45

Linus Caldwell

10,908
12
46
58

answered Mar 06 '13 at 19:57

Eduardo Briguenti Vieira

4,351
3
37
49

score 0 · Answer 3 · answered Nov 28 '13 at 13:56

You can create your own implementation of ServletContextListener

For example:

package kernel.flowcontrol;

import javax.servlet.ServletContextEvent;
import javax.servlet.ServletContextListener;

public class WsLifecycleListener implements ServletContextListener {
    @Override
    public void contextInitialized(ServletContextEvent servletContextEvent) {

    // some init work ...

    }

    @Override
    public void contextDestroyed(ServletContextEvent servletContextEvent) {}
}

And add it into web.xml:

<listener>
    <listener-class>kernel.flowcontrol.WsLifecycleListener</listener-class>
</listener>

First call to JAX-WS web service is too slow

Overview:

Problem statement:

3 Answers3