axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Davanum Srinivas (JIRA)" <>
Subject [jira] Commented: (AXIS2-2268) JRE6 + Java Web Start + Axis 2 v1.1.1 causes a thread to hang unexpectedly
Date Thu, 24 May 2007 14:53:16 GMT


Davanum Srinivas commented on AXIS2-2268:

Could you please try Axis2 1.2? and let us know if you still see this problem.


> JRE6 + Java Web Start  + Axis 2 v1.1.1 causes a thread to hang unexpectedly
> ---------------------------------------------------------------------------
>                 Key: AXIS2-2268
>                 URL:
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: databinding, deployment
>    Affects Versions: 1.1.1
>         Environment: Windows XP SP2, Java SE 6 build 1.6.0-b105
>            Reporter: Chris Gibbs
> I have encountered a bizarre problem which seems to surface occasionally when using a
combination of Java Web Start for Java SE 6 , Axis 2 v1.1.1 and the Betfair API. I am using
Axis 2 in xmlbeans mode, and it is one Betfair API call in particular which is messing up,
although the problem seems to lie either in JWS or in Axis 2.
> Approximately 10-20% of the time, a call to the login() call of the Betfair API from
a Java desktop app deployed via Java Web Start hangs at least one of the threads depending
on API services. Here is a stack trace of the guilty thread:
> ------------------
> "Timer 0" prio=6 tid=0x044ba400 nid=0x980 runnable [0x05fce000..0x05fcfb94]
>   java.lang.Thread.State: RUNNABLE
>    at java.util.HashMap.put(Unknown Source)
>    at com.sun.deploy.cache.CacheEntry.readManifest(Unknown Source)
>    at com.sun.deploy.cache.CacheEntry.readManifest(Unknown Source)
>    at com.sun.deploy.cache.CacheEntry.access$300(Unknown Source)
>    at com.sun.deploy.cache.CacheEntry$ Source)
>    at Method)
>    at com.sun.deploy.cache.CacheEntry.getJarFile(Unknown Source)
>    at Source)
>    at Source)
>    at com.sun.jnlp.JNLPClassLoader$ Source)
>    at Method)
>    at com.sun.jnlp.JNLPClassLoader.getJarFile(Unknown Source)
>    at com.sun.jnlp.JNLPCachedJarURLConnection.connect(Unknown Source)
>    at com.sun.jnlp.JNLPCachedJarURLConnection.getInputStream(Unknown Source)
>    at Source)
>    at java.lang.ClassLoader.getResourceAsStream(Unknown Source)
>    at org.apache.xmlbeans.impl.schema.SchemaTypeLoaderImpl.crackEntry(
>    at org.apache.xmlbeans.impl.schema.SchemaTypeLoaderImpl.typeSystemForComponent(
>    at org.apache.xmlbeans.impl.schema.SchemaTypeLoaderImpl.findDocumentTypeRef(
>    at org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.findDocumentType(
>    at
>    at
>    at
>    - locked <0x24903288> (a
>    at org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(
>    at com.betfair.www.publicapi.v3.bfglobalservice.LoginResponseDocument$Factory.parse(Unknown
>    at com.betfair.www.publicapi.v3.bfglobalservice.BFGlobalServiceStub.fromOM(Unknown
>    at com.betfair.www.publicapi.v3.bfglobalservice.BFGlobalServiceStub.login(Unknown
> ------------
> This then results in 100% CPU usage, and the only solution is to then close the program
and restart it. Quite often there is more than 1 thread stuck in a similar situation to the
one above, so perhaps they are all waiting on java.util.HashMap.put(), not sure. This may
be purely a bug in JWS, but I submitted it here just in case. 
> Unfortunately I'm only creating the bug at the moment using the Betfair API (
and my Betfair account, so if you have a Betfair account let me know and I can give your account
permission to access the Betfair API using my application.
> You can access the WSDL for the Betfair API at :
> The API call which is causing problems is Login(). The structure of the WSDL file appears
to be correct, and all other Betfair API calls are working correctly.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message