[jira] [Resolved] (SYNAPSE-1109) WSA:From header is missing when sending a request to an endpoint
[ https://issues.apache.org/jira/browse/SYNAPSE-1109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Udana Loku Narangoda resolved SYNAPSE-1109. - Fix Version/s: 3.0.2 Resolution: Fixed > WSA:From header is missing when sending a request to an endpoint > - > > Key: SYNAPSE-1109 > URL: https://issues.apache.org/jira/browse/SYNAPSE-1109 > Project: Synapse > Issue Type: Bug > Components: Core >Affects Versions: 3.0.1 >Reporter: Auke Schrijnen >Assignee: Isuru Udana Loku Narangoda >Priority: Major > Fix For: 3.0.2 > > Time Spent: 20m > Remaining Estimate: 0h > > When a From value is set in the message context (e.g. with > MessageContext.setFrom) before it is sent to an endpoint the value isn't used > in the resulting request. This is due to the fact that the > Axis2FlexibleMEPClient clones the message context before sending it and the > MessageHelper.clonePartially doesn't copy the From value from the source > message context to the cloned message context. -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Commented] (SYNAPSE-1107) Remove dispatchers instantiation inside dispatchAndVerify Method
[ https://issues.apache.org/jira/browse/SYNAPSE-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16853894#comment-16853894 ] Isuru Udana Loku Narangoda commented on SYNAPSE-1107: - Committed revision 1860506. Thank you for your contribution. > Remove dispatchers instantiation inside dispatchAndVerify Method > - > > Key: SYNAPSE-1107 > URL: https://issues.apache.org/jira/browse/SYNAPSE-1107 > Project: Synapse > Issue Type: Improvement >Reporter: Madhawa Gunasekara >Assignee: Isuru Udana Loku Narangoda >Priority: Major > Attachments: Fix_SYNAPSE-1107.patch > > > For the every rest request these dispatchers will be instantiated, It will > add a additional unnecessary latency for the request flow. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Resolved] (SYNAPSE-1107) Remove dispatchers instantiation inside dispatchAndVerify Method
[ https://issues.apache.org/jira/browse/SYNAPSE-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Udana Loku Narangoda resolved SYNAPSE-1107. - Resolution: Fixed Fix Version/s: 3.0.2 > Remove dispatchers instantiation inside dispatchAndVerify Method > - > > Key: SYNAPSE-1107 > URL: https://issues.apache.org/jira/browse/SYNAPSE-1107 > Project: Synapse > Issue Type: Improvement >Reporter: Madhawa Gunasekara >Assignee: Isuru Udana Loku Narangoda >Priority: Major > Fix For: 3.0.2 > > Attachments: Fix_SYNAPSE-1107.patch > > > For the every rest request these dispatchers will be instantiated, It will > add a additional unnecessary latency for the request flow. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Resolved] (SYNAPSE-1048) Listenning IO Reactor worker threads are blocked If exception occured while pass throughing large messages.
[ https://issues.apache.org/jira/browse/SYNAPSE-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Udana Loku Narangoda resolved SYNAPSE-1048. - Resolution: Fixed Fix Version/s: (was: FUTURE) 3.0.2 > Listenning IO Reactor worker threads are blocked If exception occured while > pass throughing large messages. > - > > Key: SYNAPSE-1048 > URL: https://issues.apache.org/jira/browse/SYNAPSE-1048 > Project: Synapse > Issue Type: Bug > Components: Transports >Affects Versions: 1.1 >Reporter: isuru janith ranawaka >Assignee: Isuru Udana Loku Narangoda >Priority: Major > Fix For: 3.0.2 > > Attachments: SYNAPSE_1048.diff > > > Listening IO Reactor worker threads could be blocked while pass through > large messages if exception occurred in the TargetHandler. Currently if > exception occurred then fault messages are propagated to Fault Sequence but > does not inform weather it is a writer error or reader error which could be > caused IO worker threads being spinning for condition in Pipe.flushContent() > . -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Commented] (SYNAPSE-1048) Listenning IO Reactor worker threads are blocked If exception occured while pass throughing large messages.
[ https://issues.apache.org/jira/browse/SYNAPSE-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16850247#comment-16850247 ] Isuru Udana Loku Narangoda commented on SYNAPSE-1048: - Committed revision 1860309. > Listenning IO Reactor worker threads are blocked If exception occured while > pass throughing large messages. > - > > Key: SYNAPSE-1048 > URL: https://issues.apache.org/jira/browse/SYNAPSE-1048 > Project: Synapse > Issue Type: Bug > Components: Transports >Affects Versions: 1.1 >Reporter: isuru janith ranawaka >Assignee: Isuru Udana Loku Narangoda >Priority: Major > Fix For: FUTURE > > Attachments: SYNAPSE_1048.diff > > > Listening IO Reactor worker threads could be blocked while pass through > large messages if exception occurred in the TargetHandler. Currently if > exception occurred then fault messages are propagated to Fault Sequence but > does not inform weather it is a writer error or reader error which could be > caused IO worker threads being spinning for condition in Pipe.flushContent() > . -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Comment Edited] (SYNAPSE-1048) Listenning IO Reactor worker threads are blocked If exception occured while pass throughing large messages.
[ https://issues.apache.org/jira/browse/SYNAPSE-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16850247#comment-16850247 ] Isuru Udana Loku Narangoda edited comment on SYNAPSE-1048 at 5/29/19 12:09 AM: --- Committed revision 1860309. Thank you for your contribution. was (Author: isudana): Committed revision 1860309. > Listenning IO Reactor worker threads are blocked If exception occured while > pass throughing large messages. > - > > Key: SYNAPSE-1048 > URL: https://issues.apache.org/jira/browse/SYNAPSE-1048 > Project: Synapse > Issue Type: Bug > Components: Transports >Affects Versions: 1.1 >Reporter: isuru janith ranawaka >Assignee: Isuru Udana Loku Narangoda >Priority: Major > Fix For: FUTURE > > Attachments: SYNAPSE_1048.diff > > > Listening IO Reactor worker threads could be blocked while pass through > large messages if exception occurred in the TargetHandler. Currently if > exception occurred then fault messages are propagated to Fault Sequence but > does not inform weather it is a writer error or reader error which could be > caused IO worker threads being spinning for condition in Pipe.flushContent() > . -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Assigned] (SYNAPSE-1048) Listenning IO Reactor worker threads are blocked If exception occured while pass throughing large messages.
[ https://issues.apache.org/jira/browse/SYNAPSE-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Udana Loku Narangoda reassigned SYNAPSE-1048: --- Assignee: Isuru Udana Loku Narangoda (was: Hiranya Jayathilaka) > Listenning IO Reactor worker threads are blocked If exception occured while > pass throughing large messages. > - > > Key: SYNAPSE-1048 > URL: https://issues.apache.org/jira/browse/SYNAPSE-1048 > Project: Synapse > Issue Type: Bug > Components: Transports >Affects Versions: 1.1 >Reporter: isuru janith ranawaka >Assignee: Isuru Udana Loku Narangoda >Priority: Major > Fix For: FUTURE > > Attachments: SYNAPSE_1048.diff > > > Listening IO Reactor worker threads could be blocked while pass through > large messages if exception occurred in the TargetHandler. Currently if > exception occurred then fault messages are propagated to Fault Sequence but > does not inform weather it is a writer error or reader error which could be > caused IO worker threads being spinning for condition in Pipe.flushContent() > . -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Resolved] (SYNAPSE-1075) HTTPS Load test for the 3.0 release
[ https://issues.apache.org/jira/browse/SYNAPSE-1075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Udana Loku Narangoda resolved SYNAPSE-1075. - Resolution: Done > HTTPS Load test for the 3.0 release > --- > > Key: SYNAPSE-1075 > URL: https://issues.apache.org/jira/browse/SYNAPSE-1075 > Project: Synapse > Issue Type: Task > Components: Transports >Reporter: Chanaka Fernando >Assignee: Isuru Udana Loku Narangoda >Priority: Major > Attachments: EchoProxy.xml, synapse-https-100x1000.xml, > synapse-https-200x100.xml, synapse-https-300x100.xml, > synapse-https-400x100.xml, synapse-https-500x100.xml, > synapse-https-sender-100x100.xml, synapse-https-sender-200x100.xml, > synapse-https-sender-300x100.xml, synapse-https-sender-400x100.xml, > synapse-https-sender-500x100.xml, synapse-proxy-soapui-project.xml > > > Need to carry out a load test for HTTPS listener and sender before the > release. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Commented] (SYNAPSE-1094) Build Error :- Execution distribution-package of goal org.apache.maven.plugins:maven-assembly-plugin:2.6:single failed: group id '110243664' is too big
[
https://issues.apache.org/jira/browse/SYNAPSE-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16850244#comment-16850244
]
Isuru Udana Loku Narangoda commented on SYNAPSE-1094:
-
Can we close the issue?
> Build Error :- Execution distribution-package of goal
> org.apache.maven.plugins:maven-assembly-plugin:2.6:single failed: group id
> '110243664' is too big
> ---
>
> Key: SYNAPSE-1094
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1094
> Project: Synapse
> Issue Type: Bug
>Reporter: Vanjikumaran Sivajothy
>Assignee: Vanjikumaran Sivajothy
>Priority: Major
> Attachments:
> SYNAPSE-1094,_build_error_due_to_the_limitation_in_the_plugin.patch
>
>
> {code}
> NFO] Apache Synapse - XAR Maven Plugin .. SUCCESS [ 7.686 s]
> [INFO] Apache Synapse - Configuration Migrator SUCCESS [ 0.682
> s]
> [INFO] Apache Synapse - Distribution .. FAILURE [ 14.471
> s]
> [INFO] Apache Synapse - Package skeleton ZIP .. SKIPPED
> [INFO] Apache Synapse - Package archetype . SKIPPED
> [INFO] Apache Synapse - Integration ... SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 05:53 min
> [INFO] Finished at: 2017-01-03T11:57:30-08:00
> [INFO] Final Memory: 122M/1005M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-assembly-plugin:2.6:single
> (distribution-package) on project synapse-distribution: Execution
> distribution-package of goal
> org.apache.maven.plugins:maven-assembly-plugin:2.6:single failed: group id
> '110243664' is too big ( > 2097151 ). Use STAR or POSIX extensions to
> overcome this limit -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR] mvn -rf :synapse-distribution
> {code}
> This issue due to the limitation in the maven plugin while building the tar
> [1]. Patch is attached to resolve this issue.
> {code}
> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
> 2015-11-10T08:41:47-08:00)
> Maven home: /usr/local/Cellar/maven/3.3.9/libexec
> Java version: 1.7.0_79, vendor: Oracle Corporation
> Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.11.6", arch: "x86_64", family: "mac"
> {code}
> [1] https://issues.apache.org/jira/browse/MASSEMBLY-728
> [2] https://issues.apache.org/jira/browse/COMPRESS-290
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Resolved] (SYNAPSE-1101) Self Signed certificate expired
[
https://issues.apache.org/jira/browse/SYNAPSE-1101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Isuru Udana Loku Narangoda resolved SYNAPSE-1101.
-
Resolution: Fixed
> Self Signed certificate expired
>
>
> Key: SYNAPSE-1101
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1101
> Project: Synapse
> Issue Type: Task
>Reporter: Vanjikumaran Sivajothy
>Assignee: Isuru Udana Loku Narangoda
>Priority: Blocker
>
> build is failing due to certificate expired
> {code}
> Caused by: java.security.cert.CertificateExpiredException: NotAfter: Mon Mar
> 19 16:59:59 PDT 2018
> at sun.security.x509.CertificateValidity.valid(CertificateValidity.java:274)
> at sun.security.x509.X509CertImpl.checkValidity(X509CertImpl.java:629)
> at sun.security.x509.X509CertImpl.checkValidity(X509CertImpl.java:602)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Commented] (SYNAPSE-1101) Self Signed certificate expired
[
https://issues.apache.org/jira/browse/SYNAPSE-1101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16788995#comment-16788995
]
Isuru Udana Loku Narangoda commented on SYNAPSE-1101:
-
Fixed with revision 1855156.
> Self Signed certificate expired
>
>
> Key: SYNAPSE-1101
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1101
> Project: Synapse
> Issue Type: Task
>Reporter: Vanjikumaran Sivajothy
>Assignee: Isuru Udana Loku Narangoda
>Priority: Blocker
>
> build is failing due to certificate expired
> {code}
> Caused by: java.security.cert.CertificateExpiredException: NotAfter: Mon Mar
> 19 16:59:59 PDT 2018
> at sun.security.x509.CertificateValidity.valid(CertificateValidity.java:274)
> at sun.security.x509.X509CertImpl.checkValidity(X509CertImpl.java:629)
> at sun.security.x509.X509CertImpl.checkValidity(X509CertImpl.java:602)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Reopened] (SYNAPSE-1101) Self Signed certificate expired
[
https://issues.apache.org/jira/browse/SYNAPSE-1101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Isuru Udana Loku Narangoda reopened SYNAPSE-1101:
-
Looks like issue is appearing again for some key-stores again.
> Self Signed certificate expired
>
>
> Key: SYNAPSE-1101
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1101
> Project: Synapse
> Issue Type: Task
>Reporter: Vanjikumaran Sivajothy
>Assignee: Isuru Udana Loku Narangoda
>Priority: Blocker
>
> build is failing due to certificate expired
> {code}
> Caused by: java.security.cert.CertificateExpiredException: NotAfter: Mon Mar
> 19 16:59:59 PDT 2018
> at sun.security.x509.CertificateValidity.valid(CertificateValidity.java:274)
> at sun.security.x509.X509CertImpl.checkValidity(X509CertImpl.java:629)
> at sun.security.x509.X509CertImpl.checkValidity(X509CertImpl.java:602)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Commented] (SYNAPSE-1094) Build Error :- Execution distribution-package of goal org.apache.maven.plugins:maven-assembly-plugin:2.6:single failed: group id '110243664' is too big
[
https://issues.apache.org/jira/browse/SYNAPSE-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16781162#comment-16781162
]
Isuru Udana Loku Narangoda commented on SYNAPSE-1094:
-
Hi Vanji,
Committed the patch to trunk in r1854555.
Should we update all the places which uses assembly plugin ?
> Build Error :- Execution distribution-package of goal
> org.apache.maven.plugins:maven-assembly-plugin:2.6:single failed: group id
> '110243664' is too big
> ---
>
> Key: SYNAPSE-1094
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1094
> Project: Synapse
> Issue Type: Bug
>Reporter: Vanjikumaran Sivajothy
>Assignee: Isuru Udana Loku Narangoda
>Priority: Major
> Attachments:
> SYNAPSE-1094,_build_error_due_to_the_limitation_in_the_plugin.patch
>
>
> {code}
> NFO] Apache Synapse - XAR Maven Plugin .. SUCCESS [ 7.686 s]
> [INFO] Apache Synapse - Configuration Migrator SUCCESS [ 0.682
> s]
> [INFO] Apache Synapse - Distribution .. FAILURE [ 14.471
> s]
> [INFO] Apache Synapse - Package skeleton ZIP .. SKIPPED
> [INFO] Apache Synapse - Package archetype . SKIPPED
> [INFO] Apache Synapse - Integration ... SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 05:53 min
> [INFO] Finished at: 2017-01-03T11:57:30-08:00
> [INFO] Final Memory: 122M/1005M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-assembly-plugin:2.6:single
> (distribution-package) on project synapse-distribution: Execution
> distribution-package of goal
> org.apache.maven.plugins:maven-assembly-plugin:2.6:single failed: group id
> '110243664' is too big ( > 2097151 ). Use STAR or POSIX extensions to
> overcome this limit -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR] mvn -rf :synapse-distribution
> {code}
> This issue due to the limitation in the maven plugin while building the tar
> [1]. Patch is attached to resolve this issue.
> {code}
> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
> 2015-11-10T08:41:47-08:00)
> Maven home: /usr/local/Cellar/maven/3.3.9/libexec
> Java version: 1.7.0_79, vendor: Oracle Corporation
> Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.11.6", arch: "x86_64", family: "mac"
> {code}
> [1] https://issues.apache.org/jira/browse/MASSEMBLY-728
> [2] https://issues.apache.org/jira/browse/COMPRESS-290
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Comment Edited] (SYNAPSE-1101) Self Signed certificate expired
[
https://issues.apache.org/jira/browse/SYNAPSE-1101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16781167#comment-16781167
]
Isuru Udana Loku Narangoda edited comment on SYNAPSE-1101 at 3/1/19 1:25 AM:
-
Looks like issue is appearing for some key-stores again.
was (Author: isudana):
Looks like issue is appearing again for some key-stores again.
> Self Signed certificate expired
>
>
> Key: SYNAPSE-1101
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1101
> Project: Synapse
> Issue Type: Task
>Reporter: Vanjikumaran Sivajothy
>Assignee: Isuru Udana Loku Narangoda
>Priority: Blocker
>
> build is failing due to certificate expired
> {code}
> Caused by: java.security.cert.CertificateExpiredException: NotAfter: Mon Mar
> 19 16:59:59 PDT 2018
> at sun.security.x509.CertificateValidity.valid(CertificateValidity.java:274)
> at sun.security.x509.X509CertImpl.checkValidity(X509CertImpl.java:629)
> at sun.security.x509.X509CertImpl.checkValidity(X509CertImpl.java:602)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Assigned] (SYNAPSE-1094) Build Error :- Execution distribution-package of goal org.apache.maven.plugins:maven-assembly-plugin:2.6:single failed: group id '110243664' is too big
[
https://issues.apache.org/jira/browse/SYNAPSE-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Isuru Udana Loku Narangoda reassigned SYNAPSE-1094:
---
Assignee: Vanjikumaran Sivajothy (was: Isuru Udana Loku Narangoda)
> Build Error :- Execution distribution-package of goal
> org.apache.maven.plugins:maven-assembly-plugin:2.6:single failed: group id
> '110243664' is too big
> ---
>
> Key: SYNAPSE-1094
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1094
> Project: Synapse
> Issue Type: Bug
>Reporter: Vanjikumaran Sivajothy
>Assignee: Vanjikumaran Sivajothy
>Priority: Major
> Attachments:
> SYNAPSE-1094,_build_error_due_to_the_limitation_in_the_plugin.patch
>
>
> {code}
> NFO] Apache Synapse - XAR Maven Plugin .. SUCCESS [ 7.686 s]
> [INFO] Apache Synapse - Configuration Migrator SUCCESS [ 0.682
> s]
> [INFO] Apache Synapse - Distribution .. FAILURE [ 14.471
> s]
> [INFO] Apache Synapse - Package skeleton ZIP .. SKIPPED
> [INFO] Apache Synapse - Package archetype . SKIPPED
> [INFO] Apache Synapse - Integration ... SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 05:53 min
> [INFO] Finished at: 2017-01-03T11:57:30-08:00
> [INFO] Final Memory: 122M/1005M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-assembly-plugin:2.6:single
> (distribution-package) on project synapse-distribution: Execution
> distribution-package of goal
> org.apache.maven.plugins:maven-assembly-plugin:2.6:single failed: group id
> '110243664' is too big ( > 2097151 ). Use STAR or POSIX extensions to
> overcome this limit -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR] mvn -rf :synapse-distribution
> {code}
> This issue due to the limitation in the maven plugin while building the tar
> [1]. Patch is attached to resolve this issue.
> {code}
> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
> 2015-11-10T08:41:47-08:00)
> Maven home: /usr/local/Cellar/maven/3.3.9/libexec
> Java version: 1.7.0_79, vendor: Oracle Corporation
> Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.11.6", arch: "x86_64", family: "mac"
> {code}
> [1] https://issues.apache.org/jira/browse/MASSEMBLY-728
> [2] https://issues.apache.org/jira/browse/COMPRESS-290
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Resolved] (SYNAPSE-1101) Self Signed certificate expired
[
https://issues.apache.org/jira/browse/SYNAPSE-1101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Isuru Udana Loku Narangoda resolved SYNAPSE-1101.
-
Resolution: Fixed
> Self Signed certificate expired
>
>
> Key: SYNAPSE-1101
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1101
> Project: Synapse
> Issue Type: Task
>Reporter: Vanjikumaran Sivajothy
>Assignee: Isuru Udana Loku Narangoda
>Priority: Blocker
>
> build is failing due to certificate expired
> {code}
> Caused by: java.security.cert.CertificateExpiredException: NotAfter: Mon Mar
> 19 16:59:59 PDT 2018
> at sun.security.x509.CertificateValidity.valid(CertificateValidity.java:274)
> at sun.security.x509.X509CertImpl.checkValidity(X509CertImpl.java:629)
> at sun.security.x509.X509CertImpl.checkValidity(X509CertImpl.java:602)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Commented] (SYNAPSE-1101) Self Signed certificate expired
[
https://issues.apache.org/jira/browse/SYNAPSE-1101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16677043#comment-16677043
]
Isuru Udana Loku Narangoda commented on SYNAPSE-1101:
-
Fixed with r1845940.
> Self Signed certificate expired
>
>
> Key: SYNAPSE-1101
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1101
> Project: Synapse
> Issue Type: Task
>Reporter: Vanjikumaran Sivajothy
>Assignee: Isuru Udana Loku Narangoda
>Priority: Blocker
>
> build is failing due to certificate expired
> {code}
> Caused by: java.security.cert.CertificateExpiredException: NotAfter: Mon Mar
> 19 16:59:59 PDT 2018
> at sun.security.x509.CertificateValidity.valid(CertificateValidity.java:274)
> at sun.security.x509.X509CertImpl.checkValidity(X509CertImpl.java:629)
> at sun.security.x509.X509CertImpl.checkValidity(X509CertImpl.java:602)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Deleted] (SYNAPSE-1099) HPE0-J79 PDF Test Dumps - Free HP HPE0-J79 Sample pdf questions
[ https://issues.apache.org/jira/browse/SYNAPSE-1099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Udana Loku Narangoda deleted SYNAPSE-1099: > HPE0-J79 PDF Test Dumps - Free HP HPE0-J79 Sample pdf questions > --- > > Key: SYNAPSE-1099 > URL: https://issues.apache.org/jira/browse/SYNAPSE-1099 > Project: Synapse > Issue Type: Improvement >Reporter: Kellein Milek >Assignee: Isuru Udana Loku Narangoda >Priority: Major > > *Valid HPE0-J79 Questions Dumps in addition to Ideas to Pass HPE0-J79 Exam in > First Attempt* > Finding the IT certification by passing the HPE0-J79 exams have become a > necessity of IT specialists these days to get stable jobs within their field. > But typically these HP HPE0-J79 exam refers to one of their most popular HP > Master ASE HPE0-J79 Test Dumps within the field of IT that so many experts > have been working hard for HPE0-J79 exam. These HPE0-J79 Test Dumps, however, > are sorted among the qualified professionals. That is exactly why our > HPE0-J79 Test Dumps come to be so much viral all around the world. > *Latest HP HPE0-J79 Training Material - Here's What HP qualified To Say About > It* > The users should attempt not to rush to the HP HPE0-J79 exam before planning > for them to the fullest. They can put themselves in some complications while > operating for HPE0-J79 exam without HPE0-J79 dumps pdf for their HP Master > ASE Architecting Multi-Site HPE Storage Solutions test. The a lot more they > get ready for the HP HPE0-J79 certification exam from [HPE0-J79 new questions > provided by > CertificationsDesk.com|https://www.certificationsdesk.com/hp/real-HPE0-J79-exam-questions.html], > the more they can have the ability to know about HPE0-J79 PDF dumps and can > prepare yourself better for HP HPE0-J79 certification test. This is how it > can be helpful for the students to acquire done with HPE0-J79 certification > exam. > *HP HPE0-J79 Practice Test and PDF Questions for Quick Achievement* > There are numerous amazing HPE0-J79 new questions available with us online at > our site for preparing HP Master ASE HPE0-J79 certification exam. Our clients > can go through our HPE0-J79 Dumps to HP Architecting Multi-Site HPE Storage > Solutions test, so that it becomes actually very easy for them to attempt the > HPE0-J79 certification exam quickly. This is how these kinds of HPE0-J79 new > questions that we've been offering have become really very easy HPE0-J79 Test > Dumps for them. They ought to try solving as numerous HP HPE0-J79 practice > test software > *HP HPE0-J79 Questions Dumps - Hidden Advantages You Should Know* > The HPE0-J79 Test Dumps that are available at our site for organizing for > these HPE0-J79 sample questions certification test have always been > definitely very helpful for our clients one way or another for the > preparation of HP HPE0-J79. They could delight in solving their favourite > HPE0-J79 pdf questions website after preparing for HPE0-J79 certification > test with the aid of our software. This HP HPE0-J79 Test Dumps, however, can > help them to prepare HP HPE0-J79 certification exam and to make it through > their HPE0-J79 exam, so that their period don't get wasted and they don't > need to stress for the preparation of HPE0-J79 certification exam. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Closed] (SYNAPSE-1099) HPE0-J79 PDF Test Dumps - Free HP HPE0-J79 Sample pdf questions
[ https://issues.apache.org/jira/browse/SYNAPSE-1099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Udana Loku Narangoda closed SYNAPSE-1099. --- Resolution: Invalid > HPE0-J79 PDF Test Dumps - Free HP HPE0-J79 Sample pdf questions > --- > > Key: SYNAPSE-1099 > URL: https://issues.apache.org/jira/browse/SYNAPSE-1099 > Project: Synapse > Issue Type: Improvement >Reporter: Kellein Milek >Assignee: Isuru Udana Loku Narangoda >Priority: Major > > *Valid HPE0-J79 Questions Dumps in addition to Ideas to Pass HPE0-J79 Exam in > First Attempt* > Finding the IT certification by passing the HPE0-J79 exams have become a > necessity of IT specialists these days to get stable jobs within their field. > But typically these HP HPE0-J79 exam refers to one of their most popular HP > Master ASE HPE0-J79 Test Dumps within the field of IT that so many experts > have been working hard for HPE0-J79 exam. These HPE0-J79 Test Dumps, however, > are sorted among the qualified professionals. That is exactly why our > HPE0-J79 Test Dumps come to be so much viral all around the world. > *Latest HP HPE0-J79 Training Material - Here's What HP qualified To Say About > It* > The users should attempt not to rush to the HP HPE0-J79 exam before planning > for them to the fullest. They can put themselves in some complications while > operating for HPE0-J79 exam without HPE0-J79 dumps pdf for their HP Master > ASE Architecting Multi-Site HPE Storage Solutions test. The a lot more they > get ready for the HP HPE0-J79 certification exam from [HPE0-J79 new questions > provided by > CertificationsDesk.com|https://www.certificationsdesk.com/hp/real-HPE0-J79-exam-questions.html], > the more they can have the ability to know about HPE0-J79 PDF dumps and can > prepare yourself better for HP HPE0-J79 certification test. This is how it > can be helpful for the students to acquire done with HPE0-J79 certification > exam. > *HP HPE0-J79 Practice Test and PDF Questions for Quick Achievement* > There are numerous amazing HPE0-J79 new questions available with us online at > our site for preparing HP Master ASE HPE0-J79 certification exam. Our clients > can go through our HPE0-J79 Dumps to HP Architecting Multi-Site HPE Storage > Solutions test, so that it becomes actually very easy for them to attempt the > HPE0-J79 certification exam quickly. This is how these kinds of HPE0-J79 new > questions that we've been offering have become really very easy HPE0-J79 Test > Dumps for them. They ought to try solving as numerous HP HPE0-J79 practice > test software > *HP HPE0-J79 Questions Dumps - Hidden Advantages You Should Know* > The HPE0-J79 Test Dumps that are available at our site for organizing for > these HPE0-J79 sample questions certification test have always been > definitely very helpful for our clients one way or another for the > preparation of HP HPE0-J79. They could delight in solving their favourite > HPE0-J79 pdf questions website after preparing for HPE0-J79 certification > test with the aid of our software. This HP HPE0-J79 Test Dumps, however, can > help them to prepare HP HPE0-J79 certification exam and to make it through > their HPE0-J79 exam, so that their period don't get wasted and they don't > need to stress for the preparation of HPE0-J79 certification exam. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Updated] (SYNAPSE-1050) Sample for message drop in Forward mediator
[ https://issues.apache.org/jira/browse/SYNAPSE-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Udana Loku Narangoda updated SYNAPSE-1050: Fix Version/s: 3.0.1 > Sample for message drop in Forward mediator > --- > > Key: SYNAPSE-1050 > URL: https://issues.apache.org/jira/browse/SYNAPSE-1050 > Project: Synapse > Issue Type: Sub-task >Reporter: Vanjikumaran Sivajothy >Assignee: Vanjikumaran Sivajothy > Fix For: 3.0.1 > > Attachments: SYNAPSE-1050.diff > > -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Reopened] (SYNAPSE-1050) Sample for message drop in Forward mediator
[ https://issues.apache.org/jira/browse/SYNAPSE-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Udana Loku Narangoda reopened SYNAPSE-1050: - > Sample for message drop in Forward mediator > --- > > Key: SYNAPSE-1050 > URL: https://issues.apache.org/jira/browse/SYNAPSE-1050 > Project: Synapse > Issue Type: Sub-task >Reporter: Vanjikumaran Sivajothy >Assignee: Vanjikumaran Sivajothy > Fix For: 3.0.1 > > Attachments: SYNAPSE-1050.diff > > -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Closed] (SYNAPSE-1050) Sample for message drop in Forward mediator
[ https://issues.apache.org/jira/browse/SYNAPSE-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Udana Loku Narangoda closed SYNAPSE-1050. --- Resolution: Fixed > Sample for message drop in Forward mediator > --- > > Key: SYNAPSE-1050 > URL: https://issues.apache.org/jira/browse/SYNAPSE-1050 > Project: Synapse > Issue Type: Sub-task >Reporter: Vanjikumaran Sivajothy >Assignee: Vanjikumaran Sivajothy > Fix For: 3.0.1 > > Attachments: SYNAPSE-1050.diff > > -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Commented] (SYNAPSE-1057) Spelling mistake and un handled exceptions
[ https://issues.apache.org/jira/browse/SYNAPSE-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16275822#comment-16275822 ] Isuru Udana Loku Narangoda commented on SYNAPSE-1057: - Fixed in r1809547 > Spelling mistake and un handled exceptions > -- > > Key: SYNAPSE-1057 > URL: https://issues.apache.org/jira/browse/SYNAPSE-1057 > Project: Synapse > Issue Type: Bug > Components: Core >Reporter: Vanjikumaran Sivajothy >Assignee: Vanjikumaran Sivajothy >Priority: Minor > Labels: patch > Fix For: 3.0.1 > > Attachments: SYNAPSE1057.patch > > > When DBLookup/DBreport exception happens, The flow doesn't go to > faultSequence as the handled exception. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Closed] (SYNAPSE-1095) Current Documentation is not mobile Friendly
[ https://issues.apache.org/jira/browse/SYNAPSE-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Udana Loku Narangoda closed SYNAPSE-1095. --- Resolution: Fixed > Current Documentation is not mobile Friendly > - > > Key: SYNAPSE-1095 > URL: https://issues.apache.org/jira/browse/SYNAPSE-1095 > Project: Synapse > Issue Type: Improvement >Reporter: Vanjikumaran Sivajothy >Assignee: Vanjikumaran Sivajothy > Labels: documentaion > Fix For: 3.0.1 > > Attachments: Mobile_Friendly.patch, Screen Shot 2017-01-04 at 2.36.21 > PM.png > > > Current Documentation is not mobile Friendly due the current > maven-fluido-skin. This issue can be resolved by upgrading to the version 1.6 -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Updated] (SYNAPSE-1057) Spelling mistake and un handled exceptions
[ https://issues.apache.org/jira/browse/SYNAPSE-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Udana Loku Narangoda updated SYNAPSE-1057: Fix Version/s: (was: FUTURE) 3.0.1 > Spelling mistake and un handled exceptions > -- > > Key: SYNAPSE-1057 > URL: https://issues.apache.org/jira/browse/SYNAPSE-1057 > Project: Synapse > Issue Type: Bug > Components: Core >Reporter: Vanjikumaran Sivajothy >Assignee: Vanjikumaran Sivajothy >Priority: Minor > Labels: patch > Fix For: 3.0.1 > > Attachments: SYNAPSE1057.patch > > > When DBLookup/DBreport exception happens, The flow doesn't go to > faultSequence as the handled exception. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Updated] (SYNAPSE-1095) Current Documentation is not mobile Friendly
[ https://issues.apache.org/jira/browse/SYNAPSE-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Udana Loku Narangoda updated SYNAPSE-1095: Fix Version/s: 3.0.1 > Current Documentation is not mobile Friendly > - > > Key: SYNAPSE-1095 > URL: https://issues.apache.org/jira/browse/SYNAPSE-1095 > Project: Synapse > Issue Type: Improvement >Reporter: Vanjikumaran Sivajothy >Assignee: Vanjikumaran Sivajothy > Labels: documentaion > Fix For: 3.0.1 > > Attachments: Mobile_Friendly.patch, Screen Shot 2017-01-04 at 2.36.21 > PM.png > > > Current Documentation is not mobile Friendly due the current > maven-fluido-skin. This issue can be resolved by upgrading to the version 1.6 -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Reopened] (SYNAPSE-1095) Current Documentation is not mobile Friendly
[ https://issues.apache.org/jira/browse/SYNAPSE-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Udana Loku Narangoda reopened SYNAPSE-1095: - > Current Documentation is not mobile Friendly > - > > Key: SYNAPSE-1095 > URL: https://issues.apache.org/jira/browse/SYNAPSE-1095 > Project: Synapse > Issue Type: Improvement >Reporter: Vanjikumaran Sivajothy >Assignee: Vanjikumaran Sivajothy > Labels: documentaion > Attachments: Mobile_Friendly.patch, Screen Shot 2017-01-04 at 2.36.21 > PM.png > > > Current Documentation is not mobile Friendly due the current > maven-fluido-skin. This issue can be resolved by upgrading to the version 1.6 -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Created] (SYNAPSE-1096) Synchronisation issue in callbacks in TimeoutHandler and CallbackReceiver
Isuru Udana Loku Narangoda created SYNAPSE-1096: --- Summary: Synchronisation issue in callbacks in TimeoutHandler and CallbackReceiver Key: SYNAPSE-1096 URL: https://issues.apache.org/jira/browse/SYNAPSE-1096 Project: Synapse Issue Type: Bug Reporter: Isuru Udana Loku Narangoda Assignee: Isuru Udana Loku Narangoda Due to a synchronisation issue in callbacks in TimeoutHandler and CallbackReceiver, when endpoint timeout happens there is a possibility of fault sequence is executed as well as outSequence. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Updated] (SYNAPSE-1090) Update NOTICE for 3.0.0 release
[ https://issues.apache.org/jira/browse/SYNAPSE-1090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Udana Loku Narangoda updated SYNAPSE-1090: Attachment: notice_updates_for_existing_entries.patch > Update NOTICE for 3.0.0 release > --- > > Key: SYNAPSE-1090 > URL: https://issues.apache.org/jira/browse/SYNAPSE-1090 > Project: Synapse > Issue Type: Task >Affects Versions: 3.0.0 >Reporter: Isuru Udana Loku Narangoda >Assignee: Isuru Udana Loku Narangoda >Priority: Blocker > Fix For: 3.0.0 > > Attachments: notice_updates_for_existing_entries.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Created] (SYNAPSE-1090) Update NOTICE for 3.0.0 release
Isuru Udana Loku Narangoda created SYNAPSE-1090: --- Summary: Update NOTICE for 3.0.0 release Key: SYNAPSE-1090 URL: https://issues.apache.org/jira/browse/SYNAPSE-1090 Project: Synapse Issue Type: Task Affects Versions: 3.0.0 Reporter: Isuru Udana Loku Narangoda Assignee: Isuru Udana Loku Narangoda Priority: Blocker Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Resolved] (SYNAPSE-1089) Update readme file for synapse 3.0.0 release
[ https://issues.apache.org/jira/browse/SYNAPSE-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Udana Loku Narangoda resolved SYNAPSE-1089. - Resolution: Fixed Fix Version/s: 3.0.0 > Update readme file for synapse 3.0.0 release > > > Key: SYNAPSE-1089 > URL: https://issues.apache.org/jira/browse/SYNAPSE-1089 > Project: Synapse > Issue Type: Task >Reporter: Chanaka Fernando >Assignee: Isuru Udana Loku Narangoda > Fix For: 3.0.0 > > Attachments: updated_the_readme_for_synapse_3_0_0_release.patch > > > README.txt, Notice and Building.txt files have outdated information. These > needs to be updated before the release. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Commented] (SYNAPSE-1089) Update readme file for synapse 3.0.0 release
[ https://issues.apache.org/jira/browse/SYNAPSE-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15787699#comment-15787699 ] Isuru Udana Loku Narangoda commented on SYNAPSE-1089: - Changes already made with r1776564 r1776566 > Update readme file for synapse 3.0.0 release > > > Key: SYNAPSE-1089 > URL: https://issues.apache.org/jira/browse/SYNAPSE-1089 > Project: Synapse > Issue Type: Task >Reporter: Chanaka Fernando >Assignee: Isuru Udana Loku Narangoda > Fix For: 3.0.0 > > Attachments: updated_the_readme_for_synapse_3_0_0_release.patch > > > README.txt, Notice and Building.txt files have outdated information. These > needs to be updated before the release. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Resolved] (SYNAPSE-1088) Remove Java 1.8 limitation from the docs and startup script
[ https://issues.apache.org/jira/browse/SYNAPSE-1088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Udana Loku Narangoda resolved SYNAPSE-1088. - Resolution: Fixed Fix Version/s: 3.0.0 > Remove Java 1.8 limitation from the docs and startup script > --- > > Key: SYNAPSE-1088 > URL: https://issues.apache.org/jira/browse/SYNAPSE-1088 > Project: Synapse > Issue Type: Task > Components: Documentation >Reporter: Chanaka Fernando >Assignee: Isuru Udana Loku Narangoda > Fix For: 3.0.0 > > Attachments: > Remove_the_Java_1_8_limitation_from_the_doc_and_startup_script.patch > > > In the current synapse documentation and startup script, there is a line > mentioning that it is not fully supporting Java 1.8. Better if we can remove > that part since Java 1.8 is used in most places and synapse is running on > that version without any blocking issues. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Commented] (SYNAPSE-1088) Remove Java 1.8 limitation from the docs and startup script
[ https://issues.apache.org/jira/browse/SYNAPSE-1088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15784379#comment-15784379 ] Isuru Udana Loku Narangoda commented on SYNAPSE-1088: - Committed revision 1776372. > Remove Java 1.8 limitation from the docs and startup script > --- > > Key: SYNAPSE-1088 > URL: https://issues.apache.org/jira/browse/SYNAPSE-1088 > Project: Synapse > Issue Type: Task > Components: Documentation >Reporter: Chanaka Fernando >Assignee: Isuru Udana Loku Narangoda > Fix For: 3.0.0 > > Attachments: > Remove_the_Java_1_8_limitation_from_the_doc_and_startup_script.patch > > > In the current synapse documentation and startup script, there is a line > mentioning that it is not fully supporting Java 1.8. Better if we can remove > that part since Java 1.8 is used in most places and synapse is running on > that version without any blocking issues. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Resolved] (SYNAPSE-1087) Deployment Guide - Changes
[ https://issues.apache.org/jira/browse/SYNAPSE-1087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Udana Loku Narangoda resolved SYNAPSE-1087. - Resolution: Fixed Fix Version/s: 3.0.0 > Deployment Guide - Changes > -- > > Key: SYNAPSE-1087 > URL: https://issues.apache.org/jira/browse/SYNAPSE-1087 > Project: Synapse > Issue Type: Improvement > Components: Documentation >Reporter: prabath ariyarathna >Assignee: Isuru Udana Loku Narangoda > Fix For: 3.0.0 > > Attachments: deployment_changes.diff > > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Commented] (SYNAPSE-1087) Deployment Guide - Changes
[ https://issues.apache.org/jira/browse/SYNAPSE-1087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15784239#comment-15784239 ] Isuru Udana Loku Narangoda commented on SYNAPSE-1087: - Patch applied to trunk with r1776369 > Deployment Guide - Changes > -- > > Key: SYNAPSE-1087 > URL: https://issues.apache.org/jira/browse/SYNAPSE-1087 > Project: Synapse > Issue Type: Improvement > Components: Documentation >Reporter: prabath ariyarathna >Assignee: Isuru Udana Loku Narangoda > Attachments: deployment_changes.diff > > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Resolved] (SYNAPSE-1082) Update FAQ page with the PTT informations
[ https://issues.apache.org/jira/browse/SYNAPSE-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Udana Loku Narangoda resolved SYNAPSE-1082. - Resolution: Fixed Fix Version/s: 3.0.0 Committed revision 1776367. > Update FAQ page with the PTT informations > - > > Key: SYNAPSE-1082 > URL: https://issues.apache.org/jira/browse/SYNAPSE-1082 > Project: Synapse > Issue Type: Improvement > Components: Documentation >Reporter: prabath ariyarathna >Assignee: Isuru Udana Loku Narangoda > Fix For: 3.0.0 > > Attachments: faq_Passthrough_transport.diff > > > Current documentation dose not include the PTT information under the FAQ > section -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Resolved] (SYNAPSE-1086) Developer Guide - Minor Punctuation corrections in the doc
[ https://issues.apache.org/jira/browse/SYNAPSE-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Udana Loku Narangoda resolved SYNAPSE-1086. - Resolution: Fixed Fix Version/s: 3.0.0 Committed revision 1776366. > Developer Guide - Minor Punctuation corrections in the doc > --- > > Key: SYNAPSE-1086 > URL: https://issues.apache.org/jira/browse/SYNAPSE-1086 > Project: Synapse > Issue Type: Bug > Components: Documentation >Reporter: Vanjikumaran Sivajothy >Assignee: Isuru Udana Loku Narangoda >Priority: Trivial > Fix For: 3.0.0 > > Attachments: > SYNAPSE-1086,_Developer_Guide_-_Minor_Punctuation_corrections_in_the_doc.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Resolved] (SYNAPSE-1085) Transport Catalog - Minor Punctuation corrections in the doc
[ https://issues.apache.org/jira/browse/SYNAPSE-1085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Udana Loku Narangoda resolved SYNAPSE-1085. - Resolution: Fixed Fix Version/s: 3.0.0 Committed revision 1776365. > Transport Catalog - Minor Punctuation corrections in the doc > > > Key: SYNAPSE-1085 > URL: https://issues.apache.org/jira/browse/SYNAPSE-1085 > Project: Synapse > Issue Type: Bug > Components: Documentation >Reporter: Vanjikumaran Sivajothy >Assignee: Isuru Udana Loku Narangoda >Priority: Trivial > Fix For: 3.0.0 > > Attachments: > SYNAPSE-1085,_Transport_Catalog_-_Minor_Punctuation_corrections_in_the_doc.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Resolved] (SYNAPSE-1084) Mediators Catalog - Minor corrections on the doc
[ https://issues.apache.org/jira/browse/SYNAPSE-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Udana Loku Narangoda resolved SYNAPSE-1084. - Resolution: Fixed Fix Version/s: 3.0.0 Committed revision 1776364. > Mediators Catalog - Minor corrections on the doc > > > Key: SYNAPSE-1084 > URL: https://issues.apache.org/jira/browse/SYNAPSE-1084 > Project: Synapse > Issue Type: Bug > Components: Documentation >Reporter: Vanjikumaran Sivajothy >Assignee: Isuru Udana Loku Narangoda >Priority: Trivial > Fix For: 3.0.0 > > Attachments: > SYNAPSE-1084,_Mediators_Catalog_-_Minor_corrections_on_the_doc.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Resolved] (SYNAPSE-1083) Extending Synapse page has minor issues.
[ https://issues.apache.org/jira/browse/SYNAPSE-1083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Udana Loku Narangoda resolved SYNAPSE-1083. - Resolution: Fixed Fix Version/s: 3.0.0 Committed revision 1776363. > Extending Synapse page has minor issues. > > > Key: SYNAPSE-1083 > URL: https://issues.apache.org/jira/browse/SYNAPSE-1083 > Project: Synapse > Issue Type: Bug >Reporter: Vanjikumaran Sivajothy >Assignee: Isuru Udana Loku Narangoda >Priority: Trivial > Fix For: 3.0.0 > > Attachments: SYNAPSE-1083,_minor_corrections_on_the_doc.patch > > > Patch attached for the corrections -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Resolved] (SYNAPSE-1080) Update the samples catalog documentation with new samples
[ https://issues.apache.org/jira/browse/SYNAPSE-1080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Udana Loku Narangoda resolved SYNAPSE-1080. - Resolution: Fixed Assignee: Isuru Udana Loku Narangoda (was: Ravi Undupitiya) Fix Version/s: 3.0.0 Committed revision 1776304. Thanks for the contribution. > Update the samples catalog documentation with new samples > - > > Key: SYNAPSE-1080 > URL: https://issues.apache.org/jira/browse/SYNAPSE-1080 > Project: Synapse > Issue Type: Improvement >Reporter: Chanaka Fernando >Assignee: Isuru Udana Loku Narangoda > Fix For: 3.0.0 > > Attachments: > update_samples_catalog_with_missing_documentation_samples.patch > > > Current samples catalog has some missing samples which are available in the > samples directory. There is sample 13 which is incomplete sample and need to > remove that. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Created] (SYNAPSE-1072) Update installation Guide
Isuru Udana Loku Narangoda created SYNAPSE-1072: --- Summary: Update installation Guide Key: SYNAPSE-1072 URL: https://issues.apache.org/jira/browse/SYNAPSE-1072 Project: Synapse Issue Type: Bug Reporter: Isuru Udana Loku Narangoda Assignee: Ravi Undupitiya Priority: Blocker Fix For: 3.0.0 Need to update jdk version. Maven version. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Created] (SYNAPSE-1071) Update "Upgrading" page in documentation
Isuru Udana Loku Narangoda created SYNAPSE-1071: --- Summary: Update "Upgrading" page in documentation Key: SYNAPSE-1071 URL: https://issues.apache.org/jira/browse/SYNAPSE-1071 Project: Synapse Issue Type: Task Components: Documentation Affects Versions: 3.0.0 Reporter: Isuru Udana Loku Narangoda Assignee: Ravi Undupitiya Priority: Blocker Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Resolved] (SYNAPSE-1070) Simplify samples with respond mediator
[ https://issues.apache.org/jira/browse/SYNAPSE-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Udana Loku Narangoda resolved SYNAPSE-1070. - Resolution: Fixed Fix Version/s: 3.0 > Simplify samples with respond mediator > -- > > Key: SYNAPSE-1070 > URL: https://issues.apache.org/jira/browse/SYNAPSE-1070 > Project: Synapse > Issue Type: Improvement >Reporter: Chanaka Fernando >Assignee: Isuru Udana Loku Narangoda > Fix For: 3.0 > > Attachments: samples_updated_with_respond_mediator.patch > > > Before the respond mediator, it is required to add 3 mediators (or 4) to send > a response to the client in the request path. With the respond mediator, that > requirements is not there anymore. Hence, it is possible to simplify the > samples with 3, 4 mediators. Following samples were identified. > ./synapse_sample_432.xml:39: > ./synapse_sample_470.xml:58: > ./synapse_sample_471.xml:69: > ./synapse_sample_433.xml:35: > ./synapse_sample_434.xml:37: > ./synapse_sample_850.xml:32: > ./synapse_sample_430.xml:35: > ./synapse_sample_431.xml:38: -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Comment Edited] (SYNAPSE-1070) Simplify samples with respond mediator
[ https://issues.apache.org/jira/browse/SYNAPSE-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15780769#comment-15780769 ] Isuru Udana Loku Narangoda edited comment on SYNAPSE-1070 at 12/27/16 4:53 PM: --- Patch applied with revision 1776172 with documentation update. Thanks for the contribution...! was (Author: isudana): Patch applied with revision 1776172 with documentation update. > Simplify samples with respond mediator > -- > > Key: SYNAPSE-1070 > URL: https://issues.apache.org/jira/browse/SYNAPSE-1070 > Project: Synapse > Issue Type: Improvement >Reporter: Chanaka Fernando >Assignee: Isuru Udana Loku Narangoda > Fix For: 3.0 > > Attachments: samples_updated_with_respond_mediator.patch > > > Before the respond mediator, it is required to add 3 mediators (or 4) to send > a response to the client in the request path. With the respond mediator, that > requirements is not there anymore. Hence, it is possible to simplify the > samples with 3, 4 mediators. Following samples were identified. > ./synapse_sample_432.xml:39: > ./synapse_sample_470.xml:58: > ./synapse_sample_471.xml:69: > ./synapse_sample_433.xml:35: > ./synapse_sample_434.xml:37: > ./synapse_sample_850.xml:32: > ./synapse_sample_430.xml:35: > ./synapse_sample_431.xml:38: -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Commented] (SYNAPSE-1070) Simplify samples with respond mediator
[ https://issues.apache.org/jira/browse/SYNAPSE-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15780769#comment-15780769 ] Isuru Udana Loku Narangoda commented on SYNAPSE-1070: - Patch applied with revision 1776172 with documentation update. > Simplify samples with respond mediator > -- > > Key: SYNAPSE-1070 > URL: https://issues.apache.org/jira/browse/SYNAPSE-1070 > Project: Synapse > Issue Type: Improvement >Reporter: Chanaka Fernando >Assignee: Isuru Udana Loku Narangoda > Attachments: samples_updated_with_respond_mediator.patch > > > Before the respond mediator, it is required to add 3 mediators (or 4) to send > a response to the client in the request path. With the respond mediator, that > requirements is not there anymore. Hence, it is possible to simplify the > samples with 3, 4 mediators. Following samples were identified. > ./synapse_sample_432.xml:39: > ./synapse_sample_470.xml:58: > ./synapse_sample_471.xml:69: > ./synapse_sample_433.xml:35: > ./synapse_sample_434.xml:37: > ./synapse_sample_850.xml:32: > ./synapse_sample_430.xml:35: > ./synapse_sample_431.xml:38: -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Resolved] (SYNAPSE-1069) log4j.properties file is located in lib directory which is hard to find and not make much sense
[ https://issues.apache.org/jira/browse/SYNAPSE-1069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Udana Loku Narangoda resolved SYNAPSE-1069. - Resolution: Fixed Fix Version/s: 3.0 > log4j.properties file is located in lib directory which is hard to find and > not make much sense > --- > > Key: SYNAPSE-1069 > URL: https://issues.apache.org/jira/browse/SYNAPSE-1069 > Project: Synapse > Issue Type: Improvement >Reporter: Chanaka Fernando >Assignee: Isuru Udana Loku Narangoda > Fix For: 3.0 > > Attachments: log4j_file_move.patch > > > It was hard to find the log4j.properties file since it was in the lib > directory. With this patch, it has been moved to repository/conf directory > which makes more sense. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Updated] (SYNAPSE-1069) log4j.properties file is located in lib directory which is hard to find and not make much sense
[ https://issues.apache.org/jira/browse/SYNAPSE-1069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Udana Loku Narangoda updated SYNAPSE-1069: Issue Type: Improvement (was: Bug) > log4j.properties file is located in lib directory which is hard to find and > not make much sense > --- > > Key: SYNAPSE-1069 > URL: https://issues.apache.org/jira/browse/SYNAPSE-1069 > Project: Synapse > Issue Type: Improvement >Reporter: Chanaka Fernando >Assignee: Isuru Udana Loku Narangoda > Fix For: 3.0 > > Attachments: log4j_file_move.patch > > > It was hard to find the log4j.properties file since it was in the lib > directory. With this patch, it has been moved to repository/conf directory > which makes more sense. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Resolved] (SYNAPSE-1014) NPE in DefaultNHttpClientConnection consumeInput, when invoking a proxy concurrently
[
https://issues.apache.org/jira/browse/SYNAPSE-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Isuru Udana Loku Narangoda resolved SYNAPSE-1014.
-
Resolution: Fixed
Fix Version/s: 3.0
> NPE in DefaultNHttpClientConnection consumeInput, when invoking a proxy
> concurrently
>
>
> Key: SYNAPSE-1014
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1014
> Project: Synapse
> Issue Type: Bug
> Components: Transports
>Affects Versions: 2.1
>Reporter: Senduran
>Assignee: Isuru Udana Loku Narangoda
>Priority: Blocker
> Fix For: 3.0
>
> Attachments: EchoProxy.xml, HelloProxy.xml, PassthroughLoadtest.jmx,
> http_core_4_4.log, ptt-100-1000.csv, ptt-200-1000.csv, ptt-300-1000.csv,
> ptt-400-1000.csv, ptt-500-1000.csv
>
>
> When invoking a content aware passthrough proxy at a concurrency of 100. the
> following exception occurs
> {code}
> ERROR TargetHandler Unexpected exception encountered in TargetHandler
> java.lang.NullPointerException
> at
> org.apache.http.impl.nio.DefaultNHttpClientConnection.consumeInput(DefaultNHttpClientConnection.java:268)
> at
> org.apache.http.impl.nio.DefaultHttpClientIODispatch.onInputReady(DefaultHttpClientIODispatch.java:165)
> at
> org.apache.http.impl.nio.DefaultHttpClientIODispatch.onInputReady(DefaultHttpClientIODispatch.java:51)
> at
> org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:113)
> at
> org.apache.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:159)
> at
> org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:338)
> at
> org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:316)
> at
> org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:277)
> at
> org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:105)
> at
> org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:584)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Commented] (SYNAPSE-1014) NPE in DefaultNHttpClientConnection consumeInput, when invoking a proxy concurrently
[
https://issues.apache.org/jira/browse/SYNAPSE-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15780412#comment-15780412
]
Isuru Udana Loku Narangoda commented on SYNAPSE-1014:
-
Thanks Chanaka and Prabath, I'll close this issue.
> NPE in DefaultNHttpClientConnection consumeInput, when invoking a proxy
> concurrently
>
>
> Key: SYNAPSE-1014
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1014
> Project: Synapse
> Issue Type: Bug
> Components: Transports
>Affects Versions: 2.1
>Reporter: Senduran
>Assignee: Isuru Udana Loku Narangoda
>Priority: Blocker
> Fix For: 3.0
>
> Attachments: EchoProxy.xml, HelloProxy.xml, PassthroughLoadtest.jmx,
> http_core_4_4.log, ptt-100-1000.csv, ptt-200-1000.csv, ptt-300-1000.csv,
> ptt-400-1000.csv, ptt-500-1000.csv
>
>
> When invoking a content aware passthrough proxy at a concurrency of 100. the
> following exception occurs
> {code}
> ERROR TargetHandler Unexpected exception encountered in TargetHandler
> java.lang.NullPointerException
> at
> org.apache.http.impl.nio.DefaultNHttpClientConnection.consumeInput(DefaultNHttpClientConnection.java:268)
> at
> org.apache.http.impl.nio.DefaultHttpClientIODispatch.onInputReady(DefaultHttpClientIODispatch.java:165)
> at
> org.apache.http.impl.nio.DefaultHttpClientIODispatch.onInputReady(DefaultHttpClientIODispatch.java:51)
> at
> org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:113)
> at
> org.apache.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:159)
> at
> org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:338)
> at
> org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:316)
> at
> org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:277)
> at
> org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:105)
> at
> org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:584)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Updated] (SYNAPSE-1057) Spelling mistake and un handled exceptions
[ https://issues.apache.org/jira/browse/SYNAPSE-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Udana Loku Narangoda updated SYNAPSE-1057: Fix Version/s: (was: 3.0) > Spelling mistake and un handled exceptions > -- > > Key: SYNAPSE-1057 > URL: https://issues.apache.org/jira/browse/SYNAPSE-1057 > Project: Synapse > Issue Type: Bug > Components: Core >Reporter: Vanjikumaran Sivajothy >Assignee: Hiranya Jayathilaka >Priority: Minor > Labels: patch > Fix For: FUTURE > > Attachments: SYNAPSE1057.patch > > > When DBLookup/DBreport exception happens, The flow doesn't go to > faultSequence as the handled exception. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Updated] (SYNAPSE-502) improve the vfs transport to use temporary file
[ https://issues.apache.org/jira/browse/SYNAPSE-502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Udana Loku Narangoda updated SYNAPSE-502: --- Fix Version/s: (was: 3.0) FUTURE > improve the vfs transport to use temporary file > --- > > Key: SYNAPSE-502 > URL: https://issues.apache.org/jira/browse/SYNAPSE-502 > Project: Synapse > Issue Type: Improvement > Components: Transports > Environment: All >Reporter: Otto Frost >Assignee: Rajika Kumarasiri > Fix For: FUTURE > > Attachments: SYNAPSE-502.patch > > Original Estimate: 24h > Remaining Estimate: 24h > > Enhance the vfs transport to use a temporary file at upload. > The reason is to prevent the receiving application to start reading the > uploaded-file (put) before it is completely written. > Of course the temp file has to be on the same physical filesystem. > This feature should work for ftp/sftp/local file/... > It should be similar in funcitonality as what SAP XI has at the ftp/file > adapter. > See > http://help.sap.com/saphelp_nw04/helpdata/en/0b/9a50465ccf84479e39a6d50c90fb3f/content.htm > See the receiver file adapter (the system xi communicates with receives data). > See the option TargetTempFileName > If there is already this functionality, it would be good idea to include how > to solve the problem in the examples. Of course the best solution is to use > MOM, but sometimes that isn't an option. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Comment Edited] (SYNAPSE-1014) NPE in DefaultNHttpClientConnection consumeInput, when invoking a proxy concurrently
[
https://issues.apache.org/jira/browse/SYNAPSE-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15780113#comment-15780113
]
Isuru Udana Loku Narangoda edited comment on SYNAPSE-1014 at 12/27/16 10:23 AM:
[~prabathariyarathna] [~chanakaudaya] Can you please check whether NPE is
solved with the recent fix in trunk ?
was (Author: isudana):
[~prabathariyarathna] [~chanakaudaya] Can you please check whether NPE is
solved with the latest trunk ?
> NPE in DefaultNHttpClientConnection consumeInput, when invoking a proxy
> concurrently
>
>
> Key: SYNAPSE-1014
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1014
> Project: Synapse
> Issue Type: Bug
> Components: Transports
>Affects Versions: 2.1
>Reporter: Senduran
>Assignee: Isuru Udana Loku Narangoda
>Priority: Blocker
> Attachments: HelloProxy.xml, http_core_4_4.log
>
>
> When invoking a content aware passthrough proxy at a concurrency of 100. the
> following exception occurs
> {code}
> ERROR TargetHandler Unexpected exception encountered in TargetHandler
> java.lang.NullPointerException
> at
> org.apache.http.impl.nio.DefaultNHttpClientConnection.consumeInput(DefaultNHttpClientConnection.java:268)
> at
> org.apache.http.impl.nio.DefaultHttpClientIODispatch.onInputReady(DefaultHttpClientIODispatch.java:165)
> at
> org.apache.http.impl.nio.DefaultHttpClientIODispatch.onInputReady(DefaultHttpClientIODispatch.java:51)
> at
> org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:113)
> at
> org.apache.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:159)
> at
> org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:338)
> at
> org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:316)
> at
> org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:277)
> at
> org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:105)
> at
> org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:584)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Commented] (SYNAPSE-1014) NPE in DefaultNHttpClientConnection consumeInput, when invoking a proxy concurrently
[
https://issues.apache.org/jira/browse/SYNAPSE-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15780113#comment-15780113
]
Isuru Udana Loku Narangoda commented on SYNAPSE-1014:
-
[~prabathariyarathna] [~chanakaudaya] Can you please check whether NPE is
solved with the latest trunk ?
> NPE in DefaultNHttpClientConnection consumeInput, when invoking a proxy
> concurrently
>
>
> Key: SYNAPSE-1014
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1014
> Project: Synapse
> Issue Type: Bug
> Components: Transports
>Affects Versions: 2.1
>Reporter: Senduran
>Assignee: Isuru Udana Loku Narangoda
>Priority: Blocker
> Attachments: HelloProxy.xml, http_core_4_4.log
>
>
> When invoking a content aware passthrough proxy at a concurrency of 100. the
> following exception occurs
> {code}
> ERROR TargetHandler Unexpected exception encountered in TargetHandler
> java.lang.NullPointerException
> at
> org.apache.http.impl.nio.DefaultNHttpClientConnection.consumeInput(DefaultNHttpClientConnection.java:268)
> at
> org.apache.http.impl.nio.DefaultHttpClientIODispatch.onInputReady(DefaultHttpClientIODispatch.java:165)
> at
> org.apache.http.impl.nio.DefaultHttpClientIODispatch.onInputReady(DefaultHttpClientIODispatch.java:51)
> at
> org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:113)
> at
> org.apache.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:159)
> at
> org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:338)
> at
> org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:316)
> at
> org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:277)
> at
> org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:105)
> at
> org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:584)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Commented] (SYNAPSE-1014) NPE in DefaultNHttpClientConnection consumeInput, when invoking a proxy concurrently
[
https://issues.apache.org/jira/browse/SYNAPSE-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15780110#comment-15780110
]
Isuru Udana Loku Narangoda commented on SYNAPSE-1014:
-
Created a separate ticket (SYNAPSE-1067) to keep track of HTTP Core upgrade.
> NPE in DefaultNHttpClientConnection consumeInput, when invoking a proxy
> concurrently
>
>
> Key: SYNAPSE-1014
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1014
> Project: Synapse
> Issue Type: Bug
> Components: Transports
>Affects Versions: 2.1
>Reporter: Senduran
>Assignee: Isuru Udana Loku Narangoda
>Priority: Blocker
> Attachments: HelloProxy.xml, http_core_4_4.log
>
>
> When invoking a content aware passthrough proxy at a concurrency of 100. the
> following exception occurs
> {code}
> ERROR TargetHandler Unexpected exception encountered in TargetHandler
> java.lang.NullPointerException
> at
> org.apache.http.impl.nio.DefaultNHttpClientConnection.consumeInput(DefaultNHttpClientConnection.java:268)
> at
> org.apache.http.impl.nio.DefaultHttpClientIODispatch.onInputReady(DefaultHttpClientIODispatch.java:165)
> at
> org.apache.http.impl.nio.DefaultHttpClientIODispatch.onInputReady(DefaultHttpClientIODispatch.java:51)
> at
> org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:113)
> at
> org.apache.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:159)
> at
> org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:338)
> at
> org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:316)
> at
> org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:277)
> at
> org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:105)
> at
> org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:584)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Created] (SYNAPSE-1067) Upgrade to HTTP Core 4.4
Isuru Udana Loku Narangoda created SYNAPSE-1067: --- Summary: Upgrade to HTTP Core 4.4 Key: SYNAPSE-1067 URL: https://issues.apache.org/jira/browse/SYNAPSE-1067 Project: Synapse Issue Type: Task Reporter: Isuru Udana Loku Narangoda Assignee: Ravi Undupitiya Fix For: FUTURE Attachments: http_core_4_4.log Current HTTP Core version used is 4.3.3. Attempt to upgrade to 4.4.0 failed with an error which can be found on the attachment. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Updated] (SYNAPSE-1067) Upgrade to HTTP Core 4.4
[ https://issues.apache.org/jira/browse/SYNAPSE-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Udana Loku Narangoda updated SYNAPSE-1067: Attachment: http_core_4_4.log > Upgrade to HTTP Core 4.4 > > > Key: SYNAPSE-1067 > URL: https://issues.apache.org/jira/browse/SYNAPSE-1067 > Project: Synapse > Issue Type: Task >Reporter: Isuru Udana Loku Narangoda >Assignee: Ravi Undupitiya > Fix For: FUTURE > > Attachments: http_core_4_4.log > > > Current HTTP Core version used is 4.3.3. > Attempt to upgrade to 4.4.0 failed with an error which can be found on the > attachment. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Commented] (SYNAPSE-1014) NPE in DefaultNHttpClientConnection consumeInput, when invoking a proxy concurrently
[
https://issues.apache.org/jira/browse/SYNAPSE-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15780102#comment-15780102
]
Isuru Udana Loku Narangoda commented on SYNAPSE-1014:
-
Ported a fix from
https://github.com/wso2/wso2-synapse/commit/fbc829ae1e52c552aa348967db929fa21a8cf1f6
by Isuru Ranawaka and applied to trunk at r1776101.
> NPE in DefaultNHttpClientConnection consumeInput, when invoking a proxy
> concurrently
>
>
> Key: SYNAPSE-1014
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1014
> Project: Synapse
> Issue Type: Bug
> Components: Transports
>Affects Versions: 2.1
>Reporter: Senduran
>Assignee: Isuru Udana Loku Narangoda
>Priority: Blocker
> Attachments: HelloProxy.xml, http_core_4_4.log
>
>
> When invoking a content aware passthrough proxy at a concurrency of 100. the
> following exception occurs
> {code}
> ERROR TargetHandler Unexpected exception encountered in TargetHandler
> java.lang.NullPointerException
> at
> org.apache.http.impl.nio.DefaultNHttpClientConnection.consumeInput(DefaultNHttpClientConnection.java:268)
> at
> org.apache.http.impl.nio.DefaultHttpClientIODispatch.onInputReady(DefaultHttpClientIODispatch.java:165)
> at
> org.apache.http.impl.nio.DefaultHttpClientIODispatch.onInputReady(DefaultHttpClientIODispatch.java:51)
> at
> org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:113)
> at
> org.apache.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:159)
> at
> org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:338)
> at
> org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:316)
> at
> org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:277)
> at
> org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:105)
> at
> org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:584)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Assigned] (SYNAPSE-1014) NPE in DefaultNHttpClientConnection consumeInput, when invoking a proxy concurrently
[
https://issues.apache.org/jira/browse/SYNAPSE-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Isuru Udana Loku Narangoda reassigned SYNAPSE-1014:
---
Assignee: Isuru Udana Loku Narangoda (was: Hiranya Jayathilaka)
> NPE in DefaultNHttpClientConnection consumeInput, when invoking a proxy
> concurrently
>
>
> Key: SYNAPSE-1014
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1014
> Project: Synapse
> Issue Type: Bug
> Components: Transports
>Affects Versions: 2.1
>Reporter: Senduran
>Assignee: Isuru Udana Loku Narangoda
>Priority: Blocker
> Attachments: HelloProxy.xml, http_core_4_4.log
>
>
> When invoking a content aware passthrough proxy at a concurrency of 100. the
> following exception occurs
> {code}
> ERROR TargetHandler Unexpected exception encountered in TargetHandler
> java.lang.NullPointerException
> at
> org.apache.http.impl.nio.DefaultNHttpClientConnection.consumeInput(DefaultNHttpClientConnection.java:268)
> at
> org.apache.http.impl.nio.DefaultHttpClientIODispatch.onInputReady(DefaultHttpClientIODispatch.java:165)
> at
> org.apache.http.impl.nio.DefaultHttpClientIODispatch.onInputReady(DefaultHttpClientIODispatch.java:51)
> at
> org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:113)
> at
> org.apache.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:159)
> at
> org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:338)
> at
> org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:316)
> at
> org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:277)
> at
> org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:105)
> at
> org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:584)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Resolved] (SYNAPSE-1064) NullPointerException exception occurred while testing the JMS to HTTP scenarios with the high load
[ https://issues.apache.org/jira/browse/SYNAPSE-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Udana Loku Narangoda resolved SYNAPSE-1064. - Resolution: Duplicate Assignee: Isuru Udana Loku Narangoda (was: Hiranya Jayathilaka) Duplicates to SYNAPSE-1014 > NullPointerException exception occurred while testing the JMS to HTTP > scenarios with the high load > --- > > Key: SYNAPSE-1064 > URL: https://issues.apache.org/jira/browse/SYNAPSE-1064 > Project: Synapse > Issue Type: Bug > Components: Transports >Reporter: prabath ariyarathna >Assignee: Isuru Udana Loku Narangoda >Priority: Blocker > Attachments: synapse.log > > > 1. Occured following NullPointerException while testing the sample > 250(JMS-HTTP) > 2016-12-26 13:09:47,439 [-] [HTTP-PT-Sender I/O Dispatcher-4] ERROR > TargetHandler Unexpected exception encountered in TargetHandler > java.lang.NullPointerException > at > org.apache.http.impl.nio.DefaultNHttpClientConnection.consumeInput(DefaultNHttpClientConnection.java:265) > at > org.apache.http.impl.nio.DefaultHttpClientIODispatch.onInputReady(DefaultHttpClientIODispatch.java:165) > at > org.apache.http.impl.nio.DefaultHttpClientIODispatch.onInputReady(DefaultHttpClientIODispatch.java:51) > at > org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:113) > at > org.apache.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:159) > at > org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:338) > at > org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:316) > at > org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:277) > at > org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:105) > at > org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:586) > at java.lang.Thread.run(Thread.java:745) -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Commented] (SYNAPSE-1065) GC Overhead limit exceeded error during running a performance test on simple Passthough Proxy
[
https://issues.apache.org/jira/browse/SYNAPSE-1065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15779464#comment-15779464
]
Isuru Udana Loku Narangoda commented on SYNAPSE-1065:
-
Increased heap allocation to 512M with revision 1776084.
> GC Overhead limit exceeded error during running a performance test on simple
> Passthough Proxy
> -
>
> Key: SYNAPSE-1065
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1065
> Project: Synapse
> Issue Type: Bug
> Components: Proxy Services, Transports
>Affects Versions: 3.0
> Environment: ubuntu 16.04
> 4 core 8GB RAM
>Reporter: Chanaka Fernando
>Assignee: Hiranya Jayathilaka
>Priority: Critical
> Fix For: 3.0
>
> Attachments: EchoProxy.xml, PassthroughLoadtest.jmx
>
>
> I have a simple Passthrough Proxy and a back end service which is written in
> netty and simply echo back the request message. When I run a performance test
> using Jmeter (with 100 concurrency), I am getting the following errors in the
> synapse log file and console.
> {noformat}
> 2016-12-26 23:09:32,376 [-] [Timer-1] WARN TimeoutHandler Expiring message
> ID : urn:uuid:155fee35-098b-4968-a13f-efd7b755dfc2; dropping message after
> global timeout of : 180 seconds
> 2016-12-26 23:09:47,475 [-] [Timer-1] WARN TimeoutHandler Expiring message
> ID : urn:uuid:6576e483-4cb3-4111-aaf4-523a7e87781b; dropping message after
> global timeout of : 180 seconds
> 2016-12-26 23:09:54,606 [-] [HTTP-PT-Listener I/O Dispatcher-1] WARN
> SourceHandler Connection closed after request is read: [ACTIVE]
> 2016-12-26 23:09:54,802 [-] [HTTP-PT-Listener I/O Dispatcher-1] WARN
> SourceHandler Connection closed after request is read: [ACTIVE]
> Exception: java.lang.OutOfMemoryError thrown from the
> UncaughtExceptionHandler in thread "HTTP-PT-Listener I/O Dispatcher-3"
> 2016-12-26 23:09:55,506 [-] [HTTP-PT-Listener I/O Dispatcher-1] WARN
> SourceHandler Connection closed after request is read: [ACTIVE]
> 2016-12-26 23:09:57,620 [-] [HTTP-PT-Listener I/O Dispatcher-1] WARN
> SourceHandler Connection closed after request is read: [ACTIVE]
> 2016-12-26 23:09:58,137 [-] [HTTP-PT-Listener I/O Dispatcher-1] WARN
> SourceHandler Connection closed after request is read: [ACTIVE]
> Exception in thread "PassThroughMessageProcessor-30" 2016-12-26 23:09:58,532
> [-] [HTTP-PT-Listener I/O Dispatcher-1] WARN SourceHandler Connection closed
> after request is read: [ACTIVE]
> java.lang.OutOfMemoryError: GC overhead limit exceeded
> 2016-12-26 23:09:59,097 [-] [HTTP-PT-Listener I/O Dispatcher-1] WARN
> SourceHandler Connection closed after request is read: [ACTIVE]
> 2016-12-26 23:09:58,870 [-] [HTTP-PT-Listener I/O Dispatcher-2] WARN
> SourceHandler Connection closed after request is read: [ACTIVE]
> Exception in thread "HTTP-PT-Listener I/O Dispatcher-2"
> java.lang.OutOfMemoryError: GC overhead limit exceeded
> 2016-12-26 23:10:00,459 [-] [HTTP-PT-Listener I/O Dispatcher-1] WARN
> SourceHandler Connection closed after request is read: [ACTIVE]
> Exception in thread "PassThroughHTTPListener" java.lang.OutOfMemoryError: GC
> overhead limit exceeded
> 2016-12-26 23:10:02,742 [-] [Timer-1] WARN TimeoutHandler Expiring message
> ID : urn:uuid:3782bf1e-f012-44f1-923b-43dad4050ac4; dropping message after
> global timeout of : 180 seconds
> Exception in thread "PassThroughMessageProcessor-53" 2016-12-26 23:10:03,029
> [-] [HTTP-PT-Listener I/O Dispatcher-1] WARN SourceHandler Connection closed
> after request is read: [ACTIVE]
> java.lang.OutOfMemoryError: GC overhead limit exceeded
> Exception in thread "HTTP-PT-Listener I/O Dispatcher-1"
> java.lang.OutOfMemoryError: GC overhead limit exceeded
> Exception in thread "PassThroughHTTPSender" java.lang.OutOfMemoryError: GC
> overhead limit exceeded
> Exception in thread "PassThroughMessageProcessor-34"
> java.lang.OutOfMemoryError: GC overhead limit exceeded
> Exception in thread "HTTPS-PT-Listener I/O Dispatcher-3"
> java.lang.OutOfMemoryError: GC overhead limit exceeded
> Exception in thread "HTTP-PT-Listener I/O Dispatcher-4"
> java.lang.OutOfMemoryError: GC overhead limit exceeded
> Exception in thread "PassThroughMessageProcessor-357"
> java.lang.OutOfMemoryError: GC overhead limit exceeded
> Exception in thread "PassThroughMessageProcessor-212"
> java.lang.OutOfMemoryError: GC overhead limit exceeded
> Exception in thread "PassThroughMessageProcessor-247"
> java.lang.OutOfMemoryError: GC overhead limit exceeded
> Exception in thread "HTTPS-PT-Sender I/O Dispatcher-2" Exception in thread
> "HTTPS-PT-Listener I/O Dispatcher-4" java.lang.OutOfMemoryError: GC overhead
> limit exceeded
> Exception in thread "HTTP-PT-Sender I/O Dispatcher-1"
[jira] [Resolved] (SYNAPSE-1065) GC Overhead limit exceeded error during running a performance test on simple Passthough Proxy
[
https://issues.apache.org/jira/browse/SYNAPSE-1065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Isuru Udana Loku Narangoda resolved SYNAPSE-1065.
-
Resolution: Fixed
Assignee: Isuru Udana Loku Narangoda (was: Hiranya Jayathilaka)
Fix Version/s: 3.0
> GC Overhead limit exceeded error during running a performance test on simple
> Passthough Proxy
> -
>
> Key: SYNAPSE-1065
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1065
> Project: Synapse
> Issue Type: Bug
> Components: Proxy Services, Transports
>Affects Versions: 3.0
> Environment: ubuntu 16.04
> 4 core 8GB RAM
>Reporter: Chanaka Fernando
>Assignee: Isuru Udana Loku Narangoda
>Priority: Critical
> Fix For: 3.0
>
> Attachments: EchoProxy.xml, PassthroughLoadtest.jmx
>
>
> I have a simple Passthrough Proxy and a back end service which is written in
> netty and simply echo back the request message. When I run a performance test
> using Jmeter (with 100 concurrency), I am getting the following errors in the
> synapse log file and console.
> {noformat}
> 2016-12-26 23:09:32,376 [-] [Timer-1] WARN TimeoutHandler Expiring message
> ID : urn:uuid:155fee35-098b-4968-a13f-efd7b755dfc2; dropping message after
> global timeout of : 180 seconds
> 2016-12-26 23:09:47,475 [-] [Timer-1] WARN TimeoutHandler Expiring message
> ID : urn:uuid:6576e483-4cb3-4111-aaf4-523a7e87781b; dropping message after
> global timeout of : 180 seconds
> 2016-12-26 23:09:54,606 [-] [HTTP-PT-Listener I/O Dispatcher-1] WARN
> SourceHandler Connection closed after request is read: [ACTIVE]
> 2016-12-26 23:09:54,802 [-] [HTTP-PT-Listener I/O Dispatcher-1] WARN
> SourceHandler Connection closed after request is read: [ACTIVE]
> Exception: java.lang.OutOfMemoryError thrown from the
> UncaughtExceptionHandler in thread "HTTP-PT-Listener I/O Dispatcher-3"
> 2016-12-26 23:09:55,506 [-] [HTTP-PT-Listener I/O Dispatcher-1] WARN
> SourceHandler Connection closed after request is read: [ACTIVE]
> 2016-12-26 23:09:57,620 [-] [HTTP-PT-Listener I/O Dispatcher-1] WARN
> SourceHandler Connection closed after request is read: [ACTIVE]
> 2016-12-26 23:09:58,137 [-] [HTTP-PT-Listener I/O Dispatcher-1] WARN
> SourceHandler Connection closed after request is read: [ACTIVE]
> Exception in thread "PassThroughMessageProcessor-30" 2016-12-26 23:09:58,532
> [-] [HTTP-PT-Listener I/O Dispatcher-1] WARN SourceHandler Connection closed
> after request is read: [ACTIVE]
> java.lang.OutOfMemoryError: GC overhead limit exceeded
> 2016-12-26 23:09:59,097 [-] [HTTP-PT-Listener I/O Dispatcher-1] WARN
> SourceHandler Connection closed after request is read: [ACTIVE]
> 2016-12-26 23:09:58,870 [-] [HTTP-PT-Listener I/O Dispatcher-2] WARN
> SourceHandler Connection closed after request is read: [ACTIVE]
> Exception in thread "HTTP-PT-Listener I/O Dispatcher-2"
> java.lang.OutOfMemoryError: GC overhead limit exceeded
> 2016-12-26 23:10:00,459 [-] [HTTP-PT-Listener I/O Dispatcher-1] WARN
> SourceHandler Connection closed after request is read: [ACTIVE]
> Exception in thread "PassThroughHTTPListener" java.lang.OutOfMemoryError: GC
> overhead limit exceeded
> 2016-12-26 23:10:02,742 [-] [Timer-1] WARN TimeoutHandler Expiring message
> ID : urn:uuid:3782bf1e-f012-44f1-923b-43dad4050ac4; dropping message after
> global timeout of : 180 seconds
> Exception in thread "PassThroughMessageProcessor-53" 2016-12-26 23:10:03,029
> [-] [HTTP-PT-Listener I/O Dispatcher-1] WARN SourceHandler Connection closed
> after request is read: [ACTIVE]
> java.lang.OutOfMemoryError: GC overhead limit exceeded
> Exception in thread "HTTP-PT-Listener I/O Dispatcher-1"
> java.lang.OutOfMemoryError: GC overhead limit exceeded
> Exception in thread "PassThroughHTTPSender" java.lang.OutOfMemoryError: GC
> overhead limit exceeded
> Exception in thread "PassThroughMessageProcessor-34"
> java.lang.OutOfMemoryError: GC overhead limit exceeded
> Exception in thread "HTTPS-PT-Listener I/O Dispatcher-3"
> java.lang.OutOfMemoryError: GC overhead limit exceeded
> Exception in thread "HTTP-PT-Listener I/O Dispatcher-4"
> java.lang.OutOfMemoryError: GC overhead limit exceeded
> Exception in thread "PassThroughMessageProcessor-357"
> java.lang.OutOfMemoryError: GC overhead limit exceeded
> Exception in thread "PassThroughMessageProcessor-212"
> java.lang.OutOfMemoryError: GC overhead limit exceeded
> Exception in thread "PassThroughMessageProcessor-247"
> java.lang.OutOfMemoryError: GC overhead limit exceeded
> Exception in thread "HTTPS-PT-Sender I/O Dispatcher-2" Exception in thread
> "HTTPS-PT-Listener I/O Dispatcher-4" java.lang.OutOfMemoryError: GC overhead
> limit exceeded
> Exception in thread
[jira] [Commented] (SYNAPSE-1065) GC Overhead limit exceeded error during running a performance test on simple Passthough Proxy
[
https://issues.apache.org/jira/browse/SYNAPSE-1065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15779460#comment-15779460
]
Isuru Udana Loku Narangoda commented on SYNAPSE-1065:
-
+1. Let's increase the default heap allocation to 512MB.
> GC Overhead limit exceeded error during running a performance test on simple
> Passthough Proxy
> -
>
> Key: SYNAPSE-1065
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1065
> Project: Synapse
> Issue Type: Bug
> Components: Proxy Services, Transports
>Affects Versions: 3.0
> Environment: ubuntu 16.04
> 4 core 8GB RAM
>Reporter: Chanaka Fernando
>Assignee: Hiranya Jayathilaka
>Priority: Critical
> Attachments: EchoProxy.xml, PassthroughLoadtest.jmx
>
>
> I have a simple Passthrough Proxy and a back end service which is written in
> netty and simply echo back the request message. When I run a performance test
> using Jmeter (with 100 concurrency), I am getting the following errors in the
> synapse log file and console.
> {noformat}
> 2016-12-26 23:09:32,376 [-] [Timer-1] WARN TimeoutHandler Expiring message
> ID : urn:uuid:155fee35-098b-4968-a13f-efd7b755dfc2; dropping message after
> global timeout of : 180 seconds
> 2016-12-26 23:09:47,475 [-] [Timer-1] WARN TimeoutHandler Expiring message
> ID : urn:uuid:6576e483-4cb3-4111-aaf4-523a7e87781b; dropping message after
> global timeout of : 180 seconds
> 2016-12-26 23:09:54,606 [-] [HTTP-PT-Listener I/O Dispatcher-1] WARN
> SourceHandler Connection closed after request is read: [ACTIVE]
> 2016-12-26 23:09:54,802 [-] [HTTP-PT-Listener I/O Dispatcher-1] WARN
> SourceHandler Connection closed after request is read: [ACTIVE]
> Exception: java.lang.OutOfMemoryError thrown from the
> UncaughtExceptionHandler in thread "HTTP-PT-Listener I/O Dispatcher-3"
> 2016-12-26 23:09:55,506 [-] [HTTP-PT-Listener I/O Dispatcher-1] WARN
> SourceHandler Connection closed after request is read: [ACTIVE]
> 2016-12-26 23:09:57,620 [-] [HTTP-PT-Listener I/O Dispatcher-1] WARN
> SourceHandler Connection closed after request is read: [ACTIVE]
> 2016-12-26 23:09:58,137 [-] [HTTP-PT-Listener I/O Dispatcher-1] WARN
> SourceHandler Connection closed after request is read: [ACTIVE]
> Exception in thread "PassThroughMessageProcessor-30" 2016-12-26 23:09:58,532
> [-] [HTTP-PT-Listener I/O Dispatcher-1] WARN SourceHandler Connection closed
> after request is read: [ACTIVE]
> java.lang.OutOfMemoryError: GC overhead limit exceeded
> 2016-12-26 23:09:59,097 [-] [HTTP-PT-Listener I/O Dispatcher-1] WARN
> SourceHandler Connection closed after request is read: [ACTIVE]
> 2016-12-26 23:09:58,870 [-] [HTTP-PT-Listener I/O Dispatcher-2] WARN
> SourceHandler Connection closed after request is read: [ACTIVE]
> Exception in thread "HTTP-PT-Listener I/O Dispatcher-2"
> java.lang.OutOfMemoryError: GC overhead limit exceeded
> 2016-12-26 23:10:00,459 [-] [HTTP-PT-Listener I/O Dispatcher-1] WARN
> SourceHandler Connection closed after request is read: [ACTIVE]
> Exception in thread "PassThroughHTTPListener" java.lang.OutOfMemoryError: GC
> overhead limit exceeded
> 2016-12-26 23:10:02,742 [-] [Timer-1] WARN TimeoutHandler Expiring message
> ID : urn:uuid:3782bf1e-f012-44f1-923b-43dad4050ac4; dropping message after
> global timeout of : 180 seconds
> Exception in thread "PassThroughMessageProcessor-53" 2016-12-26 23:10:03,029
> [-] [HTTP-PT-Listener I/O Dispatcher-1] WARN SourceHandler Connection closed
> after request is read: [ACTIVE]
> java.lang.OutOfMemoryError: GC overhead limit exceeded
> Exception in thread "HTTP-PT-Listener I/O Dispatcher-1"
> java.lang.OutOfMemoryError: GC overhead limit exceeded
> Exception in thread "PassThroughHTTPSender" java.lang.OutOfMemoryError: GC
> overhead limit exceeded
> Exception in thread "PassThroughMessageProcessor-34"
> java.lang.OutOfMemoryError: GC overhead limit exceeded
> Exception in thread "HTTPS-PT-Listener I/O Dispatcher-3"
> java.lang.OutOfMemoryError: GC overhead limit exceeded
> Exception in thread "HTTP-PT-Listener I/O Dispatcher-4"
> java.lang.OutOfMemoryError: GC overhead limit exceeded
> Exception in thread "PassThroughMessageProcessor-357"
> java.lang.OutOfMemoryError: GC overhead limit exceeded
> Exception in thread "PassThroughMessageProcessor-212"
> java.lang.OutOfMemoryError: GC overhead limit exceeded
> Exception in thread "PassThroughMessageProcessor-247"
> java.lang.OutOfMemoryError: GC overhead limit exceeded
> Exception in thread "HTTPS-PT-Sender I/O Dispatcher-2" Exception in thread
> "HTTPS-PT-Listener I/O Dispatcher-4" java.lang.OutOfMemoryError: GC overhead
> limit exceeded
> Exception in thread "HTTP-PT-Sender I/O Dispatcher-1" Exception in thread
>
[jira] [Commented] (SYNAPSE-1064) NullPointerException exception occurred while testing the JMS to HTTP scenarios with the high load
[
https://issues.apache.org/jira/browse/SYNAPSE-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15777800#comment-15777800
]
Isuru Udana Loku Narangoda commented on SYNAPSE-1064:
-
{code}
263 if (this.contentDecoder != null && (this.session.getEventMask() &
SelectionKey.OP_READ) > 0) {
264handler.inputReady(this, this.contentDecoder);
265if (this.contentDecoder.isCompleted()) {
266// Response entity received
267// Ready to receive a new response
268resetInput();
269}
270}
{code}
>From the above code snippet in DefaultNHttpClientConnection.java of HTTP Core
>NIO 4.3.3, only possibility is between line 263 and 265, another thread has
>made the contentDecoder to null. Looks like same connection is shared between
>multiple threads.
> NullPointerException exception occurred while testing the JMS to HTTP
> scenarios with the high load
> ---
>
> Key: SYNAPSE-1064
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1064
> Project: Synapse
> Issue Type: Bug
> Components: Transports
>Reporter: prabath ariyarathna
>Assignee: Hiranya Jayathilaka
>Priority: Blocker
>
> 1. Occured following NullPointerException while testing the sample
> 250(JMS-HTTP)
> 2016-12-26 13:09:47,439 [-] [HTTP-PT-Sender I/O Dispatcher-4] ERROR
> TargetHandler Unexpected exception encountered in TargetHandler
> java.lang.NullPointerException
> at
> org.apache.http.impl.nio.DefaultNHttpClientConnection.consumeInput(DefaultNHttpClientConnection.java:265)
> at
> org.apache.http.impl.nio.DefaultHttpClientIODispatch.onInputReady(DefaultHttpClientIODispatch.java:165)
> at
> org.apache.http.impl.nio.DefaultHttpClientIODispatch.onInputReady(DefaultHttpClientIODispatch.java:51)
> at
> org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:113)
> at
> org.apache.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:159)
> at
> org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:338)
> at
> org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:316)
> at
> org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:277)
> at
> org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:105)
> at
> org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:586)
> at java.lang.Thread.run(Thread.java:745)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Commented] (SYNAPSE-1064) NullPointerException exception occurred while testing the JMS to HTTP scenarios with the high load
[ https://issues.apache.org/jira/browse/SYNAPSE-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1592#comment-1592 ] Isuru Udana Loku Narangoda commented on SYNAPSE-1064: - [~prabathariyarathna] Can you give some info about the load test you have conducted ? > NullPointerException exception occurred while testing the JMS to HTTP > scenarios with the high load > --- > > Key: SYNAPSE-1064 > URL: https://issues.apache.org/jira/browse/SYNAPSE-1064 > Project: Synapse > Issue Type: Bug > Components: Transports >Reporter: prabath ariyarathna >Assignee: Hiranya Jayathilaka >Priority: Blocker > > 1. Occured following NullPointerException while testing the sample > 250(JMS-HTTP) > 2016-12-26 13:09:47,439 [-] [HTTP-PT-Sender I/O Dispatcher-4] ERROR > TargetHandler Unexpected exception encountered in TargetHandler > java.lang.NullPointerException > at > org.apache.http.impl.nio.DefaultNHttpClientConnection.consumeInput(DefaultNHttpClientConnection.java:265) > at > org.apache.http.impl.nio.DefaultHttpClientIODispatch.onInputReady(DefaultHttpClientIODispatch.java:165) > at > org.apache.http.impl.nio.DefaultHttpClientIODispatch.onInputReady(DefaultHttpClientIODispatch.java:51) > at > org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:113) > at > org.apache.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:159) > at > org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:338) > at > org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:316) > at > org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:277) > at > org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:105) > at > org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:586) > at java.lang.Thread.run(Thread.java:745) -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Commented] (SYNAPSE-1014) NPE in DefaultNHttpClientConnection consumeInput, when invoking a proxy concurrently
[
https://issues.apache.org/jira/browse/SYNAPSE-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15777532#comment-15777532
]
Isuru Udana Loku Narangoda commented on SYNAPSE-1014:
-
[~bsendruan] Can you post the synapse config you have used to produce this
error.
I tried with a message building scenario in out flow with a concurrency of 100,
still couldn't reproduce this.
> NPE in DefaultNHttpClientConnection consumeInput, when invoking a proxy
> concurrently
>
>
> Key: SYNAPSE-1014
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1014
> Project: Synapse
> Issue Type: Bug
> Components: Transports
>Affects Versions: 2.1
>Reporter: Senduran
>Assignee: Hiranya Jayathilaka
>Priority: Blocker
> Attachments: http_core_4_4.log
>
>
> When invoking a content aware passthrough proxy at a concurrency of 100. the
> following exception occurs
> {code}
> ERROR TargetHandler Unexpected exception encountered in TargetHandler
> java.lang.NullPointerException
> at
> org.apache.http.impl.nio.DefaultNHttpClientConnection.consumeInput(DefaultNHttpClientConnection.java:268)
> at
> org.apache.http.impl.nio.DefaultHttpClientIODispatch.onInputReady(DefaultHttpClientIODispatch.java:165)
> at
> org.apache.http.impl.nio.DefaultHttpClientIODispatch.onInputReady(DefaultHttpClientIODispatch.java:51)
> at
> org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:113)
> at
> org.apache.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:159)
> at
> org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:338)
> at
> org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:316)
> at
> org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:277)
> at
> org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:105)
> at
> org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:584)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Commented] (SYNAPSE-1061) WeightedRRLCAlgorithm Unwanted condition
[
https://issues.apache.org/jira/browse/SYNAPSE-1061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15688623#comment-15688623
]
Isuru Udana Loku Narangoda commented on SYNAPSE-1061:
-
Hi Vanji,
I checked the logic. It seems like recalculation of weight doesn't make sense
when connection count is 0. So I applied your patch to remove the unwanted
condition.
Committed revision 1770905.
Thanks.
> WeightedRRLCAlgorithm Unwanted condition
> -
>
> Key: SYNAPSE-1061
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1061
> Project: Synapse
> Issue Type: Bug
>Reporter: Vanjikumaran Sivajothy
>Assignee: Isuru Udana Loku Narangoda
> Fix For: 3.0
>
> Attachments: SYNAPSE-1061.diff
>
>
> was going through with WeightedRRLCAlgorithm and noticed that useless
> condition used in reCalcuateWeight(). Why do we need that condition over
> there and it is already known that totalConnections is not a zero.
> {code}
> public void reCalcuateWeight() {
> if (totalConnections > 0) {
> double weightRatio = (double) fixedWeight / totalWeight;
> double connectionRatio;
> if (totalConnections != 0) { //useless condition...??
> connectionRatio = (double) currentConnectionCount /
> totalConnections;
> } else {
> connectionRatio = 0;
> }
> double diff = weightRatio - connectionRatio;
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Resolved] (SYNAPSE-1061) WeightedRRLCAlgorithm Unwanted condition
[
https://issues.apache.org/jira/browse/SYNAPSE-1061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Isuru Udana Loku Narangoda resolved SYNAPSE-1061.
-
Resolution: Fixed
Fix Version/s: 3.0
> WeightedRRLCAlgorithm Unwanted condition
> -
>
> Key: SYNAPSE-1061
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1061
> Project: Synapse
> Issue Type: Bug
>Reporter: Vanjikumaran Sivajothy
>Assignee: Isuru Udana Loku Narangoda
> Fix For: 3.0
>
> Attachments: SYNAPSE-1061.diff
>
>
> was going through with WeightedRRLCAlgorithm and noticed that useless
> condition used in reCalcuateWeight(). Why do we need that condition over
> there and it is already known that totalConnections is not a zero.
> {code}
> public void reCalcuateWeight() {
> if (totalConnections > 0) {
> double weightRatio = (double) fixedWeight / totalWeight;
> double connectionRatio;
> if (totalConnections != 0) { //useless condition...??
> connectionRatio = (double) currentConnectionCount /
> totalConnections;
> } else {
> connectionRatio = 0;
> }
> double diff = weightRatio - connectionRatio;
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Assigned] (SYNAPSE-1061) WeightedRRLCAlgorithm Unwanted condition
[
https://issues.apache.org/jira/browse/SYNAPSE-1061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Isuru Udana Loku Narangoda reassigned SYNAPSE-1061:
---
Assignee: Isuru Udana Loku Narangoda (was: Hiranya Jayathilaka)
> WeightedRRLCAlgorithm Unwanted condition
> -
>
> Key: SYNAPSE-1061
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1061
> Project: Synapse
> Issue Type: Bug
>Reporter: Vanjikumaran Sivajothy
>Assignee: Isuru Udana Loku Narangoda
> Attachments: SYNAPSE-1061.diff
>
>
> was going through with WeightedRRLCAlgorithm and noticed that useless
> condition used in reCalcuateWeight(). Why do we need that condition over
> there and it is already known that totalConnections is not a zero.
> {code}
> public void reCalcuateWeight() {
> if (totalConnections > 0) {
> double weightRatio = (double) fixedWeight / totalWeight;
> double connectionRatio;
> if (totalConnections != 0) { //useless condition...??
> connectionRatio = (double) currentConnectionCount /
> totalConnections;
> } else {
> connectionRatio = 0;
> }
> double diff = weightRatio - connectionRatio;
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Commented] (SYNAPSE-1061) WeightedRRLCAlgorithm Unwanted condition
[
https://issues.apache.org/jira/browse/SYNAPSE-1061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15685377#comment-15685377
]
Isuru Udana Loku Narangoda commented on SYNAPSE-1061:
-
Hi Vanji,
Shall we try to understand the logic behind reCalcuateWeight().
I am just wondering whether we have mistakenly put
{code}
if (totalConnections > 0)
{code}
instead of
{code}
if (totalConnections >= 0)
{code}
because totalConnections == 0 is explicitly handled within the method, which
gives the idea that we need to recalculate the weight for that case as well.
> WeightedRRLCAlgorithm Unwanted condition
> -
>
> Key: SYNAPSE-1061
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1061
> Project: Synapse
> Issue Type: Bug
>Reporter: Vanjikumaran Sivajothy
>Assignee: Hiranya Jayathilaka
> Attachments: SYNAPSE-1061.diff
>
>
> was going through with WeightedRRLCAlgorithm and noticed that useless
> condition used in reCalcuateWeight(). Why do we need that condition over
> there and it is already known that totalConnections is not a zero.
> {code}
> public void reCalcuateWeight() {
> if (totalConnections > 0) {
> double weightRatio = (double) fixedWeight / totalWeight;
> double connectionRatio;
> if (totalConnections != 0) { //useless condition...??
> connectionRatio = (double) currentConnectionCount /
> totalConnections;
> } else {
> connectionRatio = 0;
> }
> double diff = weightRatio - connectionRatio;
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Assigned] (SYNAPSE-1053) Samples & Document for Loopback Mediator
[ https://issues.apache.org/jira/browse/SYNAPSE-1053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Udana Loku Narangoda reassigned SYNAPSE-1053: --- Assignee: Isuru Udana Loku Narangoda (was: Hiranya Jayathilaka) > Samples & Document for Loopback Mediator > > > Key: SYNAPSE-1053 > URL: https://issues.apache.org/jira/browse/SYNAPSE-1053 > Project: Synapse > Issue Type: Sub-task > Components: Core >Reporter: Vanjikumaran Sivajothy >Assignee: Isuru Udana Loku Narangoda > Attachments: SYNAPSE-1053.diff > > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Commented] (SYNAPSE-1053) Samples & Document for Loopback Mediator
[ https://issues.apache.org/jira/browse/SYNAPSE-1053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15664031#comment-15664031 ] Isuru Udana Loku Narangoda commented on SYNAPSE-1053: - Hi Vanji. Thanks. Documentation updated with r1769635. Can you please provide a sample too ? > Samples & Document for Loopback Mediator > > > Key: SYNAPSE-1053 > URL: https://issues.apache.org/jira/browse/SYNAPSE-1053 > Project: Synapse > Issue Type: Sub-task > Components: Core >Reporter: Vanjikumaran Sivajothy >Assignee: Hiranya Jayathilaka > Attachments: SYNAPSE-1053.diff > > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Commented] (SYNAPSE-1014) NPE in DefaultNHttpClientConnection consumeInput, when invoking a proxy concurrently
[
https://issues.apache.org/jira/browse/SYNAPSE-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15664007#comment-15664007
]
Isuru Udana Loku Narangoda commented on SYNAPSE-1014:
-
Thanks Oleg. We will check along the lines of concurrent modifications.
> NPE in DefaultNHttpClientConnection consumeInput, when invoking a proxy
> concurrently
>
>
> Key: SYNAPSE-1014
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1014
> Project: Synapse
> Issue Type: Bug
> Components: Transports
>Affects Versions: 2.1
>Reporter: Senduran
>Assignee: Hiranya Jayathilaka
>Priority: Blocker
> Attachments: http_core_4_4.log
>
>
> When invoking a content aware passthrough proxy at a concurrency of 100. the
> following exception occurs
> {code}
> ERROR TargetHandler Unexpected exception encountered in TargetHandler
> java.lang.NullPointerException
> at
> org.apache.http.impl.nio.DefaultNHttpClientConnection.consumeInput(DefaultNHttpClientConnection.java:268)
> at
> org.apache.http.impl.nio.DefaultHttpClientIODispatch.onInputReady(DefaultHttpClientIODispatch.java:165)
> at
> org.apache.http.impl.nio.DefaultHttpClientIODispatch.onInputReady(DefaultHttpClientIODispatch.java:51)
> at
> org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:113)
> at
> org.apache.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:159)
> at
> org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:338)
> at
> org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:316)
> at
> org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:277)
> at
> org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:105)
> at
> org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:584)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Commented] (SYNAPSE-1052) Mediator to Jump from IN sequence to OUT sequence
[ https://issues.apache.org/jira/browse/SYNAPSE-1052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15663976#comment-15663976 ] Isuru Udana Loku Narangoda commented on SYNAPSE-1052: - Committed revision 1769628. Thanks Vanji for the contribution. > Mediator to Jump from IN sequence to OUT sequence > -- > > Key: SYNAPSE-1052 > URL: https://issues.apache.org/jira/browse/SYNAPSE-1052 > Project: Synapse > Issue Type: New Feature > Components: Core >Reporter: Vanjikumaran Sivajothy >Assignee: Hiranya Jayathilaka > Fix For: 3.0 > > Attachments: SYNAPSE-1052.diff > > > The proposed mediator will enable synapse user to jump from IN sequence to > OUT sequence without reaching backend. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Resolved] (SYNAPSE-1058) VFS transport has the clear text password in the exceptions and Debug log
[ https://issues.apache.org/jira/browse/SYNAPSE-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Udana Loku Narangoda resolved SYNAPSE-1058. - Resolution: Fixed Assignee: Isuru Udana Loku Narangoda (was: Hiranya Jayathilaka) Fix Version/s: 3.0 > VFS transport has the clear text password in the exceptions and Debug log > - > > Key: SYNAPSE-1058 > URL: https://issues.apache.org/jira/browse/SYNAPSE-1058 > Project: Synapse > Issue Type: Bug > Components: Transports >Reporter: Vanjikumaran Sivajothy >Assignee: Isuru Udana Loku Narangoda > Labels: transport > Fix For: 3.0 > > Attachments: SYNAPSE-1058.patch > > > Most of the logs in vfs transport not secure enoght to hide the clear text > password on the log when exception throws from vfs or debug enabled. > This need to fixed like r1378457 [1] > [1]https://www.mail-archive.com/commits@synapse.apache.org/msg02701.html -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Commented] (SYNAPSE-1060) Property mediator configuration changes with requests if the type = OM
[
https://issues.apache.org/jira/browse/SYNAPSE-1060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15620998#comment-15620998
]
Isuru Udana Loku Narangoda commented on SYNAPSE-1060:
-
Above suggested fix is not sufficient, since runtime use the same reference
even though the configuration doesn't changes, it keeps accumulating the
payload segments. So need to clone while initializing the property value for
each and every request.
> Property mediator configuration changes with requests if the type = OM
> --
>
> Key: SYNAPSE-1060
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1060
> Project: Synapse
> Issue Type: Bug
>Reporter: Isuru Udana Loku Narangoda
>Assignee: Isuru Udana Loku Narangoda
>Priority: Critical
>
> {code}
>
> http://ws.apache.org/ns/synapse; name="main">
>
>
>
>
>
>
>
> http://org.apache.synapse/xsd; action="child"
> xpath="$ctx:AA"/>
>
>
>
>
>
> {code}
> Here initial configuration of the property mediator getting updated with each
> and every request.
> Log
> {code}
> 2016-10-31 07:29:51,770 [-] [PassThroughMessageProcessor-1] INFO LogMediator
> To: /, MessageID: urn:uuid:349a72af-a179-4a3c-a1b1-fd0570bb1d94, Direction:
> request, AA =
> 2016-10-31 07:30:01,562 [-] [PassThroughMessageProcessor-2] INFO LogMediator
> To: /, MessageID: urn:uuid:c40a4bbe-87b4-40c5-8d92-6589a68b5387, Direction:
> request, AA =
> 2016-10-31 07:30:09,859 [-] [PassThroughMessageProcessor-3] INFO LogMediator
> To: /, MessageID: urn:uuid:c3238c91-c139-4426-a37f-f9e4bdd4adac, Direction:
> request, AA =
> 2016-10-31 07:30:15,594 [-] [PassThroughMessageProcessor-4] INFO LogMediator
> To: /, MessageID: urn:uuid:390b0637-c52b-4dac-822d-ce478a7a92a1, Direction:
> request, AA =
> {code}
> Fix would be to clone the valueElement at the PropertyMediatorFactory
> Instead of
> {code}
> if (value != null) {
> propMediator.setValue(value.getAttributeValue(), dataType);
> } else if (valueElement != null) {
> propMediator.setValueElement(valueElement);
> {code}
> we need to use
> {code}
> if (value != null) {
> propMediator.setValue(value.getAttributeValue(), dataType);
> } else if (valueElement != null) {
> propMediator.setValueElement(valueElement.cloneOMElement());
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Updated] (SYNAPSE-1060) Property mediator configuration changes with requests if the type = OM
[
https://issues.apache.org/jira/browse/SYNAPSE-1060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Isuru Udana Loku Narangoda updated SYNAPSE-1060:
Description:
{code}
http://ws.apache.org/ns/synapse; name="main">
http://org.apache.synapse/xsd; action="child"
xpath="$ctx:AA"/>
{code}
Here initial configuration of the property mediator getting updated with each
and every request.
Log
{code}
2016-10-31 07:29:51,770 [-] [PassThroughMessageProcessor-1] INFO LogMediator
To: /, MessageID: urn:uuid:349a72af-a179-4a3c-a1b1-fd0570bb1d94, Direction:
request, AA =
2016-10-31 07:30:01,562 [-] [PassThroughMessageProcessor-2] INFO LogMediator
To: /, MessageID: urn:uuid:c40a4bbe-87b4-40c5-8d92-6589a68b5387, Direction:
request, AA =
2016-10-31 07:30:09,859 [-] [PassThroughMessageProcessor-3] INFO LogMediator
To: /, MessageID: urn:uuid:c3238c91-c139-4426-a37f-f9e4bdd4adac, Direction:
request, AA =
2016-10-31 07:30:15,594 [-] [PassThroughMessageProcessor-4] INFO LogMediator
To: /, MessageID: urn:uuid:390b0637-c52b-4dac-822d-ce478a7a92a1, Direction:
request, AA =
{code}
Fix would be to clone the valueElement at the PropertyMediatorFactory
Instead of
{code}
if (value != null) {
propMediator.setValue(value.getAttributeValue(), dataType);
} else if (valueElement != null) {
propMediator.setValueElement(valueElement);
{code}
we need to use
{code}
if (value != null) {
propMediator.setValue(value.getAttributeValue(), dataType);
} else if (valueElement != null) {
propMediator.setValueElement(valueElement.cloneOMElement());
{code}
was:
{code}
http://ws.apache.org/ns/synapse; name="main">
http://org.apache.synapse/xsd; action="child"
xpath="$ctx:AA"/>
{code}
Here initial configuration of the property mediator getting updated with each
and every request.
Fix would be to clone the valueElement at the PropertyMediatorFactory
Instead of
{code}
if (value != null) {
propMediator.setValue(value.getAttributeValue(), dataType);
} else if (valueElement != null) {
propMediator.setValueElement(valueElement);
{code}
we need to use
{code}
if (value != null) {
propMediator.setValue(value.getAttributeValue(), dataType);
} else if (valueElement != null) {
propMediator.setValueElement(valueElement.cloneOMElement());
{code}
> Property mediator configuration changes with requests if the type = OM
> --
>
> Key: SYNAPSE-1060
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1060
> Project: Synapse
> Issue Type: Bug
>Reporter: Isuru Udana Loku Narangoda
>Assignee: Isuru Udana Loku Narangoda
>Priority: Critical
>
> {code}
>
> http://ws.apache.org/ns/synapse; name="main">
>
>
>
>
>
>
>
> http://org.apache.synapse/xsd; action="child"
> xpath="$ctx:AA"/>
>
>
>
>
>
> {code}
> Here initial configuration of the property mediator getting updated with each
> and every request.
> Log
> {code}
> 2016-10-31 07:29:51,770 [-] [PassThroughMessageProcessor-1] INFO LogMediator
> To: /, MessageID: urn:uuid:349a72af-a179-4a3c-a1b1-fd0570bb1d94, Direction:
> request, AA =
> 2016-10-31 07:30:01,562 [-] [PassThroughMessageProcessor-2] INFO LogMediator
> To: /, MessageID: urn:uuid:c40a4bbe-87b4-40c5-8d92-6589a68b5387, Direction:
> request, AA =
> 2016-10-31 07:30:09,859 [-] [PassThroughMessageProcessor-3] INFO LogMediator
> To: /, MessageID: urn:uuid:c3238c91-c139-4426-a37f-f9e4bdd4adac, Direction:
> request, AA =
> 2016-10-31 07:30:15,594 [-] [PassThroughMessageProcessor-4] INFO LogMediator
> To: /, MessageID: urn:uuid:390b0637-c52b-4dac-822d-ce478a7a92a1, Direction:
> request, AA =
> {code}
> Fix would be to clone the valueElement at the PropertyMediatorFactory
> Instead of
> {code}
> if (value != null) {
> propMediator.setValue(value.getAttributeValue(), dataType);
> } else if (valueElement != null) {
> propMediator.setValueElement(valueElement);
> {code}
> we need to use
> {code}
> if (value != null) {
> propMediator.setValue(value.getAttributeValue(), dataType);
> } else if (valueElement != null) {
> propMediator.setValueElement(valueElement.cloneOMElement());
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Created] (SYNAPSE-1060) Property mediator configuration changes with requests if the type = OM
Isuru Udana Loku Narangoda created SYNAPSE-1060:
---
Summary: Property mediator configuration changes with requests if
the type = OM
Key: SYNAPSE-1060
URL: https://issues.apache.org/jira/browse/SYNAPSE-1060
Project: Synapse
Issue Type: Bug
Reporter: Isuru Udana Loku Narangoda
Assignee: Hiranya Jayathilaka
{code}
http://ws.apache.org/ns/synapse; name="main">
http://org.apache.synapse/xsd; action="child"
xpath="$ctx:AA"/>
{code}
Here initial configuration of the property mediator getting updated with each
and every request.
Fix would be to clone the valueElement at the PropertyMediatorFactory
Instead of
{code}
if (value != null) {
propMediator.setValue(value.getAttributeValue(), dataType);
} else if (valueElement != null) {
propMediator.setValueElement(valueElement);
{code}
we need to use
{code}
if (value != null) {
propMediator.setValue(value.getAttributeValue(), dataType);
} else if (valueElement != null) {
propMediator.setValueElement(valueElement.cloneOMElement());
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Commented] (SYNAPSE-851) VFS proxy generates the response.xml with empty content (Synapse-2.2.0-Snapshot trunk)
[ https://issues.apache.org/jira/browse/SYNAPSE-851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15537850#comment-15537850 ] Isuru Udana Loku Narangoda commented on SYNAPSE-851: Committed revision 1762976 > VFS proxy generates the response.xml with empty content > (Synapse-2.2.0-Snapshot trunk) > -- > > Key: SYNAPSE-851 > URL: https://issues.apache.org/jira/browse/SYNAPSE-851 > Project: Synapse > Issue Type: Bug > Components: Transports >Affects Versions: NIGHTLY >Reporter: Vijayaratha Vijayasingam >Assignee: Isuru Udana Loku Narangoda >Priority: Blocker > Fix For: 3.0 > > > Used following configuration; > I see the output(response.xml) at "out" folder is empty.. > trace="disable"> > > > > > > > > > > > 15 > MOVE > >name="transport.vfs.FileURI">file:C:\Users\TOSHIBA\Desktop\in > name="transport.vfs.MoveAfterProcess">file:C:\Users\TOSHIBA\Desktop\original > name="transport.vfs.MoveAfterFailure">file:C:\Users\TOSHIBA\Desktop\error > .* > text/plain > MOVE > proxy > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Resolved] (SYNAPSE-851) VFS proxy generates the response.xml with empty content (Synapse-2.2.0-Snapshot trunk)
[ https://issues.apache.org/jira/browse/SYNAPSE-851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Udana Loku Narangoda resolved SYNAPSE-851. Resolution: Fixed Fix Version/s: (was: FUTURE) 3.0 > VFS proxy generates the response.xml with empty content > (Synapse-2.2.0-Snapshot trunk) > -- > > Key: SYNAPSE-851 > URL: https://issues.apache.org/jira/browse/SYNAPSE-851 > Project: Synapse > Issue Type: Bug > Components: Transports >Affects Versions: NIGHTLY >Reporter: Vijayaratha Vijayasingam >Assignee: Isuru Udana Loku Narangoda >Priority: Blocker > Fix For: 3.0 > > > Used following configuration; > I see the output(response.xml) at "out" folder is empty.. > trace="disable"> > > > > > > > > > > > 15 > MOVE > >name="transport.vfs.FileURI">file:C:\Users\TOSHIBA\Desktop\in > name="transport.vfs.MoveAfterProcess">file:C:\Users\TOSHIBA\Desktop\original > name="transport.vfs.MoveAfterFailure">file:C:\Users\TOSHIBA\Desktop\error > .* > text/plain > MOVE > proxy > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Commented] (SYNAPSE-851) VFS proxy generates the response.xml with empty content (Synapse-2.2.0-Snapshot trunk)
[ https://issues.apache.org/jira/browse/SYNAPSE-851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15537798#comment-15537798 ] Isuru Udana Loku Narangoda commented on SYNAPSE-851: The problem is a new Thread is spawning at the axis2 level. Only option I see to fix this is stop spawning of a new thread for vfs listener scenarios. We need to remove ClientApiNonBlocking property before sending out the message. By adding the following at the inSequence I could get the scenario working. IMO, it is ok to remove that at the VFSListener level programatically. > VFS proxy generates the response.xml with empty content > (Synapse-2.2.0-Snapshot trunk) > -- > > Key: SYNAPSE-851 > URL: https://issues.apache.org/jira/browse/SYNAPSE-851 > Project: Synapse > Issue Type: Bug > Components: Transports >Affects Versions: NIGHTLY >Reporter: Vijayaratha Vijayasingam >Assignee: Isuru Udana Loku Narangoda >Priority: Blocker > Fix For: FUTURE > > > Used following configuration; > I see the output(response.xml) at "out" folder is empty.. > trace="disable"> > > > > > > > > > > > 15 > MOVE > >name="transport.vfs.FileURI">file:C:\Users\TOSHIBA\Desktop\in > name="transport.vfs.MoveAfterProcess">file:C:\Users\TOSHIBA\Desktop\original > name="transport.vfs.MoveAfterFailure">file:C:\Users\TOSHIBA\Desktop\error > .* > text/plain > MOVE > proxy > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Assigned] (SYNAPSE-851) VFS proxy generates the response.xml with empty content (Synapse-2.2.0-Snapshot trunk)
[ https://issues.apache.org/jira/browse/SYNAPSE-851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Udana Loku Narangoda reassigned SYNAPSE-851: -- Assignee: Isuru Udana Loku Narangoda (was: Rajika Kumarasiri) > VFS proxy generates the response.xml with empty content > (Synapse-2.2.0-Snapshot trunk) > -- > > Key: SYNAPSE-851 > URL: https://issues.apache.org/jira/browse/SYNAPSE-851 > Project: Synapse > Issue Type: Bug > Components: Transports >Affects Versions: NIGHTLY >Reporter: Vijayaratha Vijayasingam >Assignee: Isuru Udana Loku Narangoda >Priority: Blocker > Fix For: FUTURE > > > Used following configuration; > I see the output(response.xml) at "out" folder is empty.. > trace="disable"> > > > > > > > > > > > 15 > MOVE > >name="transport.vfs.FileURI">file:C:\Users\TOSHIBA\Desktop\in > name="transport.vfs.MoveAfterProcess">file:C:\Users\TOSHIBA\Desktop\original > name="transport.vfs.MoveAfterFailure">file:C:\Users\TOSHIBA\Desktop\error > .* > text/plain > MOVE > proxy > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Assigned] (SYNAPSE-901) Concurrency issue at Clone Mediator
[ https://issues.apache.org/jira/browse/SYNAPSE-901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Udana Loku Narangoda reassigned SYNAPSE-901: -- Assignee: Isuru Udana Loku Narangoda (was: Hiranya Jayathilaka) > Concurrency issue at Clone Mediator > --- > > Key: SYNAPSE-901 > URL: https://issues.apache.org/jira/browse/SYNAPSE-901 > Project: Synapse > Issue Type: Bug > Components: Core >Affects Versions: 2.1 > Environment: Any >Reporter: Malith Dhanushka >Assignee: Isuru Udana Loku Narangoda >Priority: Blocker > Fix For: FUTURE > > Attachments: SYNAPSE-901.patch > > > This issue is very much identical to the issue SYNAPSE-897. Clone mediator > gives following exception when messages are processed in parallel, > [SynapseWorker-2] ERROR MediatorWorker Unexpected error executing task/async > inject > java.util.EmptyStackException > at java.util.Stack.peek(Stack.java:85) > at > org.apache.synapse.util.xpath.SynapseXPathVariableContext.getVariableValue(SynapseXPathVariableContext.java:157) > at org.jaxen.ContextSupport.getVariableValue(ContextSupport.java:215) > at org.jaxen.Context.getVariableValue(Context.java:196) > at > org.jaxen.expr.DefaultVariableReferenceExpr.evaluate(DefaultVariableReferenceExpr.java:103) > at org.jaxen.expr.DefaultXPathExpr.asList(DefaultXPathExpr.java:102) > at org.jaxen.BaseXPath.selectNodesForContext(BaseXPath.java:677) > at org.jaxen.BaseXPath.selectNodes(BaseXPath.java:216) > at org.jaxen.BaseXPath.evaluate(BaseXPath.java:175) > at > org.apache.synapse.util.xpath.SynapseXPath.stringValueOf(SynapseXPath.java:172) > at > org.apache.synapse.mediators.transform.HeaderMediator.mediate(HeaderMediator.java:79) > at > org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:60) > at > org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:114) > at > org.apache.synapse.mediators.MediatorWorker.run(MediatorWorker.java:69) > 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:662) > Exception in thread "SynapseWorker-2" java.lang.NullPointerException > at org.apache.synapse.FaultHandler.handleFault(FaultHandler.java:78) > at > org.apache.synapse.mediators.MediatorWorker.run(MediatorWorker.java:90) > 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:662) -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Resolved] (SYNAPSE-974) Mail transport sample 256 configurations are not valid.
[ https://issues.apache.org/jira/browse/SYNAPSE-974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Udana Loku Narangoda resolved SYNAPSE-974. Resolution: Fixed Assignee: Isuru Udana Loku Narangoda (was: Hiranya Jayathilaka) Fix Version/s: 3.0 > Mail transport sample 256 configurations are not valid. > --- > > Key: SYNAPSE-974 > URL: https://issues.apache.org/jira/browse/SYNAPSE-974 > Project: Synapse > Issue Type: Bug > Components: Documentation >Affects Versions: 2.1 > Environment: Ubuntu linux AMD64bit > Java 1.6 >Reporter: Chanaka Fernando >Assignee: Isuru Udana Loku Narangoda >Priority: Blocker > Labels: documentation > Fix For: 3.0 > > Attachments: FixForIssue974.patch > > > Password of the sample email addresses are changed by someone. The below > configuration not working any more. > Enabling Mail transport in axis2.xml > -- > class="org.apache.synapse.transport.mail.MailTransportSender"> name="mail.smtp.host">smtp.gmail.com name="mail.smtp.port">587 name="mail.smtp.starttls.enable">true name="mail.smtp.auth">true name="mail.smtp.user">synapse.demo.0 name="mail.smtp.password">mailpassword name="mail.smtp.from">synapse.dem...@gmail.com > Inside the Sample 256 synapse configuration > --- > synapse.dem...@gmail.com > pop3 name="transport.PollInterval">5 name="mail.pop3.host">pop.gmail.com name="mail.pop3.port">995 name="mail.pop3.user">synapse.demo.1 name="mail.pop3.password">mailpassword name="mail.pop3.socketFactory.class">javax.net.ssl.SSLSocketFactory > false > 995 name="transport.mail.ContentType">application/xml -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Commented] (SYNAPSE-974) Mail transport sample 256 configurations are not valid.
[ https://issues.apache.org/jira/browse/SYNAPSE-974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15480157#comment-15480157 ] Isuru Udana Loku Narangoda commented on SYNAPSE-974: Modified patch committed revision 1760198. Changed gmail account settings to allow less secure apps. > Mail transport sample 256 configurations are not valid. > --- > > Key: SYNAPSE-974 > URL: https://issues.apache.org/jira/browse/SYNAPSE-974 > Project: Synapse > Issue Type: Bug > Components: Documentation >Affects Versions: 2.1 > Environment: Ubuntu linux AMD64bit > Java 1.6 >Reporter: Chanaka Fernando >Assignee: Hiranya Jayathilaka >Priority: Blocker > Labels: documentation > Fix For: 3.0 > > Attachments: FixForIssue974.patch > > > Password of the sample email addresses are changed by someone. The below > configuration not working any more. > Enabling Mail transport in axis2.xml > -- > class="org.apache.synapse.transport.mail.MailTransportSender"> name="mail.smtp.host">smtp.gmail.com name="mail.smtp.port">587 name="mail.smtp.starttls.enable">true name="mail.smtp.auth">true name="mail.smtp.user">synapse.demo.0 name="mail.smtp.password">mailpassword name="mail.smtp.from">synapse.dem...@gmail.com > Inside the Sample 256 synapse configuration > --- > synapse.dem...@gmail.com > pop3 name="transport.PollInterval">5 name="mail.pop3.host">pop.gmail.com name="mail.pop3.port">995 name="mail.pop3.user">synapse.demo.1 name="mail.pop3.password">mailpassword name="mail.pop3.socketFactory.class">javax.net.ssl.SSLSocketFactory > false > 995 name="transport.mail.ContentType">application/xml -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Resolved] (SYNAPSE-854) Mail proxy sample broken
[ https://issues.apache.org/jira/browse/SYNAPSE-854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Udana Loku Narangoda resolved SYNAPSE-854. Resolution: Duplicate Duplicated to SYNAPSE-974 > Mail proxy sample broken > - > > Key: SYNAPSE-854 > URL: https://issues.apache.org/jira/browse/SYNAPSE-854 > Project: Synapse > Issue Type: Bug > Components: Transports >Affects Versions: NIGHTLY >Reporter: Sagara Gunathunga >Assignee: Isuru Udana Loku Narangoda >Priority: Blocker > Attachments: FixForIssue854.patch > > > Getting following exception when running sample256 with latest snapshot > version of Synapse.. Please note that I have tested same mail transport > component used in here with Axis2 without any issue also this sample worked > fine with a WSO2 ESB 4.0.2 that also based on Synapse. > 012-03-14 11:56:02,401 [-] [mailto-Worker-4] ERROR AxisEngine The > endpoint reference (EPR) for the Operation not found is and the WSA > Action = null. If this EPR was previously reachable, please contact > the server administrator. > org.apache.axis2.AxisFault: The endpoint reference (EPR) for the > Operation not found is and the WSA Action = null. If this EPR was > previously reachable, please contact the server administrator. >at > org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:117) >at org.apache.axis2.engine.Phase.invoke(Phase.java:324) >at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:262) >at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:168) >at > org.apache.axis2.transport.base.AbstractTransportListener.handleIncomingMessage(AbstractTransportListener.java:328) >at > org.apache.axis2.transport.mail.MailTransportListener.processMail(MailTransportListener.java:524) >at > org.apache.axis2.transport.mail.MailTransportListener.access$000(MailTransportListener.java:61) >at > org.apache.axis2.transport.mail.MailTransportListener$MailProcessor.run(MailTransportListener.java:331) >at > org.apache.axis2.transport.mail.MailTransportListener.processMail(MailTransportListener.java:295) >at > org.apache.axis2.transport.mail.MailTransportListener.checkMail(MailTransportListener.java:199) >at > org.apache.axis2.transport.mail.MailTransportListener.poll(MailTransportListener.java:80) >at > org.apache.axis2.transport.mail.MailTransportListener.poll(MailTransportListener.java:61) >at > org.apache.axis2.transport.base.AbstractPollingTransportListener$1$1.run(AbstractPollingTransportListener.java:67) >at > org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:173) >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:662) > 2012-03-14 11:56:02,403 [-] [mailto-Worker-4] ERROR > MailTransportSender To address for outgoing message cannot be > determined > 2012-03-14 11:56:02,404 [-] [mailto-Worker-4] ERROR > MailTransportSender Error generating mail message > org.apache.axis2.AxisFault: To address for outgoing message cannot be > determined >at > org.apache.axis2.transport.base.AbstractTransportSender.handleException(AbstractTransportSender.java:231) >at > org.apache.axis2.transport.mail.MailTransportSender.sendMail(MailTransportSender.java:314) >at > org.apache.axis2.transport.mail.MailTransportSender.sendMessage(MailTransportSender.java:175) >at > org.apache.axis2.transport.base.AbstractTransportSender.invoke(AbstractTransportSender.java:119) >at org.apache.axis2.engine.AxisEngine.sendFault(AxisEngine.java:526) >at > org.apache.axis2.transport.base.AbstractTransportListener.handleIncomingMessage(AbstractTransportListener.java:336) >at > org.apache.axis2.transport.mail.MailTransportListener.processMail(MailTransportListener.java:524) >at > org.apache.axis2.transport.mail.MailTransportListener.access$000(MailTransportListener.java:61) >at > org.apache.axis2.transport.mail.MailTransportListener$MailProcessor.run(MailTransportListener.java:331) >at > org.apache.axis2.transport.mail.MailTransportListener.processMail(MailTransportListener.java:295) >at > org.apache.axis2.transport.mail.MailTransportListener.checkMail(MailTransportListener.java:199) >at > org.apache.axis2.transport.mail.MailTransportListener.poll(MailTransportListener.java:80) >at > org.apache.axis2.transport.mail.MailTransportListener.poll(MailTransportListener.java:61) >at >
[jira] [Commented] (SYNAPSE-854) Mail proxy sample broken
[ https://issues.apache.org/jira/browse/SYNAPSE-854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15480114#comment-15480114 ] Isuru Udana Loku Narangoda commented on SYNAPSE-854: Issue was with the firewall in my machine. I am marking this as duplicated to SYNAPSE-974. > Mail proxy sample broken > - > > Key: SYNAPSE-854 > URL: https://issues.apache.org/jira/browse/SYNAPSE-854 > Project: Synapse > Issue Type: Bug > Components: Transports >Affects Versions: NIGHTLY >Reporter: Sagara Gunathunga >Assignee: Isuru Udana Loku Narangoda >Priority: Blocker > Attachments: FixForIssue854.patch > > > Getting following exception when running sample256 with latest snapshot > version of Synapse.. Please note that I have tested same mail transport > component used in here with Axis2 without any issue also this sample worked > fine with a WSO2 ESB 4.0.2 that also based on Synapse. > 012-03-14 11:56:02,401 [-] [mailto-Worker-4] ERROR AxisEngine The > endpoint reference (EPR) for the Operation not found is and the WSA > Action = null. If this EPR was previously reachable, please contact > the server administrator. > org.apache.axis2.AxisFault: The endpoint reference (EPR) for the > Operation not found is and the WSA Action = null. If this EPR was > previously reachable, please contact the server administrator. >at > org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:117) >at org.apache.axis2.engine.Phase.invoke(Phase.java:324) >at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:262) >at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:168) >at > org.apache.axis2.transport.base.AbstractTransportListener.handleIncomingMessage(AbstractTransportListener.java:328) >at > org.apache.axis2.transport.mail.MailTransportListener.processMail(MailTransportListener.java:524) >at > org.apache.axis2.transport.mail.MailTransportListener.access$000(MailTransportListener.java:61) >at > org.apache.axis2.transport.mail.MailTransportListener$MailProcessor.run(MailTransportListener.java:331) >at > org.apache.axis2.transport.mail.MailTransportListener.processMail(MailTransportListener.java:295) >at > org.apache.axis2.transport.mail.MailTransportListener.checkMail(MailTransportListener.java:199) >at > org.apache.axis2.transport.mail.MailTransportListener.poll(MailTransportListener.java:80) >at > org.apache.axis2.transport.mail.MailTransportListener.poll(MailTransportListener.java:61) >at > org.apache.axis2.transport.base.AbstractPollingTransportListener$1$1.run(AbstractPollingTransportListener.java:67) >at > org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:173) >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:662) > 2012-03-14 11:56:02,403 [-] [mailto-Worker-4] ERROR > MailTransportSender To address for outgoing message cannot be > determined > 2012-03-14 11:56:02,404 [-] [mailto-Worker-4] ERROR > MailTransportSender Error generating mail message > org.apache.axis2.AxisFault: To address for outgoing message cannot be > determined >at > org.apache.axis2.transport.base.AbstractTransportSender.handleException(AbstractTransportSender.java:231) >at > org.apache.axis2.transport.mail.MailTransportSender.sendMail(MailTransportSender.java:314) >at > org.apache.axis2.transport.mail.MailTransportSender.sendMessage(MailTransportSender.java:175) >at > org.apache.axis2.transport.base.AbstractTransportSender.invoke(AbstractTransportSender.java:119) >at org.apache.axis2.engine.AxisEngine.sendFault(AxisEngine.java:526) >at > org.apache.axis2.transport.base.AbstractTransportListener.handleIncomingMessage(AbstractTransportListener.java:336) >at > org.apache.axis2.transport.mail.MailTransportListener.processMail(MailTransportListener.java:524) >at > org.apache.axis2.transport.mail.MailTransportListener.access$000(MailTransportListener.java:61) >at > org.apache.axis2.transport.mail.MailTransportListener$MailProcessor.run(MailTransportListener.java:331) >at > org.apache.axis2.transport.mail.MailTransportListener.processMail(MailTransportListener.java:295) >at > org.apache.axis2.transport.mail.MailTransportListener.checkMail(MailTransportListener.java:199) >at > org.apache.axis2.transport.mail.MailTransportListener.poll(MailTransportListener.java:80) >at >
[jira] [Resolved] (SYNAPSE-1015) Message building fails at high concurrency when the outsequence is content aware
[
https://issues.apache.org/jira/browse/SYNAPSE-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Isuru Udana Loku Narangoda resolved SYNAPSE-1015.
-
Resolution: Fixed
Assignee: Ravi Undupitiya (was: Hiranya Jayathilaka)
Fix Version/s: 3.0
> Message building fails at high concurrency when the outsequence is content
> aware
> -
>
> Key: SYNAPSE-1015
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1015
> Project: Synapse
> Issue Type: Bug
> Components: Core, Transports
>Affects Versions: 2.1
>Reporter: Senduran
>Assignee: Ravi Undupitiya
>Priority: Blocker
> Fix For: 3.0
>
> Attachments: controlled-bytebuffer-fix.diff
>
>
> When invoke the following proxy at a concurrency (around 200)
> {code:xml}
> http://ws.apache.org/ns/synapse;
>name="HelloProxy"
>transports="https,http"
>statistics="disable"
>trace="disable"
>startOnLoad="true">
>
>
>
>
>http://localhost:9765/services/HelloService/"/>
>
>
>
>
>
>
>a
>
>
>
>
>
>
>http://localhost:9765/services/HelloService?wsdl"/>
>
>
> {code}
> Following exception occurs after a while,
> {code}
> 2016-05-23 23:51:09,455 [-] [PassThroughMessageProcessor-30] ERROR RelayUtils
> Error while building PassThrough stream
> org.apache.axiom.om.DeferredParsingException:
> com.ctc.wstx.exc.WstxUnexpectedCharException: Illegal character (NULL,
> unicode 0) encountered: not valid in any content
> at [row,col {unknown-source}]: [1,1]
> at
> org.apache.axiom.om.impl.builder.StAXOMBuilder.parserNext(StAXOMBuilder.java:681)
> at
> org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:184)
> at
> org.apache.axiom.core.CoreParentNodeSupport.ajc$interMethod$org_apache_axiom_core_CoreParentNodeSupport$org_apache_axiom_core_CoreParentNode$buildNext(CoreParentNodeSupport.aj:96)
> at
> org.apache.axiom.om.impl.llom.OMDocumentImpl.buildNext(OMDocumentImpl.java:1)
> at
> org.apache.axiom.core.CoreParentNodeSupport.ajc$interMethodDispatch1$org_apache_axiom_core_CoreParentNodeSupport$org_apache_axiom_core_CoreParentNode$buildNext(CoreParentNodeSupport.aj)
> at
> org.apache.axiom.core.CoreParentNodeSupport.ajc$interMethod$org_apache_axiom_core_CoreParentNodeSupport$org_apache_axiom_core_CoreParentNode$coreGetFirstChild(CoreParentNodeSupport.aj:113)
> at
> org.apache.axiom.om.impl.llom.OMDocumentImpl.coreGetFirstChild(OMDocumentImpl.java:1)
> at
> org.apache.axiom.core.CoreParentNodeSupport.ajc$interMethodDispatch1$org_apache_axiom_core_CoreParentNodeSupport$org_apache_axiom_core_CoreParentNode$coreGetFirstChild(CoreParentNodeSupport.aj)
> at
> org.apache.axiom.core.CoreDocumentSupport.ajc$interMethod$org_apache_axiom_core_CoreDocumentSupport$org_apache_axiom_core_CoreDocument$coreGetDocumentElement(CoreDocumentSupport.aj:42)
> at
> org.apache.axiom.om.impl.llom.OMDocumentImpl.coreGetDocumentElement(OMDocumentImpl.java:1)
> at
> org.apache.axiom.om.impl.common.AxiomDocumentSupport.ajc$interMethod$org_apache_axiom_om_impl_common_AxiomDocumentSupport$org_apache_axiom_om_impl_intf_AxiomDocument$getOMDocumentElement(AxiomDocumentSupport.aj:32)
> at
> org.apache.axiom.om.impl.llom.OMDocumentImpl.getOMDocumentElement(OMDocumentImpl.java:1)
> at
> org.apache.axiom.om.impl.builder.StAXOMBuilder.getDocumentElement(StAXOMBuilder.java:557)
> at
> org.apache.axiom.om.impl.builder.StAXOMBuilder.getDocumentElement(StAXOMBuilder.java:553)
> at
> org.apache.axis2.builder.SOAPBuilder.processDocument(SOAPBuilder.java:53)
> at
> org.apache.synapse.transport.passthru.util.DeferredMessageBuilder.getDocument(DeferredMessageBuilder.java:114)
> at
> org.apache.synapse.transport.passthru.util.RelayUtils.buildMessage(RelayUtils.java:146)
> at
> org.apache.synapse.transport.passthru.util.RelayUtils.buildMessage(RelayUtils.java:86)
> at
> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:62)
> at
> org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:114)
> at
> org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:230)
> at
> org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:444)
> at
> org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:221)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:169)
>
[jira] [Updated] (SYNAPSE-854) Mail proxy sample broken
[ https://issues.apache.org/jira/browse/SYNAPSE-854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Udana Loku Narangoda updated SYNAPSE-854: --- Summary: Mail proxy sample broken (was: Mail proxcy sample broken ) > Mail proxy sample broken > - > > Key: SYNAPSE-854 > URL: https://issues.apache.org/jira/browse/SYNAPSE-854 > Project: Synapse > Issue Type: Bug > Components: Transports >Affects Versions: NIGHTLY >Reporter: Sagara Gunathunga >Assignee: Isuru Udana Loku Narangoda >Priority: Blocker > Attachments: FixForIssue854.patch > > > Getting following exception when running sample256 with latest snapshot > version of Synapse.. Please note that I have tested same mail transport > component used in here with Axis2 without any issue also this sample worked > fine with a WSO2 ESB 4.0.2 that also based on Synapse. > 012-03-14 11:56:02,401 [-] [mailto-Worker-4] ERROR AxisEngine The > endpoint reference (EPR) for the Operation not found is and the WSA > Action = null. If this EPR was previously reachable, please contact > the server administrator. > org.apache.axis2.AxisFault: The endpoint reference (EPR) for the > Operation not found is and the WSA Action = null. If this EPR was > previously reachable, please contact the server administrator. >at > org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:117) >at org.apache.axis2.engine.Phase.invoke(Phase.java:324) >at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:262) >at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:168) >at > org.apache.axis2.transport.base.AbstractTransportListener.handleIncomingMessage(AbstractTransportListener.java:328) >at > org.apache.axis2.transport.mail.MailTransportListener.processMail(MailTransportListener.java:524) >at > org.apache.axis2.transport.mail.MailTransportListener.access$000(MailTransportListener.java:61) >at > org.apache.axis2.transport.mail.MailTransportListener$MailProcessor.run(MailTransportListener.java:331) >at > org.apache.axis2.transport.mail.MailTransportListener.processMail(MailTransportListener.java:295) >at > org.apache.axis2.transport.mail.MailTransportListener.checkMail(MailTransportListener.java:199) >at > org.apache.axis2.transport.mail.MailTransportListener.poll(MailTransportListener.java:80) >at > org.apache.axis2.transport.mail.MailTransportListener.poll(MailTransportListener.java:61) >at > org.apache.axis2.transport.base.AbstractPollingTransportListener$1$1.run(AbstractPollingTransportListener.java:67) >at > org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:173) >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:662) > 2012-03-14 11:56:02,403 [-] [mailto-Worker-4] ERROR > MailTransportSender To address for outgoing message cannot be > determined > 2012-03-14 11:56:02,404 [-] [mailto-Worker-4] ERROR > MailTransportSender Error generating mail message > org.apache.axis2.AxisFault: To address for outgoing message cannot be > determined >at > org.apache.axis2.transport.base.AbstractTransportSender.handleException(AbstractTransportSender.java:231) >at > org.apache.axis2.transport.mail.MailTransportSender.sendMail(MailTransportSender.java:314) >at > org.apache.axis2.transport.mail.MailTransportSender.sendMessage(MailTransportSender.java:175) >at > org.apache.axis2.transport.base.AbstractTransportSender.invoke(AbstractTransportSender.java:119) >at org.apache.axis2.engine.AxisEngine.sendFault(AxisEngine.java:526) >at > org.apache.axis2.transport.base.AbstractTransportListener.handleIncomingMessage(AbstractTransportListener.java:336) >at > org.apache.axis2.transport.mail.MailTransportListener.processMail(MailTransportListener.java:524) >at > org.apache.axis2.transport.mail.MailTransportListener.access$000(MailTransportListener.java:61) >at > org.apache.axis2.transport.mail.MailTransportListener$MailProcessor.run(MailTransportListener.java:331) >at > org.apache.axis2.transport.mail.MailTransportListener.processMail(MailTransportListener.java:295) >at > org.apache.axis2.transport.mail.MailTransportListener.checkMail(MailTransportListener.java:199) >at > org.apache.axis2.transport.mail.MailTransportListener.poll(MailTransportListener.java:80) >at > org.apache.axis2.transport.mail.MailTransportListener.poll(MailTransportListener.java:61) >at >
[jira] [Resolved] (SYNAPSE-1040) cloneMessageContext in MessageHelper does not deep clone all synapse properties
[ https://issues.apache.org/jira/browse/SYNAPSE-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Udana Loku Narangoda resolved SYNAPSE-1040. - Resolution: Fixed > cloneMessageContext in MessageHelper does not deep clone all synapse > properties > > > Key: SYNAPSE-1040 > URL: https://issues.apache.org/jira/browse/SYNAPSE-1040 > Project: Synapse > Issue Type: Bug > Components: Core >Affects Versions: 1.1 >Reporter: isuru janith ranawaka >Assignee: Isuru Udana Loku Narangoda >Priority: Blocker > Fix For: 3.0 > > Attachments: SYNAPSE-1040.diff > > > Clone mediator does not clone all the synapse properties inside Synapse > MessageContext. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Commented] (SYNAPSE-1040) cloneMessageContext in MessageHelper does not deep clone all synapse properties
[ https://issues.apache.org/jira/browse/SYNAPSE-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15322862#comment-15322862 ] Isuru Udana Loku Narangoda commented on SYNAPSE-1040: - Hi Isuru Ranawaka, Modified fix applied in r1747563. Thank you for the contribution. > cloneMessageContext in MessageHelper does not deep clone all synapse > properties > > > Key: SYNAPSE-1040 > URL: https://issues.apache.org/jira/browse/SYNAPSE-1040 > Project: Synapse > Issue Type: Bug > Components: Core >Affects Versions: 1.1 >Reporter: isuru janith ranawaka >Assignee: Isuru Udana Loku Narangoda >Priority: Blocker > Fix For: 3.0 > > Attachments: SYNAPSE-1040.diff > > > Clone mediator does not clone all the synapse properties inside Synapse > MessageContext. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Commented] (SYNAPSE-1030) Test case for DISABLE_CHUNKING for API
[ https://issues.apache.org/jira/browse/SYNAPSE-1030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15322095#comment-15322095 ] Isuru Udana Loku Narangoda commented on SYNAPSE-1030: - Hi Vanji, For my information can you please explain the difference in the behaviour ? > Test case for DISABLE_CHUNKING for API > -- > > Key: SYNAPSE-1030 > URL: https://issues.apache.org/jira/browse/SYNAPSE-1030 > Project: Synapse > Issue Type: Sub-task > Components: Core, Transports >Reporter: Vanjikumaran Sivajothy >Assignee: Hiranya Jayathilaka > Attachments: SYNAPSE-1030.diff > > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Commented] (SYNAPSE-1040) cloneMessageContext in MessageHelper does not deep clone all synapse properties
[ https://issues.apache.org/jira/browse/SYNAPSE-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15322090#comment-15322090 ] Isuru Udana Loku Narangoda commented on SYNAPSE-1040: - sure, I'll review and merge. > cloneMessageContext in MessageHelper does not deep clone all synapse > properties > > > Key: SYNAPSE-1040 > URL: https://issues.apache.org/jira/browse/SYNAPSE-1040 > Project: Synapse > Issue Type: Bug > Components: Core >Affects Versions: 1.1 >Reporter: isuru janith ranawaka >Assignee: Isuru Udana Loku Narangoda >Priority: Blocker > Fix For: 3.0 > > Attachments: SYNAPSE-1040.diff > > > Clone mediator does not clone all the synapse properties inside Synapse > MessageContext. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Commented] (SYNAPSE-1044) Test Case for Text on SOAP Fault detail.
[ https://issues.apache.org/jira/browse/SYNAPSE-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15321820#comment-15321820 ] Isuru Udana Loku Narangoda commented on SYNAPSE-1044: - I am not sure why we need to think about the end user aspect here. IMO, end user doesn't care as long as functionality works properly. We need to decide on how the functionality can be be tested. We should try to cover whatever possible from unit tests and then go for a integration test if something cannot be covered from a unit test. Should we document the way we should add tests to synapse under development best practices ? > Test Case for Text on SOAP Fault detail. > > > Key: SYNAPSE-1044 > URL: https://issues.apache.org/jira/browse/SYNAPSE-1044 > Project: Synapse > Issue Type: Sub-task >Reporter: Vanjikumaran Sivajothy >Assignee: Hiranya Jayathilaka > Attachments: SYNAPSE-1044.txt > > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Commented] (SYNAPSE-1040) cloneMessageContext in MessageHelper does not deep clone all synapse properties
[ https://issues.apache.org/jira/browse/SYNAPSE-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15321813#comment-15321813 ] Isuru Udana Loku Narangoda commented on SYNAPSE-1040: - Hi Hiranya, I will explain this. We are not deep cloning most of these types. With parallel executions (clone, iterate) for non primitives we are sharing the same reference. For an example the Function stack used in Templates. This leads to major concurrency issues. Ideally we should deep clone all the properties available in the message context which is not practical, at least we should do it for all known types. > cloneMessageContext in MessageHelper does not deep clone all synapse > properties > > > Key: SYNAPSE-1040 > URL: https://issues.apache.org/jira/browse/SYNAPSE-1040 > Project: Synapse > Issue Type: Bug > Components: Core >Affects Versions: 1.1 >Reporter: isuru janith ranawaka >Assignee: Hiranya Jayathilaka >Priority: Blocker > Fix For: 3.0 > > Attachments: SYNAPSE-1040.diff > > > Clone mediator does not clone all the synapse properties inside Synapse > MessageContext. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Updated] (SYNAPSE-1040) cloneMessageContext in MessageHelper does not deep clone all synapse properties
[ https://issues.apache.org/jira/browse/SYNAPSE-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Udana Loku Narangoda updated SYNAPSE-1040: Fix Version/s: (was: FUTURE) 3.0 > cloneMessageContext in MessageHelper does not deep clone all synapse > properties > > > Key: SYNAPSE-1040 > URL: https://issues.apache.org/jira/browse/SYNAPSE-1040 > Project: Synapse > Issue Type: Bug > Components: Core >Affects Versions: 1.1 >Reporter: isuru janith ranawaka >Assignee: Hiranya Jayathilaka >Priority: Blocker > Fix For: 3.0 > > Attachments: SYNAPSE-1040.diff > > > Clone mediator does not clone all the synapse properties inside Synapse > MessageContext. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Resolved] (SYNAPSE-1042) MessageID returned as Null when a proxy is invoked via a scheduled task
[
https://issues.apache.org/jira/browse/SYNAPSE-1042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Isuru Udana Loku Narangoda resolved SYNAPSE-1042.
-
Resolution: Fixed
Fix Version/s: 3.0
Committed revision 1747332.
Thanks for the contribution.
> MessageID returned as Null when a proxy is invoked via a scheduled task
> ---
>
> Key: SYNAPSE-1042
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1042
> Project: Synapse
> Issue Type: Bug
>Reporter: prabath ariyarathna
>Assignee: Isuru Udana Loku Narangoda
> Fix For: 3.0
>
> Attachments: SYNAPSE-1042.diff
>
>
> When a proxy is invoked by a scheduled task the message ID is returned as
> empty in the insequence.
>
>expression="get-property('MessageID')"/>
>
> INFO LogMediator MESSAGE_ID =
> *Proxy*
>
> {code}
> trace="disable">
>
>
>
>
>expression="get-property('MessageID')"/>
>
>
>
>
>
>expression="get-property('MessageID')"/>
>
>
>
>
>
> {code}
> *Task*
>
> {code}
>
>
>
>value="http://localhost:9000/services/SimpleStockQuoteService"/>
>
>
> http://www.wso2.org/products/wso2commons/tasks;
> name="message">
>http://services.samples;>
>
> IBM
>
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Assigned] (SYNAPSE-1042) MessageID returned as Null when a proxy is invoked via a scheduled task
[
https://issues.apache.org/jira/browse/SYNAPSE-1042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Isuru Udana Loku Narangoda reassigned SYNAPSE-1042:
---
Assignee: Isuru Udana Loku Narangoda (was: Hiranya Jayathilaka)
> MessageID returned as Null when a proxy is invoked via a scheduled task
> ---
>
> Key: SYNAPSE-1042
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1042
> Project: Synapse
> Issue Type: Bug
>Reporter: prabath ariyarathna
>Assignee: Isuru Udana Loku Narangoda
> Attachments: SYNAPSE-1042.diff
>
>
> When a proxy is invoked by a scheduled task the message ID is returned as
> empty in the insequence.
>
>expression="get-property('MessageID')"/>
>
> INFO LogMediator MESSAGE_ID =
> *Proxy*
>
> {code}
> trace="disable">
>
>
>
>
>expression="get-property('MessageID')"/>
>
>
>
>
>
>expression="get-property('MessageID')"/>
>
>
>
>
>
> {code}
> *Task*
>
> {code}
>
>
>
>value="http://localhost:9000/services/SimpleStockQuoteService"/>
>
>
> http://www.wso2.org/products/wso2commons/tasks;
> name="message">
>http://services.samples;>
>
> IBM
>
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
[jira] [Updated] (SYNAPSE-1040) cloneMessageContext in MessageHelper does not deep clone all synapse properties
[ https://issues.apache.org/jira/browse/SYNAPSE-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Udana Loku Narangoda updated SYNAPSE-1040: Priority: Blocker (was: Minor) > cloneMessageContext in MessageHelper does not deep clone all synapse > properties > > > Key: SYNAPSE-1040 > URL: https://issues.apache.org/jira/browse/SYNAPSE-1040 > Project: Synapse > Issue Type: Improvement > Components: Core >Affects Versions: 1.1 >Reporter: isuru janith ranawaka >Assignee: Hiranya Jayathilaka >Priority: Blocker > Fix For: FUTURE > > Attachments: SYNAPSE-1040.diff > > > Clone mediator does not clone all the synapse properties inside Synapse > MessageContext. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
