Skip to main content

Spring support in JAX-WS

87 replies [Last post]

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
gregster
Offline
Joined: 2007-04-25
Points: 0

org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line 91 i
n XML document from ServletContext resource [/WEB-INF/HistoricalData.xml] is inv
alid; nested exception is org.xml.sax.SAXParseException: cvc-complex-type.2.4.a:
Invalid content was found starting with element 'wss:bindings'. One of '{"http:
//jax-ws.dev.java.net/spring/servlet":service, WC[##other:"http://jax-ws.dev.jav
a.net/spring/servlet"]}' is expected.
Caused by:
org.xml.sax.SAXParseException: cvc-complex-type.2.4.a: Invalid content was found
starting with element 'wss:bindings'. One of '{"http://jax-ws.dev.java.net/spri
ng/servlet":service, WC[##other:"http://jax-ws.dev.java.net/spring/servlet"]}' i
s expected.

Hey I get the following when having jaxws2.1 jaxws-spring-1-4.jar in my path.

Any ideas?

Regards,

Nick

kohsuke
Offline
Joined: 2003-06-09
Points: 0

It looks like Spring is complaining that your document doesn't match with the schema. Can you paste the portion that it's complaining? (around line 91)

laonda
Offline
Joined: 2007-04-24
Points: 0

I tried to get the example JAX-WS working on RAD7 but i am getting to following error:

