[ 
https://issues.apache.org/jira/browse/MUSE-270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vinh Nguyen updated MUSE-270:
-----------------------------

    Attachment: WsnErrorsTest.zip

Test case to see the errors generated when notifications are sent from multiple 
resources.  This is based on the Muse wsn-consumer and wsn-producer samples 
with some slight modifications.

Zip file includes:

1) wsnproducer.war - ready to deploy
2) wsnconsumer.war - ready to deploy
3) MyCapabilityImpl.java - producer source code which generates 100 
notifications
4) ConsumerCapabilityImpl.java - consumer source code which periodically prints 
how many notifications it received
5) WsnTestClient.java - client source code which subscribes the consumer for 
notifications

To test, deploy both War files and run the client.  Then check the muse.log 
files of each deployed app.  You will see exceptions in both the producer and 
consumer related to EndpointReference problems.

Basically, 3 instances of the producer WsResource are initialized.  Each will 
print 100 notifications.  So the consumer should receive 300 notifications.

On average, I am seeing 1/3 of the notifications dropped using this simple test 
case.


> EMPTY_DOC thread stability issues
> ---------------------------------
>
>                 Key: MUSE-270
>                 URL: https://issues.apache.org/jira/browse/MUSE-270
>             Project: Muse
>          Issue Type: Bug
>          Components: Utilities - General, QName, and XML, WS-Addressing and 
> SOAP
>    Affects Versions: 2.0.0 M1, 2.0.0 M2, 2.0.0, 2.1.0, 2.2.0, 2.3.0
>         Environment: Impacts all platforms and configurations
>            Reporter: Rich Lucente
>            Assignee: Dan Jemiolo
>             Fix For: 2.3.0
>
>         Attachments: epr-tests.zip, WsnErrorsTest.zip
>
>
> This bug is being opened to track the EMPTY_DOC thread stability issue 
> currently being discussed on the muse-dev mailing list.  XmlUtils provides 
> EMPTY_DOC as a scratchpad instance of a DOM Document for creation of 
> elements.  This has been shown to cause exceptions in a multi-threaded 
> environment.  The issue is compounded by the widespread use of EMPTY_DOC in 
> the code due to its convenience and the reduction in object creation when 
> constructing XML fragments.

-- 
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to