Petals SE Notification

On restart, the SE Notification is sending subscribe to wrong endpoints

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Blocker Blocker
  • Resolution: Fixed
  • Affects Version/s: 1.0.3
  • Fix Version/s: 1.0.3
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    When the component restart, it tries to recover itself by replaying notification operations from its persisted data, it seems that messages are sent to the wrong services.
    In the current case, it is sending subscribe messages to the se-kpi which do not know how to handle this type of messages :

    [Petals.Container.Components.petals-se-notification]-FINE 2010-09-23 15:46:48,969 target producer Service to subscribe to : {http://petals.ow2.org/component}NotificationProducerService

[Petals.Container.Components.petals-se-notification]-FINE 2010-09-23 15:46:48,969 target producer Interface to subscribe to : {http://docs.oasis-open.org/wsn/bw-2}NotificationProducer

[Petals.Container.Components.petals-se-notification]-FINE 2010-09-23 15:46:48,969 target producer Endpoint to subscribe to : edpt-0F6EDB524A3CC2A7EA12852479437149770001

[Petals.Container.Components.petals-se-notification]-FINEST 2010-09-23 15:46:48,973 Message in with Id 'petals:uid:C27E5794683EC5B323128524960897386400053' to send
[Petals.Container.Components.petals-se-notification]-FINEST 2010-09-23 15:46:48,974 Operation : {http://docs.oasis-open.org/wsn/b-2}Subscribe
[Petals.Container.Components.petals-se-notification]-FINEST 2010-09-23 15:46:48,974 MEP : http://www.w3.org/2004/08/wsdl/in-out
[Petals.Container.Components.petals-se-notification]-FINEST 2010-09-23 15:46:48,975 Message Content : <?xml version="1.0" encoding="MacRoman" standalone="no"?><wsnt:Subscribe xmlns:wsnt="http://docs.oasis-open.org/wsn/b-2"><wsnt:ConsumerReference><wsa:Address xmlns:wsa="http://www.w3.org/2005/08/addressing">http://petals.ow2.org/cdk</wsa:Address><wsa:ReferenceParameters xmlns:wsa="http://www.w3.org/2005/08/addressing"><ebm:SOAParameter xmlns:ebm="http://www.ebmwebsourcing.com/wsnotification/specificTypes"><ebm:InterfaceName xmlns="http://docs.oasis-open.org/wsn/brw-2">NotificationBroker</ebm:InterfaceName><ebm:ServiceName xmlns="http://petals.ow2.org/petals-se-notification">NotificationBrokerService</ebm:ServiceName><ebm:Endpoint>NotificationBrokerServiceEndpoint</ebm:Endpoint></ebm:SOAParameter></wsa:ReferenceParameters></wsnt:ConsumerReference><wsnt:Filter><wsnt:TopicExpression xmlns:petals="http://petals.ow2.org/topic" Dialect="http://docs.oasis-open.org/wsn/t-1/TopicExpression/Full">petals:component/cdk/producer/fault[@wstop:topic='true']</wsnt:TopicExpression><wsnt:MessageContent Dialect="http://www.ebmwebsourcing.com/wsnotification/soaparameter"><ebm:SOAParameter xmlns:ebm="http://www.ebmwebsourcing.com/wsnotification/specificTypes"><ebm:InterfaceName xmlns="http://notification.test.petals.ebmwebsourcing.com">NotifyImpl</ebm:InterfaceName><ebm:ServiceName xmlns="http://notification.test.petals.ebmwebsourcing.com">NotifyImpl</ebm:ServiceName><ebm:Endpoint>NotifyImplPort</ebm:Endpoint></ebm:SOAParameter></wsnt:MessageContent></wsnt:Filter><wsnt:SubscriptionPolicy><ebm:TransformPolicy xmlns:ebm="http://www.ebmwebsourcing.com/wsnotification/specificTypes"><xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0"><xsl:output indent="yes" method="xml"/><xsl:template match="/"><wsnebm:NotifyContent xmlns:wsnebm="http://www.ebmwebsourcing.com/WS-BaseNotification/NotifyContent" processType="1"><wsnebm:params>	
				
				
			</wsnebm:params>
		</wsnebm:NotifyContent>
	</xsl:template>
</xsl:stylesheet></ebm:TransformPolicy><ebm:ProcessPolicy xmlns:ebm="http://www.ebmwebsourcing.com/wsnotification/specificTypes" action="create"/><ebm:ContextPolicy xmlns:ebm="http://www.ebmwebsourcing.com/wsnotification/specificTypes" correlationId="true" endpoint="true" interface="true" meuuid="true" notifDate="true" service="true" status="true"/></wsnt:SubscriptionPolicy></wsnt:Subscribe>
[Petals.Container.Components.petals-se-kpi]-FINE 2010-09-23 15:46:48,979 Accepting a JBI message with Id : petals:uid:C27E5794683EC5B323128524960897386400053
[Petals.Container.Components.petals-se-kpi]-FINEST 2010-09-23 15:46:48,979 Process an exchange as PROVIDER with id : petals:uid:C27E5794683EC5B323128524960897386400053
[Petals.Container.Components.petals-se-kpi]-FINE 2010-09-23 15:46:48,980 Process an exchange managed directly by the component
[Petals.Container.Components.petals-se-kpi]-FINE 2010-09-23 15:46:48,980 		 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[Petals.Container.Components.petals-se-kpi]-FINE 2010-09-23 15:46:48,980 Notification Message received on "onNotificationMessage" method !
[Petals.Container.Components.petals-se-kpi]-FINEST 2010-09-23 15:46:48,981 Message out with Id 'petals:uid:C27E5794683EC5B323128524960897386400053' to send
[Petals.Container.Components.petals-se-kpi]-FINEST 2010-09-23 15:46:48,981 Operation : {http://docs.oasis-open.org/wsn/b-2}Subscribe
[Petals.Container.Components.petals-se-kpi]-FINEST 2010-09-23 15:46:48,981 MEP : http://www.w3.org/2004/08/wsdl/in-out
[Petals.Container.Components.petals-se-kpi]-FINEST 2010-09-23 15:46:48,981 Message Content is null
[Petals.Container.Components.petals-se-notification]-WARNING 2010-09-23 15:46:49,006  [forwardSubscriptionRequest(...) ] - A WS-Notification Fault have been return on "subscribe" request !!
(inOutExchange Fault Content : 
<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Fault xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
  <faultcode>soapenv:Server</faultcode>
  <faultstring>The KPI process only WS-Notification Notify on InOnly</faultstring>
  <faultactor>http://petals.ow2.org/exception</faultactor>
  <detail>
    <stackTrace>org.ow2.petals.component.framework.api.exception.SOAP11FaultServerException: The KPI process only WS-Notification Notify on InOnly
	at org.ow2.petals.component.framework.process.MessageExchangeProcessor.processInOutAsProvider(MessageExchangeProcessor.java:667)
	at org.ow2.petals.component.framework.process.MessageExchangeProcessor.processAsProvider(MessageExchangeProcessor.java:389)
	at org.ow2.petals.component.framework.process.MessageExchangeProcessor.process(MessageExchangeProcessor.java:233)
	at org.ow2.petals.component.framework.process.MessageExchangeProcessor.run(MessageExchangeProcessor.java:177)
	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:637)
</stackTrace>
  </detail>
</soapenv:Fault>

    To reproduce:
    1. start all notification components
    2. Stop all but se-notification
    3. Stop the se-notification
    4. Start all but se-notification
    5. Start the se-notification : PROBLEM

    Show
    When the component restart, it tries to recover itself by replaying notification operations from its persisted data, it seems that messages are sent to the wrong services. In the current case, it is sending subscribe messages to the se-kpi which do not know how to handle this type of messages : 
    [Petals.Container.Components.petals-se-notification]-FINE 2010-09-23 15:46:48,969 target producer Service to subscribe to : {http://petals.ow2.org/component}NotificationProducerService

[Petals.Container.Components.petals-se-notification]-FINE 2010-09-23 15:46:48,969 target producer Interface to subscribe to : {http://docs.oasis-open.org/wsn/bw-2}NotificationProducer

[Petals.Container.Components.petals-se-notification]-FINE 2010-09-23 15:46:48,969 target producer Endpoint to subscribe to : edpt-0F6EDB524A3CC2A7EA12852479437149770001

[Petals.Container.Components.petals-se-notification]-FINEST 2010-09-23 15:46:48,973 Message in with Id 'petals:uid:C27E5794683EC5B323128524960897386400053' to send
[Petals.Container.Components.petals-se-notification]-FINEST 2010-09-23 15:46:48,974 Operation : {http://docs.oasis-open.org/wsn/b-2}Subscribe
[Petals.Container.Components.petals-se-notification]-FINEST 2010-09-23 15:46:48,974 MEP : http://www.w3.org/2004/08/wsdl/in-out
[Petals.Container.Components.petals-se-notification]-FINEST 2010-09-23 15:46:48,975 Message Content : <?xml version="1.0" encoding="MacRoman" standalone="no"?><wsnt:Subscribe xmlns:wsnt="http://docs.oasis-open.org/wsn/b-2"><wsnt:ConsumerReference><wsa:Address xmlns:wsa="http://www.w3.org/2005/08/addressing">http://petals.ow2.org/cdk</wsa:Address><wsa:ReferenceParameters xmlns:wsa="http://www.w3.org/2005/08/addressing"><ebm:SOAParameter xmlns:ebm="http://www.ebmwebsourcing.com/wsnotification/specificTypes"><ebm:InterfaceName xmlns="http://docs.oasis-open.org/wsn/brw-2">NotificationBroker</ebm:InterfaceName><ebm:ServiceName xmlns="http://petals.ow2.org/petals-se-notification">NotificationBrokerService</ebm:ServiceName><ebm:Endpoint>NotificationBrokerServiceEndpoint</ebm:Endpoint></ebm:SOAParameter></wsa:ReferenceParameters></wsnt:ConsumerReference><wsnt:Filter><wsnt:TopicExpression xmlns:petals="http://petals.ow2.org/topic" Dialect="http://docs.oasis-open.org/wsn/t-1/TopicExpression/Full">petals:component/cdk/producer/fault[@wstop:topic='true']</wsnt:TopicExpression><wsnt:MessageContent Dialect="http://www.ebmwebsourcing.com/wsnotification/soaparameter"><ebm:SOAParameter xmlns:ebm="http://www.ebmwebsourcing.com/wsnotification/specificTypes"><ebm:InterfaceName xmlns="http://notification.test.petals.ebmwebsourcing.com">NotifyImpl</ebm:InterfaceName><ebm:ServiceName xmlns="http://notification.test.petals.ebmwebsourcing.com">NotifyImpl</ebm:ServiceName><ebm:Endpoint>NotifyImplPort</ebm:Endpoint></ebm:SOAParameter></wsnt:MessageContent></wsnt:Filter><wsnt:SubscriptionPolicy><ebm:TransformPolicy xmlns:ebm="http://www.ebmwebsourcing.com/wsnotification/specificTypes"><xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0"><xsl:output indent="yes" method="xml"/><xsl:template match="/"><wsnebm:NotifyContent xmlns:wsnebm="http://www.ebmwebsourcing.com/WS-BaseNotification/NotifyContent" processType="1"><wsnebm:params>	
				
				
			</wsnebm:params>
		</wsnebm:NotifyContent>
	</xsl:template>
</xsl:stylesheet></ebm:TransformPolicy><ebm:ProcessPolicy xmlns:ebm="http://www.ebmwebsourcing.com/wsnotification/specificTypes" action="create"/><ebm:ContextPolicy xmlns:ebm="http://www.ebmwebsourcing.com/wsnotification/specificTypes" correlationId="true" endpoint="true" interface="true" meuuid="true" notifDate="true" service="true" status="true"/></wsnt:SubscriptionPolicy></wsnt:Subscribe>
[Petals.Container.Components.petals-se-kpi]-FINE 2010-09-23 15:46:48,979 Accepting a JBI message with Id : petals:uid:C27E5794683EC5B323128524960897386400053
[Petals.Container.Components.petals-se-kpi]-FINEST 2010-09-23 15:46:48,979 Process an exchange as PROVIDER with id : petals:uid:C27E5794683EC5B323128524960897386400053
[Petals.Container.Components.petals-se-kpi]-FINE 2010-09-23 15:46:48,980 Process an exchange managed directly by the component
[Petals.Container.Components.petals-se-kpi]-FINE 2010-09-23 15:46:48,980 		 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[Petals.Container.Components.petals-se-kpi]-FINE 2010-09-23 15:46:48,980 Notification Message received on "onNotificationMessage" method !
[Petals.Container.Components.petals-se-kpi]-FINEST 2010-09-23 15:46:48,981 Message out with Id 'petals:uid:C27E5794683EC5B323128524960897386400053' to send
[Petals.Container.Components.petals-se-kpi]-FINEST 2010-09-23 15:46:48,981 Operation : {http://docs.oasis-open.org/wsn/b-2}Subscribe
[Petals.Container.Components.petals-se-kpi]-FINEST 2010-09-23 15:46:48,981 MEP : http://www.w3.org/2004/08/wsdl/in-out
[Petals.Container.Components.petals-se-kpi]-FINEST 2010-09-23 15:46:48,981 Message Content is null
[Petals.Container.Components.petals-se-notification]-WARNING 2010-09-23 15:46:49,006  [forwardSubscriptionRequest(...) ] - A WS-Notification Fault have been return on "subscribe" request !!
(inOutExchange Fault Content : 
<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Fault xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
  <faultcode>soapenv:Server</faultcode>
  <faultstring>The KPI process only WS-Notification Notify on InOnly</faultstring>
  <faultactor>http://petals.ow2.org/exception</faultactor>
  <detail>
    <stackTrace>org.ow2.petals.component.framework.api.exception.SOAP11FaultServerException: The KPI process only WS-Notification Notify on InOnly
	at org.ow2.petals.component.framework.process.MessageExchangeProcessor.processInOutAsProvider(MessageExchangeProcessor.java:667)
	at org.ow2.petals.component.framework.process.MessageExchangeProcessor.processAsProvider(MessageExchangeProcessor.java:389)
	at org.ow2.petals.component.framework.process.MessageExchangeProcessor.process(MessageExchangeProcessor.java:233)
	at org.ow2.petals.component.framework.process.MessageExchangeProcessor.run(MessageExchangeProcessor.java:177)
	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:637)
</stackTrace>
  </detail>
</soapenv:Fault>
    To reproduce: 1. start all notification components 2. Stop all but se-notification 3. Stop the se-notification 4. Start all but se-notification 5. Start the se-notification : PROBLEM
  • Environment:
    se-notif + se-kpi as consumer + bc-soap as provider

Issue Links

Depends
 
Duplicate
 

Activity

Transition Status Change Time Execution Times Last Executer Last Execution Date
New New Open Open
58m 7s
1
Christophe Hamerling
Thu, 23 Sep 2010 - 17:14:41 +0200
Open Open In Progress In Progress
6h 28m
1
Christophe Hamerling
Thu, 23 Sep 2010 - 23:43:27 +0200
In Progress In Progress Resolved Resolved
16h 52m
1
Christophe Hamerling
Fri, 24 Sep 2010 - 16:35:27 +0200
Resolved Resolved Closed Closed
39d 1h 47m
1
Olivier Fabre
Tue, 2 Nov 2010 - 17:23:26 +0100

People

Dates

  • Created:
    Thu, 23 Sep 2010 - 16:16:34 +0200
    Updated:
    Tue, 2 Nov 2010 - 17:23:26 +0100
    Resolved:
    Fri, 24 Sep 2010 - 16:35:27 +0200
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.