Exception caught while initializing context
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name '(inner bean)': FactoryBean threw exception on object creation; nested exception is java.lang.NoSuchMethodError: com/sun/xml/bind/api/JAXBRIContext.newInstance([Ljava/lang/Class;Ljava/util/Collection;Ljava/util/Map;Ljava/lang/String;ZLcom/sun/xml/bind/v2/model/annotation/RuntimeAnnotationReader;)Lcom/sun/xml/bind/api/JAXBRIContext;
Caused by: java.lang.NoSuchMethodError: com/sun/xml/bind/api/JAXBRIContext.newInstance([Ljava/lang/Class;Ljava/util/Collection;Ljava/util/Map;Ljava/lang/String;ZLcom/sun/xml/bind/v2/model/annotation/RuntimeAnnotationReader;)Lcom/sun/xml/bind/api/JAXBRIContext;

As far as i can see it is missing the boolean c14nSupport in the call. I can't see how this is possible? Anyone some ideas. I am using the stockQuote example that has been provided.

kohsuke
Offline
Joined: 2003-06-09
Points: 0

I suspect you have an old JAXB RI.

Maybe you are picking it up from the parent classloader inside containers. What container do you run?

laonda
Offline
Joined: 2007-04-24
Points: 0

Thanks for the advice.

It was indeed a class loader problem. I changed the classloader to parent last and the server started up.

The problem is that if the classloader with the below settings it cant find the servlet: Stack Dump = javax.servlet.UnavailableException: SRVE0201E: Servlet [com.sun.xml.ws.transport.http.servlet.WSSpringServlet]: not a servlet class

* Server-specific Application Settings is on multiple, parent last
* Application it self is on application class loader first, single class loader for application
* Module is on application class loader first

I tried several settings but none seems to work. I found a simelar problem http://forum.springframework.org/showthread.php?t=33663 that advise to set the server-specific application setting to single. This will cause the admin consol to crash in my case. So thats not realy a solution. I will continue my search on this problem.

I removed the servlet-api-2.5.jar so it can use the websphere provided jar. If so i am getting a VerifyError:

Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name '(inner bean)': FactoryBean threw exception on object creation; nested exception is java.lang.VerifyError
Caused by: java.lang.VerifyError

The post http://forums.java.net/jive/message.jspa?messageID=193093 defines the same problem. So it is probably a websphere issue.

Message was edited by: laonda

ullenboom
Offline
Joined: 2005-09-01
Points: 0

Hi. I want to take a shot at this example (https://jax-ws-commons.dev.java.net/spring/) but got a nasty NPE. Together with the different hints for jars and schemas I now have a web project with

- spring.jar
- commons-logging.jar
- jaxb-imp.jar
- jaxw-api.jar
- jaxws-rt.jar
- jaxws-spring-1.1.jar
- xbean-spring-2.8.jar

in my web app class path. The runtime is Java SE 6, Tomcat 5.5 and the latest jax-ws 2.1.

My bean is simple:

package com.tutego.service;

public class GreeterService
{
public String greet( String name )
{
return "Hello " + name + "!";
}
}

And web.xml is standard too:


xmlns="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
SpringWeb

index.html
index.htm
index.jsp
default.html
default.htm
default.jsp

contextConfigLocation /WEB-INF/applicationContext.xml

org.springframework.web.context.ContextLoaderListener


jaxws-servlet

com.sun.xml.ws.transport.http.servlet.WSSpringServlet


jaxws-servlet
/greet

The applicationContext.xml follows the suggestions with the namespace.

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:ws="http://jax-ws.dev.java.net/spring/core"
xmlns:wss="http://jax-ws.dev.java.net/spring/servlet"
xsi:schemaLocation="
http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
http://jax-ws.dev.java.net/spring/core http://jax-ws.dev.java.net/spring/core.xsd
http://jax-ws.dev.java.net/spring/servlet http://jax-ws.dev.java.net/spring/servlet.xsd">

impl="com.tutego.service.GreeterService" />





I thought this will be fine, but *boom*

INFO: Destroying singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@10e35d5: defining beans [date,greeterService,jax-ws.http]; root of factory hierarchy
13.03.2007 12:59:50 org.springframework.web.context.ContextLoader initWebApplicationContext
SCHWERWIEGEND: Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jax-ws.http' defined in ServletContext resource [/WEB-INF/applicationContext.xml]: Cannot create inner bean 'wss:binding#caf6c1' of type [com.sun.xml.ws.transport.http.servlet.SpringBinding] while setting bean property 'bindings' with key [0]; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'wss:binding#caf6c1' defined in ServletContext resource [/WEB-INF/applicationContext.xml]: Cannot resolve reference to bean 'greeterService' while setting bean property 'service'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'greeterService': FactoryBean threw exception on object creation; nested exception is java.lang.NullPointerException
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'wss:binding#caf6c1' defined in ServletContext resource [/WEB-INF/applicationContext.xml]: Cannot resolve reference to bean 'greeterService' while setting bean property 'service'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'greeterService': FactoryBean threw exception on object creation; nested exception is java.lang.NullPointerException
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'greeterService': FactoryBean threw exception on object creation; nested exception is java.lang.NullPointerException
Caused by: java.lang.NullPointerException
at com.sun.xml.ws.server.EndpointFactory.getWsdlLocation(EndpointFactory.java:379)
at org.jvnet.jax_ws_commons.spring.SpringService.getObject(SpringService.java:280)
at org.springframework.beans.factory.support.AbstractBeanFactory.getObjectFromFactoryBean(AbstractBeanFactory.java:1226)
at org.springframework.beans.factory.support.AbstractBeanFactory.getObjectForBeanInstance(AbstractBeanFactory.java:1191)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:211)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:163)

Can anyone give me a hint?

Chris

kohsuke
Offline
Joined: 2003-06-09
Points: 0

The root cause of the problem is that your service endpoint class doesn't have @WebService annotation.

I fixed the spring support code to check for this error and report it.

ullenboom
Offline
Joined: 2005-09-01
Points: 0

Ah OK. I first thought the WS is really a "pure" POJO without any annotations like a class published with the JaxRpcPortProxyFactoryBean. I tried it with JSR 181 annotations before but got a lot of other Exceptions. Now it is clear for me. Thanks. I put a summary online under http://www.tutego.com/blog/javainsel/2007/03/jax-ws-21-with-spring-under....

plynch
Offline
Joined: 2006-08-20
Points: 0

Kohsuke,

What do you think of this:

https://glassfish.dev.java.net/issues/show_bug.cgi?id=2419

This issue stopped me from using jaxws-spring.

Glassfish developer is claiming the jaxws_commons-spring use of
com.sun.xml.ws.transport.http.servlet.WSServletDelegate

is not valid.

However I don't really have a work around for the stated exception.

Basically I could not get jaxws spring to work in Tomcat or Glassfish on JDK 1.6

..and if using WSServletDelegate in this way is not valid, where does that leave this project.

What one can do to get Spring working with jaxws is use the DefaultLocatorFactory model - although admittedly not that sexy it works.

kohsuke
Offline
Joined: 2003-06-09
Points: 0

Ah, so this is what that is all about.

Plynch, we've been puzzled why you are trying to use WSServletDelegate. You really should have mentioned the spring support upfront so that we know you are just creating a test case that reveals the essence of the problem.

What Bhakti and Dhiru are saying is that WSServletDelegate is not meant for developers out there. They are meant for projects like jax-ws-commons.

I'll reopen the issue and talk to Bhati.

rtiernay
Offline
Joined: 2006-03-16
Points: 0

Spring support for JAX-WS service endpoints seems to be working quite nicely.

However, is there a service client mechanism that would allow for spring to inject a port into a managed bean?

I suppose I'm looking for something like the XFire's
XFireClientFactoryBean (http://www.mail-archive.com/cxf-user@incubator.apache.org/msg00087.html)

jitu
Offline
Joined: 2003-06-14
Points: 0

There is already @WebServiceRef in the API and Java EE 5 injects those into the managed beans. Probably we could use the spring to do it.

kohsuke
Offline
Joined: 2003-06-09
Points: 0

No, we don't have any leverage on Spring development to have them understand a JavaEE annotation.

kohsuke
Offline
Joined: 2003-06-09
Points: 0

A nice endorsement to what we are doing: http://blog.interface21.com/main/2007/02/16/suns-glassfish-embracing-spr...

Good to know that Spring people think we are on the right track.

plynch
Offline
Joined: 2006-08-20
Points: 0

FYI
Bad Javadoc in SpringService.java causes SAXParseException: White spaces are required between publicId and systemId
https://jax-ws-commons.dev.java.net/issues/show_bug.cgi?id=1

kohsuke
Offline
Joined: 2003-06-09
Points: 0

I thought this is an error that happens when XSD files are not packaged in the jar properly, or otherwise when Spring fails to resolve schema references locally.

Then Spring tries to fetch XSD from the remote website, which returns an error HTML page, and obviously it fails to parse as XML.

I applied your patch, but I thought the real fix is to upload the schemas to the website.

plynch
Offline
Joined: 2006-08-20
Points: 0

I did this
1. Download jaxws-spring-1.1.jar
2. Extract spring-jax-ws-core.xsd.html
3. Fix javadoc comments that are inserted into spring-jax-ws-core.xsd.html which contain unescaped '>'
4. Insert corrected spring-jax-ws-core.xsd.html back into jar file.
5. Try to load the test app war again with the new jar file included. It now works and doesn't throw the SAXParseException.

-Peter

willemsrb
Offline
Joined: 2007-02-08
Points: 0

Hi,

got it working (after a few hours hitting my keyboard ;-)) and it is really super! Integration with Spring is working like a charm... We're now going from XFire to JAXWS (XFire had a big bug regarding soap headers)... Thanks Kohsuke!!!

However when i try to add a @HandlerChain(file="xxx") on my service implementation class the log gives the following warning:

[code]
Container org.jvnet.jax_ws_commons.spring.SpringService$ContainerWrapper@110ded doesn't support class com.sun.xml.ws.api.server.Module
[/code]

Any idea how to get this working? It works when not using Spring to configure the webservices... (the original sun-jaxws.xml file)

Thanks in advance....

Regards,Robert

kohsuke
Offline
Joined: 2003-06-09
Points: 0

The warning is not much to do with the handler chain, but I put a fix to this. I'll be releasing 1.1 now.

kohsuke
Offline
Joined: 2003-06-09
Points: 0
cmoesel
Offline
Joined: 2006-02-16
Points: 0

Kohsuke,

Again, thank you for all of your hard work and your promptness at fixing things. I don't know if you were asking me or Robert about being added as a developer. If you'd like to add me you may, but truthfully, I doubt I'd commit much at this point. But if I come across another easy fix like that, I'd certainly be happy to take care of it. It's up to you.

Unfortunately, it looks like you only pushed the 1.1 javadoc and schema to the maven repository. I expect you also intended to push out the jar?

-Chris

kohsuke
Offline
Joined: 2003-06-09
Points: 0

Apparently the push wasn't complete. I should be fixed now.
I added you as a developer, so feel free to make a quick fix like that.

cmoesel
Offline
Joined: 2006-02-16
Points: 0

Hello...

I'm trying to specify the primary WSDL, but am having a hard time doing so. In one of the pre-1.0 versions of the spring support extension, I think I was able to do it like this:




WEB-INF/wsdl/MyService.wsdl


I came to this solution via trial and error. Now, however, I get an error with the same config:
com.sun.xml.ws.server.ServerRtException: [failed to localize] cannot.load.wsdl(WEB-INF/wsdl/MyService.wsdl)

If I just switch the value to "MyService.wsdl" instead of "WEB-INF/wsdl/MyService.wsdl", I get a different error:
java.lang.IllegalArgumentException: Unknown type MyService.wsdl

Could you please advise on how to use this feature?

willemsrb
Offline
Joined: 2007-02-08
Points: 0

Looks like there was an 'else' forgetten in the code ;-):

