Re: [Opaltoolkit-users] Problem reloading opal

[Luca C. <lcl...@uc...>]

Anthony Bretaudeau wrote:
> Hi,
> Now that I use the stop opal webapp, wait a minute and then restart it I
> no longer have this HSQLDB problem (although I still get this when stopping:
> Exception in thread "HSQLDB Timer @4e8890da" java.lang.NullPointerException
>     at org.hsqldb.lib.HsqlTimer.nextTask(Unknown Source)
>     at org.hsqldb.lib.HsqlTimer$TaskRunner.run(Unknown Source)
>     at java.lang.Thread.run(Thread.java:595)
> )
> 

Anthony,
you can ignore this error.

> However, I still have a problem: services are usually not accessible
> after restarting. I get this kind of error message from clients:
> 

There is a problem in your configuration, but this is a very generic 
error message.


What kind of jobmanager are you using?
Can you try to issue one last, ant clean, ant install?

Can you send me the $CATALINA_HOME/logs/catalina.out?


Sincerely,
Luca


> Exception in thread "main" AxisFault
>  faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
>  faultSubcode:
>  faultString: java.lang.reflect.InvocationTargetException
>  faultActor:
>  faultNode:
>  faultDetail:
>     {http://xml.apache.org/axis/}hostname:genoweb3
> 
> java.lang.reflect.InvocationTargetException
>     at
> org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:221)
>     at
> org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:128)
>     at
> org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
>     at
> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:604)
>     at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocumentFragmentScannerImpl.java:1750)
>     at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2906)
>     at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:624)
>     at
> com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:116)
>     at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:486)
>     at
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:810)
>     at
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:740)
>     at
> com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:110)
>     at
> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1208)
>     at
> com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:525)
>     at javax.xml.parsers.SAXParser.parse(SAXParser.java:392)
>     at
> org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
>     at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
>     at org.apache.axis.Message.getSOAPEnvelope(Message.java:424)
>     at
> org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
>     at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
>     at org.apache.axis.client.Call.invokeEngine(Call.java:2765)
>     at org.apache.axis.client.Call.invoke(Call.java:2748)
>     at org.apache.axis.client.Call.invoke(Call.java:2424)
>     at org.apache.axis.client.Call.invoke(Call.java:2347)
>     at org.apache.axis.client.Call.invoke(Call.java:1804)
>     at
> edu.sdsc.nbcr.opal.AppServicePortTypeSoapBindingStub.launchJob(AppServicePortTypeSoapBindingStub.java:551)
>     at
> CustomOpalClient.CustomOpalClient.launchJob(CustomOpalClient.java:397)
>     at Test.main(Test.java:49)
> 
> It seems like a server problem, maybe with axis? Is this a known
> problem? Is there a solution (apart from restarting tomcat server)?
> Thanks!
> 
> Luca Clementi a écrit :
>> Anthony Bretaudeau wrote:
>>> Hi,
>>> I've got a problem when reloading opal2 app from tomcat manager. After
>>> doing so, registered webservices stop working and the only solution is
>>> to restart tomcat (which is quite uncomfortable as we have other apps in
>>> production on the same tomcat server).
>>> Looking at the log, I see some db related errors when reloading: see
>>> below.
>>> Can you help me?
>>> Thanks!
>> Anthony,
>> we already saw this problem.
>> It is caused by a a race condition of HSQL during the reload of the
>> webapp, basically HSQL is restarted before the old HSQL is completely
>> destroyed. It doesn't always happen, sometime the reload works well.
>>
>> If you use external database this problem won't appear.
>>
>> My suggestion is to stop the webapp, wait some seconds and then start
>> the webapp again, this should avoid this race condition.
>>
>> Sincerely,
>> Luca
>>
>>