Please find the complete error log below.
2016-01-26 15:30:27,128] ERROR - PassThroughHttpSender Failed to submit the
response
java.lang.NullPointerException
at
org.apache.synapse.transport.passthru.util.SourceResponseFactory.create(SourceResponseFactory.java:64)
at
Hi All,
Did this fix included to last release?
I'm getting exact same issue in API Manager 1.10 with high concurrency.
Getting exact same NPE mentioned in below JIRA[1]
[1]https://wso2.org/jira/browse/ESBJAVA-4142
Thanks,
sanjeewa.
On Wed, Oct 14, 2015 at 11:09 AM, Jagath Sisirakumara
Hi ESB folks,
Can we get a milestone release of synapse and carbon-mediation including
this fix and another PR I sent to synapse? We have to do a milestone
release of API Manager this week.
Thanks,
NuwanD.
On Mon, Oct 12, 2015 at 11:43 AM, Nuwan Dias wrote:
> Thanks a lot
Hi Nuwan,
Our plan is to do the first milestone release end of next week. With this
we hope to incorporate latest carbon-deployment and kernel releases (if it
released during this week).
Thanks.
On Wed, Oct 14, 2015 at 11:07 AM, Chanaka Fernando
wrote:
> [Adding Jagath]
>
>
[Adding Jagath]
On Wed, Oct 14, 2015 at 10:17 AM, Nuwan Dias wrote:
> Hi ESB folks,
>
> Can we get a milestone release of synapse and carbon-mediation including
> this fix and another PR I sent to synapse? We have to do a milestone
> release of API Manager this week.
>
>
Hi All,
This issue is fixed with the following PR [1]. Thanks for reporting and
helping us to figure out the issue.
[1] https://github.com/wso2/carbon-mediation/pull/467
On Fri, Oct 9, 2015 at 3:41 PM, Chanaka Fernando wrote:
> Hi Sameera,
>
> Your judgment is correct and
Thanks a lot Chanaka.
On Mon, Oct 12, 2015 at 11:39 AM, Chanaka Fernando
wrote:
> Hi All,
>
> This issue is fixed with the following PR [1]. Thanks for reporting and
> helping us to figure out the issue.
>
> [1] https://github.com/wso2/carbon-mediation/pull/467
>
> On Fri,
Any update on this please?
On Thu, Oct 8, 2015 at 10:50 PM, Chanaka Fernando wrote:
> Hi NuwanD,
>
> The fix is not in kernel but in carbon-mediation. What I need is kernel
> team's opinion on usage of the aforementioned method. If we can get their
> input, fix is
Hi Sameera,
Your judgment is correct and it helped us to find the root cause :). I'll
fix the code from carbon-mediation side. Thanks for your input.
On Fri, Oct 9, 2015 at 3:19 PM, Sameera Jayasoma wrote:
> Hi Chanaka,
>
> You don't need to destroy the current context. This
Hi Chanaka,
You don't need to destroy the current context. This part is handle by the
Kernel code. Users of the CarbonContext API do not need to worry about
destroying the context.
Who has done this change? So my initial judgment is correct. :) Stack
cannot become empty.
Thanks,
Sameera.
On
[Adding Kishanthan]
On Thu, Oct 8, 2015 at 6:14 PM, Chanaka Fernando wrote:
> Hi All,
>
> At last, I was able to find the root cause for this behavior. This is
> actually coming from carbon-mediation code. What actually happens is that
> when ESB starts with a tenant, it will
Hi all,
Will this be fixed in kernel 4.4.2? Its causing integration test failures
in API Manager and we would like this to be fixed soon.
Thanks,
NuwanD.
On Thu, Oct 8, 2015 at 6:22 PM, Chanaka Fernando wrote:
> [Adding Kishanthan]
>
> On Thu, Oct 8, 2015 at 6:14 PM,
Hi NuwanD,
The fix is not in kernel but in carbon-mediation. What I need is kernel
team's opinion on usage of the aforementioned method. If we can get their
input, fix is straightforward.
On Thu, Oct 8, 2015 at 9:58 PM, Nuwan Dias wrote:
> Hi all,
>
> Will this be fixed in
Hi Sameera/KasunG,
I have debugged the code to find the root cause for this empty stack
exception. This is causing several other issues at the ESB layer. What
actually happens is that inside the
MultitenantMessageReceiver.processRequest() method, we have the following
code segment.
try {
I think we need to check isEmpty as well.
On Tue, Jul 7, 2015 at 3:41 PM, Jagath Sisirakumara Ariyarathne
jaga...@wso2.com wrote:
Hi,
I am working on [1] and found that the cause of the exception mentioned
below is in the code segment in
Yeah, we should always check for an empty stack.
On Tue, Jul 7, 2015 at 5:17 PM, Malaka Silva mal...@wso2.com wrote:
I think we need to check isEmpty as well.
On Tue, Jul 7, 2015 at 3:41 PM, Jagath Sisirakumara Ariyarathne
jaga...@wso2.com wrote:
Hi,
I am working on [1] and found that
Hi,
I am working on [1] and found that the cause of the exception mentioned
below is in the code segment in
org.wso2.carbon.context.internal.CarbonContextDataHolder
in carbon.utils.
public void endTenantFlow() {
StackCarbonContextDataHolder carbonContextDataHolders =
Hi Carbon Team,
Please review and merge the PR[1] to fix the JIRA[2].
[1] - https://github.com/wso2/carbon4-kernel/pull/285
[2] - https://wso2.org/jira/browse/ESBJAVA-3832
Thanks.
On Tue, Jul 7, 2015 at 5:47 PM, Kasun Indrasiri ka...@wso2.com wrote:
Yeah, we should always check for an empty
I understand, but we need to understand why that stack becomes empty.
AFAIK, if we follow the proper APIs, stack should not become empty
On Tue, Jul 7, 2015 at 5:47 PM, Kasun Indrasiri ka...@wso2.com wrote:
Yeah, we should always check for an empty stack.
On Tue, Jul 7, 2015 at 5:17 PM,
Hi Sameera,
I will check it and update.
Thanks.
On Wed, Jul 8, 2015 at 11:10 AM, Sameera Jayasoma same...@wso2.com wrote:
Hi Jagath,
Can you debug and see whey the stack becomes empty? Thats a serious
problem. Stack should be become empty here.
Checking whether the stack is empty will
Hi Jagath,
Can you debug and see whey the stack becomes empty? Thats a serious
problem. Stack should be become empty here.
Checking whether the stack is empty will stop the error log, but it doesn't
fix the actual problem here.
On Wed, Jul 8, 2015 at 10:50 AM, Sameera Jayasoma same...@wso2.com
21 matches
Mail list logo