public void setPrimaryWsdl(Object primaryWsdl) throws IOException {
if(primaryWsdl instanceof String) {
this.primaryWsdl = convertStringToSource((String)primaryWsdl);
} else
if(primaryWsdl instanceof URL) {
this.primaryWsdl = SDDocumentSource.create((URL)primaryWsdl);
} else
if(primaryWsdl instanceof SDDocumentSource) {
this.primaryWsdl = (SDDocumentSource) primaryWsdl;
}
throw new IllegalArgumentException("Unknown type "+primaryWsdl);
}

On settign a primaryWsdl the illegalArgumentException will always be thrown...

This code was from the 1.0-source jar

Regards,
Robert

cmoesel
Offline
Joined: 2006-02-16
Points: 0

Good catch, Robert.

Thanks for digging into the code-- I had taken a quick glance at it but somehow missed that the exception is always thrown (doh!). I guess I'll just recompile a new jar for it for now. Usually Kohsuke's pretty good about getting fixes in fast, so I suspect this will be in a nightly real soon.

Yet another thing... that could not have happened... if it was closed source!

Thanks again!
Chris

mieleton
Offline
Joined: 2007-02-06
Points: 0

Hi again ;)

I tried to deploy a web service, but JBoss infomrs that it can not locate schemas for the wss:bindings @ http://jax-ws.dev.java.net/spring/core.xsd?

