Petals SE KPI

SAXParseException: unable to restore the subscription references

Details

  • Type: Bug Bug
  • Status: New New
  • Resolution: Unresolved
  • Affects Version/s: 1.1.1
  • Fix Version/s: None
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    The SE sometimes (1 per 8 intoi my server) can't restore the subscriptions. It seems that's a thread unsafe issue. The trace:

    [Petals.Container.Components.petals-se-kpi]-WARNING 2011-01-12 11:08:02,996 unable to restore the subscription references
[Fatal Error] SubsReference.xml:1:1: Premature end of file.
org.xml.sax.SAXParseException: Premature end of file.
        at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:249)
        at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:284)
        at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:208)
        at com.ebmwebsourcing.wsstar.addressing.definition.impl.WSAddressingReaderImpl.convertFromFiletoDocument(WSAddressingReaderImpl.java:233)
        at com.ebmwebsourcing.wsstar.addressing.definition.impl.WSAddressingReaderImpl.readEndpointReferenceType(WSAddressingReaderImpl.java:216)
        at org.ow2.petals.engine.kpi.KeyProcessIndicatorService.restoreSubscriptionRef(KeyProcessIndicatorService.java:292)
        at org.ow2.petals.engine.kpi.su.KpiServiceUnitManager.doStart(KpiServiceUnitManager.java:113)
        at org.ow2.petals.component.framework.su.AbstractServiceUnitManager.start(AbstractServiceUnitManager.java:616)
        at org.ow2.petals.container.lifecycle.ServiceUnitLifeCycle.start(ServiceUnitLifeCycle.java:161)
        at org.ow2.petals.container.lifecycle.ServiceAssemblyLifeCycle.doStart(ServiceAssemblyLifeCycle.java:166)
        at org.ow2.petals.container.lifecycle.LifeCycleAbstract.start(LifeCycleAbstract.java:185)
        at org.ow2.petals.jbi.management.recovery.SystemRecoveryServiceImpl.recoverServiceAssembly(SystemRecoveryServiceImpl.java:602)
        at org.ow2.petals.jbi.management.recovery.SystemRecoveryServiceImpl$2.call(SystemRecoveryServiceImpl.java:322)
        at org.ow2.petals.jbi.management.recovery.SystemRecoveryServiceImpl$2.call(SystemRecoveryServiceImpl.java:1)
        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
        at java.util.concurrent.FutureTask.run(FutureTask.java:138)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
        at java.util.concurrent.FutureTask.run(FutureTask.java:138)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
        at java.lang.Thread.run(Thread.java:619)

    We can see that the Exception isn't cught by the petals logger too (we see [Fatal Error]).
    If we restart, we have again the trace. It seems that we continue to receive the notifications (so is it ok or completly lost and recreated from scratch?)

    Show
    The SE sometimes (1 per 8 intoi my server) can't restore the subscriptions. It seems that's a thread unsafe issue. The trace: 
    [Petals.Container.Components.petals-se-kpi]-WARNING 2011-01-12 11:08:02,996 unable to restore the subscription references
[Fatal Error] SubsReference.xml:1:1: Premature end of file.
org.xml.sax.SAXParseException: Premature end of file.
        at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:249)
        at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:284)
        at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:208)
        at com.ebmwebsourcing.wsstar.addressing.definition.impl.WSAddressingReaderImpl.convertFromFiletoDocument(WSAddressingReaderImpl.java:233)
        at com.ebmwebsourcing.wsstar.addressing.definition.impl.WSAddressingReaderImpl.readEndpointReferenceType(WSAddressingReaderImpl.java:216)
        at org.ow2.petals.engine.kpi.KeyProcessIndicatorService.restoreSubscriptionRef(KeyProcessIndicatorService.java:292)
        at org.ow2.petals.engine.kpi.su.KpiServiceUnitManager.doStart(KpiServiceUnitManager.java:113)
        at org.ow2.petals.component.framework.su.AbstractServiceUnitManager.start(AbstractServiceUnitManager.java:616)
        at org.ow2.petals.container.lifecycle.ServiceUnitLifeCycle.start(ServiceUnitLifeCycle.java:161)
        at org.ow2.petals.container.lifecycle.ServiceAssemblyLifeCycle.doStart(ServiceAssemblyLifeCycle.java:166)
        at org.ow2.petals.container.lifecycle.LifeCycleAbstract.start(LifeCycleAbstract.java:185)
        at org.ow2.petals.jbi.management.recovery.SystemRecoveryServiceImpl.recoverServiceAssembly(SystemRecoveryServiceImpl.java:602)
        at org.ow2.petals.jbi.management.recovery.SystemRecoveryServiceImpl$2.call(SystemRecoveryServiceImpl.java:322)
        at org.ow2.petals.jbi.management.recovery.SystemRecoveryServiceImpl$2.call(SystemRecoveryServiceImpl.java:1)
        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
        at java.util.concurrent.FutureTask.run(FutureTask.java:138)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
        at java.util.concurrent.FutureTask.run(FutureTask.java:138)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
        at java.lang.Thread.run(Thread.java:619)
    We can see that the Exception isn't cught by the petals logger too (we see [Fatal Error]). If we restart, we have again the trace. It seems that we continue to receive the notifications (so is it ok or completly lost and recreated from scratch?)
  • Environment:
    ESB 3.1.1, rhel 5

Activity

Ascending order - Click to sort in descending order
No changes have yet been made on this issue.

People

Dates

  • Created:
    Wed, 12 Jan 2011 - 11:19:22 +0100
    Updated:
    Thu, 3 Feb 2011 - 09:30:01 +0100
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.