On Sat, May 7, 2011 at 8:32 AM, Danushka Menikkumbura danus...@wso2.comwrote:
It still logs an error.
Since this is a problem with bam data publishers and currently has fixed
with setting proper tenant id please revert this change.
It is not a nice thing to catch NullPointerException and the
Hi,
We came up with this during smoke tests. Events published by ESB are not
being received by BAM due to this. I believe it's due to the qpid error.
Please have a look.
Stacktrace:
[2011-05-06 17:04:35,518] DEBUG - PublisherUtils Event payload
svrusrdata:Event xmlns:svrusrdata=
AmilaJ fixed the issue in DefaultRealmService as I heard.
Danushka
On Fri, May 6, 2011 at 5:18 PM, Tharindu Mathew thari...@wso2.com wrote:
Hi,
We came up with this during smoke tests. Events published by ESB are not
being received by BAM due to this. I believe it's due to the qpid error.
Tharindu, please do whatever it takes to get a BAM pack ready today.
On Fri, May 6, 2011 at 5:18 PM, Tharindu Mathew thari...@wso2.com wrote:
Hi,
We came up with this during smoke tests. Events published by ESB are not
being received by BAM due to this. I believe it's due to the qpid error.
Tharindu,
I just checked the DefaultDealmService.java but did not see any change.
Probably the fix went to some other place. Anyway the qpid authz plugin now
handles NPE. So, just update components/qpid and rebuild the BAM.
Thanks,
Danushka
On Fri, May 6, 2011 at 8:22 PM, Afkham Azeez
have you updated the event core with the current trunk or are you working
with some old ESB build?
thanks,
Amila.
On Fri, May 6, 2011 at 5:18 PM, Tharindu Mathew thari...@wso2.com wrote:
Hi,
We came up with this during smoke tests. Events published by ESB are not
being received by BAM due
I do not think event has anything to do with this error.
Danushka
On Fri, May 6, 2011 at 11:01 PM, Amila Suriarachchi am...@wso2.com wrote:
have you updated the event core with the current trunk or are you working
with some old ESB build?
thanks,
Amila.
On Fri, May 6, 2011 at 5:18 PM,
On Fri, May 6, 2011 at 8:12 PM, Danushka Menikkumbura danus...@wso2.com wrote:
AmilaJ fixed the issue in DefaultRealmService as I heard.
Hi Danushka,
I didnt do any modifications to DefaultRealmService with this regard.
Similar error was reported in [Carbon-dev] QPid exception when trying
to
Hi Danushka,
I did bit of debugging with the ESB pack i got from Supun and found following.
The tenant id passed to DefaultRealmService.getTenantUserRealm from
QpidAuthorizationPlugin.getUserRealm is -1. Thus according to
DefaultRealmService.getTenantUserRealm logic the tenant id -1 does not
Hi Amila,
I think there was some miscommunication. Supun, correct me if I am wrong.
Anyway I have now handled NPE in the Qpid code too.
But still I wonder how the Qpid call passes a -1. See the code snippet given
below. This was done last week when we tested MB Stratos version.
// Get tenant
This can happen because of the following code, if some one has not set the
tenant details properly when calling the event publish method.
String userName = ;
if (CarbonContext.getCurrentContext().getTenantId() != 0) {
userName = CarbonContext.getCurrentContext().getUsername()
On Sat, May 7, 2011 at 6:23 AM, Danushka Menikkumbura danus...@wso2.comwrote:
Hi Amila,
I think there was some miscommunication. Supun, correct me if I am wrong.
Anyway I have now handled NPE in the Qpid code too.
If the reason what I have given is correct please revert this change. This
It still logs an error.
On Sat, May 7, 2011 at 8:02 AM, Amila Suriarachchi am...@wso2.com wrote:
On Sat, May 7, 2011 at 6:23 AM, Danushka Menikkumbura
danus...@wso2.comwrote:
Hi Amila,
I think there was some miscommunication. Supun, correct me if I am wrong.
Anyway I have now handled
13 matches
Mail list logo