kohsuke
Offline
Joined: 2003-06-09
Points: 0

The schema files should be inside our spring extension jar, and remote references will be redirected to your local copy.

But I should still copy these xsds to those locations. If you can file an issue for this in http://jax-ws-commons.dev.java.net/issues/ that would be very helpful.

cmoesel
Offline
Joined: 2006-02-16
Points: 0

I figured I'd also post the error I get when trying to build. If I run "mvn clean package" from the "jax-ws-commons/spring" directory, it fails on the tests.

Here's what it reports in "jax-ws-commons/spring/spring-core/target/surefire-reports/ToyTest.txt":

-------------------------------------------------------------------------------
Test set: ToyTest
-------------------------------------------------------------------------------
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.499 sec <<< FAILURE!
test1(ToyTest) Time elapsed: 0.483 sec <<< ERROR!
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jax-ws.http' defined in class path resource [config.xml]: Cannot create inner bean '(inner bean)' while setting bean property 'bindings' with key [0]; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name '(inner bean)' defined in class path resource [config.xml]: Cannot resolve reference to bean 'simplestService' while setting bean property 'service'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'simplestService': FactoryBean threw exception on object creation; nested exception is java.lang.NoSuchMethodError: com.sun.xml.stream.buffer.MutableXMLStreamBuffer.setSystemId(Ljava/lang/String;)V
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name '(inner bean)' defined in class path resource [config.xml]: Cannot resolve reference to bean 'simplestService' while setting bean property 'service'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'simplestService': FactoryBean threw exception on object creation; nested exception is java.lang.NoSuchMethodError: com.sun.xml.stream.buffer.MutableXMLStreamBuffer.setSystemId(Ljava/lang/String;)V
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'simplestService': FactoryBean threw exception on object creation; nested exception is java.lang.NoSuchMethodError: com.sun.xml.stream.buffer.MutableXMLStreamBuffer.setSystemId(Ljava/lang/String;)V
Caused by: java.lang.NoSuchMethodError: com.sun.xml.stream.buffer.MutableXMLStreamBuffer.setSystemId(Ljava/lang/String;)V
at com.sun.xml.ws.server.WSDLGenResolver.getWSDL(WSDLGenResolver.java:97)
at com.sun.xml.ws.wsdl.writer.WSDLGenerator.doGeneration(WSDLGenerator.java:231)
at com.sun.xml.ws.server.EndpointFactory.generateWSDL(EndpointFactory.java:407)
at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:178)
at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:420)
at org.jvnet.jax_ws_commons.spring.SpringService.getObject(SpringService.java:282)
at org.springframework.beans.factory.support.AbstractBeanFactory.getObjectFromFactoryBean(AbstractBeanFactory.java:994)
at org.springframework.beans.factory.support.AbstractBeanFactory.getObjectForBeanInstance(AbstractBeanFactory.java:960)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:256)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:156)
at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:246)
at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:128)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:955)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:729)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:416)
at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveInnerBeanDefinition(BeanDefinitionValueResolver.java:198)
at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:116)
at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveManagedList(BeanDefinitionValueResolver.java:266)
at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:132)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:955)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:729)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:416)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:245)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:141)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:242)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:156)
at ToyTest.test1(ToyTest.java:12)

