[ESBJAVA-5027] Datapublisher instance count grows when DAS/BAM is not available to receive events Created: 22/Feb/17  Updated: 23/Feb/17  Resolved: 23/Feb/17

Status: Resolved
Project: WSO2 ESB
Component/s: None
Affects Version/s: 4.9.0
Fix Version/s: 4.9.0

Type: Bug Priority: Normal
Reporter: Mohanadarshan Vivekanandalingam Assignee: Mohanadarshan Vivekanandalingam
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Severity: Major
Estimated Complexity: Moderate
Test cases added: Yes

 Description   

Above issue is not there in last ESB since data publisher implementation is different in latest code.

Issue: You could see below logs when we configured a proxy or API with a publishEvent mediator and there is any DAS/CEP server available to receive events.

{org.wso2.carbon.databridge.agent.thrift.AsyncDataPublisher}
TID: [-1] [] [2017-02-23 12:49:36,505] ERROR {org.wso2.carbon.databridge.agent.thrift.AsyncDataPublisher}

- Reconnection failed for for tcp://localhost:7612

At this situation, Data publisher object gets created in-definitely until a connection is available. This will cause OOM at some situations.

Use JProfiler or any other proper tool and check below objects to verify the issue
org.wso2.carbon.databridge.agent.thrift.DataPublisher



 Comments   
Comment by Mohanadarshan Vivekanandalingam [ 23/Feb/17 ]

The issue is not available in latest ESB since data publisher implementation is different.





Generated at Fri Feb 24 02:49:07 IST 2017 using JIRA 7.2.2#72004-sha1:9d5132893cc8c728a3601a9034a1f8547ef5c7be.