kohsuke
Offline
Joined: 2003-06-09
Points: 0

Looks like there's some versioning issue withxmlstreambuffer.jar. Maybe we need to post a newer version there. Thanks for the info.

plynch
Offline
Joined: 2006-08-20
Points: 0

suppose a project would like to depend on springframework's module named 'spring-core' and also your spring project.

Then we see these jars side by side:
spring-core-1.0-SNAPSHOT.jar <-- jaxws-commons spring
spring-core-2.0.2.jar <-- part of official spring module

Rather confusing - suggest you change the name of your jar.

Looking forward to seeing this project working.

kohsuke
Offline
Joined: 2003-06-09
Points: 0

Ah, good point. Yeah, this is terrible.

I'll change the artifactId. Maybe jax-ws-spring, or something like that.

mieleton
Offline
Joined: 2007-02-06
Points: 0

Hi!

Thanks kohsuke for starting this spring - jax-ws support. I had just few days back started to test out how to combine those 2 when I found your blog about it ;)

One problem tho... I downloaded spring-core-1.0-SNAPSHOT.jar and spring-core-1.0.jar files to test with them but both of them came down as invalid jar/zip files for me.

Are they packaged with something special or might there be something wrong in the repository?

Location I tried to download from:
https://maven2-repository.dev.java.net/source/browse/maven2-repository/t...

mieleton
Offline
Joined: 2007-02-06
Points: 0

My bad, found out the correct files now ;)

Continuing my testing....

cmoesel
Offline
Joined: 2006-02-16
Points: 0

I'm running into a problem trying to use this. I downloaded the spring-core-1.0-SNAPSHOT.jar (revision 181) from the repository (still can't build correctly from mvn for some reason).

When I deploy my app, I get the following error:

11:36:02 ERROR ContextLoader - Context initialization failed
org.springframework.beans.factory.BeanDefinitionStoreException: Line 1 in XML document from ServletContext resource [/WEB-INF/applicationContext.xml] is invalid; nested exception is org.xml.sax.SAXParseException: White spaces are required between publicId and systemId.
Caused by:
org.xml.sax.SAXParseException: White spaces are required between publicId and systemId.

I found if I comment out the wss:bindings tag (and its descendants) in my applicationContext.xml file, it no longer complains.

Any ideas of what's going on?

kohsuke
Offline
Joined: 2003-06-09
Points: 0

The "White spaces are required between publicId and systemId." error happens when the jar doesn't contain the right schema files. This apparently happens if I run "mvn deploy" instead of "mvn clean deploy".

I must have pushed the wrong version to the repo.

kohsuke
Offline
Joined: 2003-06-09
Points: 0

(accidentally posted the same text twice)

kohsuke
Offline
Joined: 2003-06-09
Points: 0

I fixed the problem anthavio reported. It turns out that on web application Spring always validates (by XSD) the bean definition file, whereas my test bed didn't.

So this revealed several bugs that I haven't caught before as well as some bugs in XBean code --- XBean isn't apparently as stable as I'd like it to be (like https://issues.apache.org/jira/browse/XBEAN-73).

Anyway, things are back into the shape. The test application started running again.