Re: [Carbon-dev] Events are not getting published in latest packs due to qpid error
On Sat, May 7, 2011 at 8:32 AM, Danushka Menikkumbura wrote:
> 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 log messages
may gone undetected.
thanks,
Amila.
>
>
> On Sat, May 7, 2011 at 8:02 AM, Amila Suriarachchi wrote:
>
>>
>>
>> On Sat, May 7, 2011 at 6:23 AM, Danushka Menikkumbura
>> wrote:
>>
>>> 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
>> may lead to such wrong invocations gone undetected.
>>
>> thanks,
>> Amila.
>>
>>
>>>
>>> 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 ID
>>> int tenantID = 0;
>>> int domainNameSeparatorIndex =
>>> username.indexOf(DOMAIN_NAME_SEPARATOR);
>>> if (-1 != domainNameSeparatorIndex) { // Service case
>>> String domainName =
>>> username.substring(domainNameSeparatorIndex + 1);
>>> tenantID =
>>> realmService.getTenantManager().getTenantId(domainName);
>>> }
>>>
>>> // Get Realm
>>> userRealm = realmService.getTenantUserRealm(tenantID);
>>>
>>> Thanks,
>>> Danushka
>>>
>>>
>>> On Sat, May 7, 2011 at 2:32 AM, Amila Jayasekara wrote:
>>>
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
have a special meaning and also it is not representing a normal
tenant. Since RealmService cannot find the appropriate tenant when
trying to retrieve Realm it gives a null pointer exception.
I believe what you actually need is super tenant realm (Since this is
running in stand alone mode). You need to pass 0 instead of -1.
I will add a null check to tenant, before getting RealmService; to
give a descriptive error message.
Thanks
AmilaJ
On Sat, May 7, 2011 at 2:05 AM, Amila Jayasekara
wrote:
> 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 invoke an admin service" mail thread.
> But later in the same thread you informed the issue was not
> reproducible with a fresh installation.
>
> Let me again investigate the pack i got from Supun.
>
> Thanks
> AmilaJ
>
>>
>> Danushka
>>
>> On Fri, May 6, 2011 at 5:18 PM, Tharindu Mathew
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.
>>> Please have a look.
>>> Stacktrace:
>>> [2011-05-06 17:04:35,518] DEBUG - PublisherUtils Event payload
>>> >>> >>> xmlns:svrusrdata="
http://wso2.org/ns/2009/09/bam/server/user-defined/data
">
https://10.100.0.191:9444
0ProxyOutMaxProcessingTime-lafProxy1ProxyOutAvgProcessingTime-lafProxy0.ProxyOutMinProcessingTime-lafProxy0ProxyOutCount-lafProxy27ProxyOutCumulativeCount-lafProxy27ProxyOutFaultCount-lafProxy0ProxyOutIDlafProxy
>>> [2011-05-06 17:04:35,518] DEBUG - BAMMediationStatisticsObserver
>>> ComponentType.PROXYSERVICE >>> >>> xmlns:svrusrdata="
http://wso2.org/ns/2009/09/bam/server/user-defined/data
">
https://10.100.0.191:9444
0ProxyOutMaxProcessingTime-lafProxy1ProxyOutAvgProcessingTime-lafProxy0.ProxyOutMinProcessingTime-lafProxy0ProxyOutCount-lafProxy27ProxyOutCumulativeCount-lafProxy27ProxyOutFaultCount-lafProxy0ProxyOutIDlafProxy
>>> [2011-05-06 17:04:35,528] DEBUG - BAMMediationStatisticsObserver
Event is
>>> published>>> >>> xmlns:svrusrdata="
http://wso2.org/ns/2009/09/bam/server/user-defined/data
">
https://10.100.0.191:9444
0ProxyOutMaxProcessingTime-lafProxy1ProxyOutAvgProcessingTime-lafProxy0.ProxyOutMinProcessingTime-lafProxy0ProxyOutCount-lafProxy27ProxyOutCumulativeCount-lafProxy27ProxyOutFaultCount-lafProxy0ProxyOutIDlafProxy
>>> [2011-05-06 17:04:35,597] ERROR - DefaultRealmService
>>> java.lang.NullPointerException
>>> at
>>>
>>
Re: [Carbon-dev] Events are not getting published in latest packs due to qpid error
It still logs an error.
On Sat, May 7, 2011 at 8:02 AM, Amila Suriarachchi wrote:
>
>
> On Sat, May 7, 2011 at 6:23 AM, Danushka Menikkumbura
> wrote:
>
>> 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
> may lead to such wrong invocations gone undetected.
>
> thanks,
> Amila.
>
>
>>
>> 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 ID
>> int tenantID = 0;
>> int domainNameSeparatorIndex =
>> username.indexOf(DOMAIN_NAME_SEPARATOR);
>> if (-1 != domainNameSeparatorIndex) { // Service case
>> String domainName =
>> username.substring(domainNameSeparatorIndex + 1);
>> tenantID =
>> realmService.getTenantManager().getTenantId(domainName);
>> }
>>
>> // Get Realm
>> userRealm = realmService.getTenantUserRealm(tenantID);
>>
>> Thanks,
>> Danushka
>>
>>
>> On Sat, May 7, 2011 at 2:32 AM, Amila Jayasekara wrote:
>>
>>> 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
>>> have a special meaning and also it is not representing a normal
>>> tenant. Since RealmService cannot find the appropriate tenant when
>>> trying to retrieve Realm it gives a null pointer exception.
>>>
>>> I believe what you actually need is super tenant realm (Since this is
>>> running in stand alone mode). You need to pass 0 instead of -1.
>>>
>>> I will add a null check to tenant, before getting RealmService; to
>>> give a descriptive error message.
>>>
>>> Thanks
>>> AmilaJ
>>>
>>>
>>> On Sat, May 7, 2011 at 2:05 AM, Amila Jayasekara
>>> wrote:
>>> > 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 invoke an admin service" mail thread.
>>> > But later in the same thread you informed the issue was not
>>> > reproducible with a fresh installation.
>>> >
>>> > Let me again investigate the pack i got from Supun.
>>> >
>>> > Thanks
>>> > AmilaJ
>>> >
>>> >>
>>> >> Danushka
>>> >>
>>> >> On Fri, May 6, 2011 at 5:18 PM, Tharindu Mathew
>>> 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.
>>> >>> Please have a look.
>>> >>> Stacktrace:
>>> >>> [2011-05-06 17:04:35,518] DEBUG - PublisherUtils Event payload
>>> >>> >> >>> xmlns:svrusrdata="
>>> http://wso2.org/ns/2009/09/bam/server/user-defined/data
>>> ">
>>> https://10.100.0.191:9444
>>> 0ProxyOutMaxProcessingTime-lafProxy1ProxyOutAvgProcessingTime-lafProxy0.ProxyOutMinProcessingTime-lafProxy0ProxyOutCount-lafProxy27ProxyOutCumulativeCount-lafProxy27ProxyOutFaultCount-lafProxy0ProxyOutIDlafProxy
>>> >>> [2011-05-06 17:04:35,518] DEBUG - BAMMediationStatisticsObserver
>>> >>> ComponentType.PROXYSERVICE >> >>> xmlns:svrusrdata="
>>> http://wso2.org/ns/2009/09/bam/server/user-defined/data
>>> ">
>>> https://10.100.0.191:9444
>>> 0ProxyOutMaxProcessingTime-lafProxy1ProxyOutAvgProcessingTime-lafProxy0.ProxyOutMinProcessingTime-lafProxy0ProxyOutCount-lafProxy27ProxyOutCumulativeCount-lafProxy27ProxyOutFaultCount-lafProxy0ProxyOutIDlafProxy
>>> >>> [2011-05-06 17:04:35,528] DEBUG - BAMMediationStatisticsObserver
>>> Event is
>>> >>> published>> >>> xmlns:svrusrdata="
>>> http://wso2.org/ns/2009/09/bam/server/user-defined/data
>>> ">
>>> https://10.100.0.191:9444
>>> 0ProxyOutMaxProcessingTime-lafProxy1ProxyOutAvgProcessingTime-lafProxy0.ProxyOutMinProcessingTime-lafProxy0ProxyOutCount-lafProxy27ProxyOutCumulativeCount-lafProxy27ProxyOutFaultCount-lafProxy0ProxyOutIDlafProxy
>>> >>> [2011-05-06 17:04:35,597] ERROR - DefaultRealmService
>>> >>> java.lang.NullPointerException
>>> >>> at
>>> >>>
>>> org.wso2.carbon.user.core.common.DefaultRealmService.getTenantUserRealm(DefaultRealmService.java:157)
>>> >>> at
>>> >>>
>>> org.wso2.carbon.qpid.authorization.service.qpid.QpidAuthorizationPlugin.getUserRealm(QpidAuthorizationPlugin.java:184)
>>> >>> at
>>> >>>
>>> org.wso2.carbon.qpid.authorization.service.qpid.QpidAuthorizationPlugin.authorise(QpidAuthorizationPlugin.java:124)
>>> >>> at
>>> >>>
>>> org.apache.qpid.server.securi
Re: [Carbon-dev] Events are not getting published in latest packs due to qpid error
On Sat, May 7, 2011 at 6:23 AM, Danushka Menikkumbura wrote:
> 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
may lead to such wrong invocations gone undetected.
thanks,
Amila.
>
> 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 ID
> int tenantID = 0;
> int domainNameSeparatorIndex =
> username.indexOf(DOMAIN_NAME_SEPARATOR);
> if (-1 != domainNameSeparatorIndex) { // Service case
> String domainName =
> username.substring(domainNameSeparatorIndex + 1);
> tenantID =
> realmService.getTenantManager().getTenantId(domainName);
> }
>
> // Get Realm
> userRealm = realmService.getTenantUserRealm(tenantID);
>
> Thanks,
> Danushka
>
>
> On Sat, May 7, 2011 at 2:32 AM, Amila Jayasekara wrote:
>
>> 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
>> have a special meaning and also it is not representing a normal
>> tenant. Since RealmService cannot find the appropriate tenant when
>> trying to retrieve Realm it gives a null pointer exception.
>>
>> I believe what you actually need is super tenant realm (Since this is
>> running in stand alone mode). You need to pass 0 instead of -1.
>>
>> I will add a null check to tenant, before getting RealmService; to
>> give a descriptive error message.
>>
>> Thanks
>> AmilaJ
>>
>>
>> On Sat, May 7, 2011 at 2:05 AM, Amila Jayasekara wrote:
>> > 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 invoke an admin service" mail thread.
>> > But later in the same thread you informed the issue was not
>> > reproducible with a fresh installation.
>> >
>> > Let me again investigate the pack i got from Supun.
>> >
>> > Thanks
>> > AmilaJ
>> >
>> >>
>> >> Danushka
>> >>
>> >> On Fri, May 6, 2011 at 5:18 PM, Tharindu Mathew
>> 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.
>> >>> Please have a look.
>> >>> Stacktrace:
>> >>> [2011-05-06 17:04:35,518] DEBUG - PublisherUtils Event payload
>> >>> > >>> xmlns:svrusrdata="
>> http://wso2.org/ns/2009/09/bam/server/user-defined/data
>> ">
>> https://10.100.0.191:9444
>> 0ProxyOutMaxProcessingTime-lafProxy1ProxyOutAvgProcessingTime-lafProxy0.ProxyOutMinProcessingTime-lafProxy0ProxyOutCount-lafProxy27ProxyOutCumulativeCount-lafProxy27ProxyOutFaultCount-lafProxy0ProxyOutIDlafProxy
>> >>> [2011-05-06 17:04:35,518] DEBUG - BAMMediationStatisticsObserver
>> >>> ComponentType.PROXYSERVICE > >>> xmlns:svrusrdata="
>> http://wso2.org/ns/2009/09/bam/server/user-defined/data
>> ">
>> https://10.100.0.191:9444
>> 0ProxyOutMaxProcessingTime-lafProxy1ProxyOutAvgProcessingTime-lafProxy0.ProxyOutMinProcessingTime-lafProxy0ProxyOutCount-lafProxy27ProxyOutCumulativeCount-lafProxy27ProxyOutFaultCount-lafProxy0ProxyOutIDlafProxy
>> >>> [2011-05-06 17:04:35,528] DEBUG - BAMMediationStatisticsObserver Event
>> is
>> >>> published> >>> xmlns:svrusrdata="
>> http://wso2.org/ns/2009/09/bam/server/user-defined/data
>> ">
>> https://10.100.0.191:9444
>> 0ProxyOutMaxProcessingTime-lafProxy1ProxyOutAvgProcessingTime-lafProxy0.ProxyOutMinProcessingTime-lafProxy0ProxyOutCount-lafProxy27ProxyOutCumulativeCount-lafProxy27ProxyOutFaultCount-lafProxy0ProxyOutIDlafProxy
>> >>> [2011-05-06 17:04:35,597] ERROR - DefaultRealmService
>> >>> java.lang.NullPointerException
>> >>> at
>> >>>
>> org.wso2.carbon.user.core.common.DefaultRealmService.getTenantUserRealm(DefaultRealmService.java:157)
>> >>> at
>> >>>
>> org.wso2.carbon.qpid.authorization.service.qpid.QpidAuthorizationPlugin.getUserRealm(QpidAuthorizationPlugin.java:184)
>> >>> at
>> >>>
>> org.wso2.carbon.qpid.authorization.service.qpid.QpidAuthorizationPlugin.authorise(QpidAuthorizationPlugin.java:124)
>> >>> at
>> >>>
>> org.apache.qpid.server.security.SecurityManager$11.allowed(SecurityManager.java:390)
>> >>> at
>> >>>
>> org.apache.qpid.server.security.SecurityManager.checkAllPlugins(SecurityManager.java:245)
>> >>> at
>> >>>
>> org.apache.qpid.server.security.SecurityMana
Re: [Carbon-dev] Events are not getting published in latest packs due to qpid error
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() + "@"
+ CarbonContext.getCurrentContext().getTenantDomain();
} else {
userName = CarbonContext.getCurrentContext().getUsername();
}
return userName;
In that case tenant id will be -1 and hence user name will be admin@null
Tharindu can you please check whether BAM calls the super tenant follows
properly like this,
try {
SuperTenantCarbonContext.startTenantFlow();
SuperTenantCarbonContext.getCurrentContext().setTenantId(tenantID);
SuperTenantCarbonContext.getCurrentContext().getTenantDomain(true);
this.delivaryManager.publish(this.message, this.topicName,
this.deliveryMode);
} catch (EventBrokerException e) {
log.error("Can not publish the message ", e);
} finally {
SuperTenantCarbonContext.endTenantFlow();
}
please see the relavent disscussion in stratos deve as well.
thanks,
Amila.
On Sat, May 7, 2011 at 6:23 AM, Danushka Menikkumbura wrote:
> 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 ID
> int tenantID = 0;
> int domainNameSeparatorIndex =
> username.indexOf(DOMAIN_NAME_SEPARATOR);
> if (-1 != domainNameSeparatorIndex) { // Service case
> String domainName =
> username.substring(domainNameSeparatorIndex + 1);
> tenantID =
> realmService.getTenantManager().getTenantId(domainName);
> }
>
> // Get Realm
> userRealm = realmService.getTenantUserRealm(tenantID);
>
> Thanks,
> Danushka
>
>
> On Sat, May 7, 2011 at 2:32 AM, Amila Jayasekara wrote:
>
>> 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
>> have a special meaning and also it is not representing a normal
>> tenant. Since RealmService cannot find the appropriate tenant when
>> trying to retrieve Realm it gives a null pointer exception.
>>
>> I believe what you actually need is super tenant realm (Since this is
>> running in stand alone mode). You need to pass 0 instead of -1.
>>
>> I will add a null check to tenant, before getting RealmService; to
>> give a descriptive error message.
>>
>> Thanks
>> AmilaJ
>>
>>
>> On Sat, May 7, 2011 at 2:05 AM, Amila Jayasekara wrote:
>> > 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 invoke an admin service" mail thread.
>> > But later in the same thread you informed the issue was not
>> > reproducible with a fresh installation.
>> >
>> > Let me again investigate the pack i got from Supun.
>> >
>> > Thanks
>> > AmilaJ
>> >
>> >>
>> >> Danushka
>> >>
>> >> On Fri, May 6, 2011 at 5:18 PM, Tharindu Mathew
>> 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.
>> >>> Please have a look.
>> >>> Stacktrace:
>> >>> [2011-05-06 17:04:35,518] DEBUG - PublisherUtils Event payload
>> >>> > >>> xmlns:svrusrdata="
>> http://wso2.org/ns/2009/09/bam/server/user-defined/data
>> ">
>> https://10.100.0.191:9444
>> 0ProxyOutMaxProcessingTime-lafProxy1ProxyOutAvgProcessingTime-lafProxy0.ProxyOutMinProcessingTime-lafProxy0ProxyOutCount-lafProxy27ProxyOutCumulativeCount-lafProxy27ProxyOutFaultCount-lafProxy0ProxyOutIDlafProxy
>> >>> [2011-05-06 17:04:35,518] DEBUG - BAMMediationStatisticsObserver
>> >>> ComponentType.PROXYSERVICE > >>> xmlns:svrusrdata="
>> http://wso2.org/ns/2009/09/bam/server/user-defined/data
>> ">
>> https://10.100.0.191:9444
>> 0ProxyOutMaxProcessingTime-lafProxy1ProxyOutAvgProcessingTime-lafProxy0.ProxyOutMinProcessingTime-lafProxy0ProxyOutCount-lafProxy27ProxyOutCumulativeCount-lafProxy27ProxyOutFaultCount-lafProxy0ProxyOutIDlafProxy
>> >>> [2011-05-06 17:04:35,528] DEBUG - BAMMediationStatisticsObserver Event
>> is
>> >>> published> >>> xmlns:svrusrdata="
>> http://wso2.org
Re: [Carbon-dev] Events are not getting published in latest packs due to qpid error
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 ID
int tenantID = 0;
int domainNameSeparatorIndex =
username.indexOf(DOMAIN_NAME_SEPARATOR);
if (-1 != domainNameSeparatorIndex) { // Service case
String domainName =
username.substring(domainNameSeparatorIndex + 1);
tenantID =
realmService.getTenantManager().getTenantId(domainName);
}
// Get Realm
userRealm = realmService.getTenantUserRealm(tenantID);
Thanks,
Danushka
On Sat, May 7, 2011 at 2:32 AM, Amila Jayasekara wrote:
> 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
> have a special meaning and also it is not representing a normal
> tenant. Since RealmService cannot find the appropriate tenant when
> trying to retrieve Realm it gives a null pointer exception.
>
> I believe what you actually need is super tenant realm (Since this is
> running in stand alone mode). You need to pass 0 instead of -1.
>
> I will add a null check to tenant, before getting RealmService; to
> give a descriptive error message.
>
> Thanks
> AmilaJ
>
>
> On Sat, May 7, 2011 at 2:05 AM, Amila Jayasekara wrote:
> > On Fri, May 6, 2011 at 8:12 PM, Danushka Menikkumbura
> 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 invoke an admin service" mail thread.
> > But later in the same thread you informed the issue was not
> > reproducible with a fresh installation.
> >
> > Let me again investigate the pack i got from Supun.
> >
> > Thanks
> > AmilaJ
> >
> >>
> >> Danushka
> >>
> >> On Fri, May 6, 2011 at 5:18 PM, Tharindu Mathew
> 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.
> >>> Please have a look.
> >>> Stacktrace:
> >>> [2011-05-06 17:04:35,518] DEBUG - PublisherUtils Event payload
> >>> >>> xmlns:svrusrdata="
> http://wso2.org/ns/2009/09/bam/server/user-defined/data
> ">
> https://10.100.0.191:9444
> 0ProxyOutMaxProcessingTime-lafProxy1ProxyOutAvgProcessingTime-lafProxy0.ProxyOutMinProcessingTime-lafProxy0ProxyOutCount-lafProxy27ProxyOutCumulativeCount-lafProxy27ProxyOutFaultCount-lafProxy0ProxyOutIDlafProxy
> >>> [2011-05-06 17:04:35,518] DEBUG - BAMMediationStatisticsObserver
> >>> ComponentType.PROXYSERVICE >>> xmlns:svrusrdata="
> http://wso2.org/ns/2009/09/bam/server/user-defined/data
> ">
> https://10.100.0.191:9444
> 0ProxyOutMaxProcessingTime-lafProxy1ProxyOutAvgProcessingTime-lafProxy0.ProxyOutMinProcessingTime-lafProxy0ProxyOutCount-lafProxy27ProxyOutCumulativeCount-lafProxy27ProxyOutFaultCount-lafProxy0ProxyOutIDlafProxy
> >>> [2011-05-06 17:04:35,528] DEBUG - BAMMediationStatisticsObserver Event
> is
> >>> published >>> xmlns:svrusrdata="
> http://wso2.org/ns/2009/09/bam/server/user-defined/data
> ">
> https://10.100.0.191:9444
> 0ProxyOutMaxProcessingTime-lafProxy1ProxyOutAvgProcessingTime-lafProxy0.ProxyOutMinProcessingTime-lafProxy0ProxyOutCount-lafProxy27ProxyOutCumulativeCount-lafProxy27ProxyOutFaultCount-lafProxy0ProxyOutIDlafProxy
> >>> [2011-05-06 17:04:35,597] ERROR - DefaultRealmService
> >>> java.lang.NullPointerException
> >>> at
> >>>
> org.wso2.carbon.user.core.common.DefaultRealmService.getTenantUserRealm(DefaultRealmService.java:157)
> >>> at
> >>>
> org.wso2.carbon.qpid.authorization.service.qpid.QpidAuthorizationPlugin.getUserRealm(QpidAuthorizationPlugin.java:184)
> >>> at
> >>>
> org.wso2.carbon.qpid.authorization.service.qpid.QpidAuthorizationPlugin.authorise(QpidAuthorizationPlugin.java:124)
> >>> at
> >>>
> org.apache.qpid.server.security.SecurityManager$11.allowed(SecurityManager.java:390)
> >>> at
> >>>
> org.apache.qpid.server.security.SecurityManager.checkAllPlugins(SecurityManager.java:245)
> >>> at
> >>>
> org.apache.qpid.server.security.SecurityManager.authorisePublish(SecurityManager.java:386)
> >>> at
> >>>
> org.apache.qpid.server.transport.ServerSessionDelegate.messageTransfer(ServerSessionDelegate.java:307)
> >>> at
> >>>
> org.apache.qpid.server.transport.ServerSessionDelegate.messageTransfer(ServerSessionDelegate.java:96)
> >>> at
> >>>
> org.apache.qpid.transport.MessageTransfer.dispatch(MessageTransfer.java:
Re: [Carbon-dev] Events are not getting published in latest packs due to qpid error
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 have a special meaning and also it is not representing a normal tenant. Since RealmService cannot find the appropriate tenant when trying to retrieve Realm it gives a null pointer exception. I believe what you actually need is super tenant realm (Since this is running in stand alone mode). You need to pass 0 instead of -1. I will add a null check to tenant, before getting RealmService; to give a descriptive error message. Thanks AmilaJ On Sat, May 7, 2011 at 2:05 AM, Amila Jayasekara wrote: > On Fri, May 6, 2011 at 8:12 PM, Danushka Menikkumbura > 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 invoke an admin service" mail thread. > But later in the same thread you informed the issue was not > reproducible with a fresh installation. > > Let me again investigate the pack i got from Supun. > > Thanks > AmilaJ > >> >> Danushka >> >> On Fri, May 6, 2011 at 5:18 PM, Tharindu Mathew 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. >>> Please have a look. >>> Stacktrace: >>> [2011-05-06 17:04:35,518] DEBUG - PublisherUtils Event payload >>> >> xmlns:svrusrdata="http://wso2.org/ns/2009/09/bam/server/user-defined/data";>https://10.100.0.191:94440ProxyOutMaxProcessingTime-lafProxy1ProxyOutAvgProcessingTime-lafProxy0.ProxyOutMinProcessingTime-lafProxy0ProxyOutCount-lafProxy27ProxyOutCumulativeCount-lafProxy27ProxyOutFaultCount-lafProxy0ProxyOutIDlafProxy >>> [2011-05-06 17:04:35,518] DEBUG - BAMMediationStatisticsObserver >>> ComponentType.PROXYSERVICE >> xmlns:svrusrdata="http://wso2.org/ns/2009/09/bam/server/user-defined/data";>https://10.100.0.191:94440ProxyOutMaxProcessingTime-lafProxy1ProxyOutAvgProcessingTime-lafProxy0.ProxyOutMinProcessingTime-lafProxy0ProxyOutCount-lafProxy27ProxyOutCumulativeCount-lafProxy27ProxyOutFaultCount-lafProxy0ProxyOutIDlafProxy >>> [2011-05-06 17:04:35,528] DEBUG - BAMMediationStatisticsObserver Event is >>> published>> xmlns:svrusrdata="http://wso2.org/ns/2009/09/bam/server/user-defined/data";>https://10.100.0.191:94440ProxyOutMaxProcessingTime-lafProxy1ProxyOutAvgProcessingTime-lafProxy0.ProxyOutMinProcessingTime-lafProxy0ProxyOutCount-lafProxy27ProxyOutCumulativeCount-lafProxy27ProxyOutFaultCount-lafProxy0ProxyOutIDlafProxy >>> [2011-05-06 17:04:35,597] ERROR - DefaultRealmService >>> java.lang.NullPointerException >>> at >>> org.wso2.carbon.user.core.common.DefaultRealmService.getTenantUserRealm(DefaultRealmService.java:157) >>> at >>> org.wso2.carbon.qpid.authorization.service.qpid.QpidAuthorizationPlugin.getUserRealm(QpidAuthorizationPlugin.java:184) >>> at >>> org.wso2.carbon.qpid.authorization.service.qpid.QpidAuthorizationPlugin.authorise(QpidAuthorizationPlugin.java:124) >>> at >>> org.apache.qpid.server.security.SecurityManager$11.allowed(SecurityManager.java:390) >>> at >>> org.apache.qpid.server.security.SecurityManager.checkAllPlugins(SecurityManager.java:245) >>> at >>> org.apache.qpid.server.security.SecurityManager.authorisePublish(SecurityManager.java:386) >>> at >>> org.apache.qpid.server.transport.ServerSessionDelegate.messageTransfer(ServerSessionDelegate.java:307) >>> at >>> org.apache.qpid.server.transport.ServerSessionDelegate.messageTransfer(ServerSessionDelegate.java:96) >>> at >>> org.apache.qpid.transport.MessageTransfer.dispatch(MessageTransfer.java:108) >>> at >>> org.apache.qpid.transport.SessionDelegate.command(SessionDelegate.java:50) >>> at >>> org.apache.qpid.server.transport.ServerSessionDelegate.command(ServerSessionDelegate.java:112) >>> at >>> org.apache.qpid.server.transport.ServerSessionDelegate.command(ServerSessionDelegate.java:96) >>> at org.apache.qpid.transport.Method.delegate(Method.java:159) >>> at org.apache.qpid.transport.Session.received(Session.java:500) >>> at org.apache.qpid.transport.Connection.dispatch(Connection.java:404) >>> at >>> org.apache.qpid.transport.ConnectionDelegate.handle(ConnectionDelegate.java:64) >>> at >>> org.apache.qpid.transport.ConnectionDelegate.handle(ConnectionDelegate.java:40) >>> at >>> org.apache.qpid.transport.MethodDelegate.messageTransfer(MethodDelegate.java:113) >>> at >>> org.apache.qpid.transport.MessageTransfer.dispatch(MessageTransfer.java:108) >>> at >>> org.apache.qpid.transport.ConnectionDelegate.command(ConnectionDelegate.java:54) >>> at >>> org.apache.qpid.transport.ConnectionDelegate.command(ConnectionDelegate.java:40) >>> at org.apach
Re: [Carbon-dev] Events are not getting published in latest packs due to qpid error
On Fri, May 6, 2011 at 8:12 PM, Danushka Menikkumbura 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 invoke an admin service" mail thread. But later in the same thread you informed the issue was not reproducible with a fresh installation. Let me again investigate the pack i got from Supun. Thanks AmilaJ > > Danushka > > On Fri, May 6, 2011 at 5:18 PM, Tharindu Mathew 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. >> Please have a look. >> Stacktrace: >> [2011-05-06 17:04:35,518] DEBUG - PublisherUtils Event payload >> > xmlns:svrusrdata="http://wso2.org/ns/2009/09/bam/server/user-defined/data";>https://10.100.0.191:94440ProxyOutMaxProcessingTime-lafProxy1ProxyOutAvgProcessingTime-lafProxy0.ProxyOutMinProcessingTime-lafProxy0ProxyOutCount-lafProxy27ProxyOutCumulativeCount-lafProxy27ProxyOutFaultCount-lafProxy0ProxyOutIDlafProxy >> [2011-05-06 17:04:35,518] DEBUG - BAMMediationStatisticsObserver >> ComponentType.PROXYSERVICE > xmlns:svrusrdata="http://wso2.org/ns/2009/09/bam/server/user-defined/data";>https://10.100.0.191:94440ProxyOutMaxProcessingTime-lafProxy1ProxyOutAvgProcessingTime-lafProxy0.ProxyOutMinProcessingTime-lafProxy0ProxyOutCount-lafProxy27ProxyOutCumulativeCount-lafProxy27ProxyOutFaultCount-lafProxy0ProxyOutIDlafProxy >> [2011-05-06 17:04:35,528] DEBUG - BAMMediationStatisticsObserver Event is >> published> xmlns:svrusrdata="http://wso2.org/ns/2009/09/bam/server/user-defined/data";>https://10.100.0.191:94440ProxyOutMaxProcessingTime-lafProxy1ProxyOutAvgProcessingTime-lafProxy0.ProxyOutMinProcessingTime-lafProxy0ProxyOutCount-lafProxy27ProxyOutCumulativeCount-lafProxy27ProxyOutFaultCount-lafProxy0ProxyOutIDlafProxy >> [2011-05-06 17:04:35,597] ERROR - DefaultRealmService >> java.lang.NullPointerException >> at >> org.wso2.carbon.user.core.common.DefaultRealmService.getTenantUserRealm(DefaultRealmService.java:157) >> at >> org.wso2.carbon.qpid.authorization.service.qpid.QpidAuthorizationPlugin.getUserRealm(QpidAuthorizationPlugin.java:184) >> at >> org.wso2.carbon.qpid.authorization.service.qpid.QpidAuthorizationPlugin.authorise(QpidAuthorizationPlugin.java:124) >> at >> org.apache.qpid.server.security.SecurityManager$11.allowed(SecurityManager.java:390) >> at >> org.apache.qpid.server.security.SecurityManager.checkAllPlugins(SecurityManager.java:245) >> at >> org.apache.qpid.server.security.SecurityManager.authorisePublish(SecurityManager.java:386) >> at >> org.apache.qpid.server.transport.ServerSessionDelegate.messageTransfer(ServerSessionDelegate.java:307) >> at >> org.apache.qpid.server.transport.ServerSessionDelegate.messageTransfer(ServerSessionDelegate.java:96) >> at >> org.apache.qpid.transport.MessageTransfer.dispatch(MessageTransfer.java:108) >> at >> org.apache.qpid.transport.SessionDelegate.command(SessionDelegate.java:50) >> at >> org.apache.qpid.server.transport.ServerSessionDelegate.command(ServerSessionDelegate.java:112) >> at >> org.apache.qpid.server.transport.ServerSessionDelegate.command(ServerSessionDelegate.java:96) >> at org.apache.qpid.transport.Method.delegate(Method.java:159) >> at org.apache.qpid.transport.Session.received(Session.java:500) >> at org.apache.qpid.transport.Connection.dispatch(Connection.java:404) >> at >> org.apache.qpid.transport.ConnectionDelegate.handle(ConnectionDelegate.java:64) >> at >> org.apache.qpid.transport.ConnectionDelegate.handle(ConnectionDelegate.java:40) >> at >> org.apache.qpid.transport.MethodDelegate.messageTransfer(MethodDelegate.java:113) >> at >> org.apache.qpid.transport.MessageTransfer.dispatch(MessageTransfer.java:108) >> at >> org.apache.qpid.transport.ConnectionDelegate.command(ConnectionDelegate.java:54) >> at >> org.apache.qpid.transport.ConnectionDelegate.command(ConnectionDelegate.java:40) >> at org.apache.qpid.transport.Method.delegate(Method.java:159) >> at org.apache.qpid.transport.Connection.received(Connection.java:369) >> at >> org.apache.qpid.server.transport.ServerConnection.received(ServerConnection.java:196) >> at >> org.apache.qpid.server.transport.ServerConnection.received(ServerConnection.java:53) >> at org.apache.qpid.transport.network.Assembler.emit(Assembler.java:95) >> at >> org.apache.qpid.transport.network.Assembler.assemble(Assembler.java:217) >> at org.apache.qpid.transport.network.Assembler.frame(Assembler.java:129) >> at org.apache.qpid.transport.network.Frame.delegate(Frame.java:133) >> at >> org.apache.qpid.transport.network.Assembler.received(Assembler.java:100) >> at org.apache.qpid.transport.network.Assembler.received(Assembler.java:42) >> at >> org.apache.qpid.transport.network.InputHandler.next(InputHandler.java:187) >> at >> org.apache.qpid.tran
Re: [Carbon-dev] Events are not getting published in latest packs due to qpid error
I do not think event has anything to do with this error. Danushka On Fri, May 6, 2011 at 11:01 PM, Amila Suriarachchi 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, Tharindu Mathew 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. >> Please have a look. >> >> Stacktrace: >> >> [2011-05-06 17:04:35,518] DEBUG - PublisherUtils Event payload >> http://wso2.org/ns/2009/09/bam/server/user-defined/data >> "> >> https://10.100.0.191:9444 >> 0ProxyOutMaxProcessingTime-lafProxy1ProxyOutAvgProcessingTime-lafProxy0.ProxyOutMinProcessingTime-lafProxy0ProxyOutCount-lafProxy27ProxyOutCumulativeCount-lafProxy27ProxyOutFaultCount-lafProxy0ProxyOutIDlafProxy >> [2011-05-06 17:04:35,518] DEBUG - BAMMediationStatisticsObserver >> ComponentType.PROXYSERVICE http://wso2.org/ns/2009/09/bam/server/user-defined/data >> "> >> https://10.100.0.191:9444 >> 0ProxyOutMaxProcessingTime-lafProxy1ProxyOutAvgProcessingTime-lafProxy0.ProxyOutMinProcessingTime-lafProxy0ProxyOutCount-lafProxy27ProxyOutCumulativeCount-lafProxy27ProxyOutFaultCount-lafProxy0ProxyOutIDlafProxy >> [2011-05-06 17:04:35,528] DEBUG - BAMMediationStatisticsObserver Event is >> publishedhttp://wso2.org/ns/2009/09/bam/server/user-defined/data >> "> >> https://10.100.0.191:9444 >> 0ProxyOutMaxProcessingTime-lafProxy1ProxyOutAvgProcessingTime-lafProxy0.ProxyOutMinProcessingTime-lafProxy0ProxyOutCount-lafProxy27ProxyOutCumulativeCount-lafProxy27ProxyOutFaultCount-lafProxy0ProxyOutIDlafProxy >> [2011-05-06 17:04:35,597] ERROR - DefaultRealmService >> java.lang.NullPointerException >> at >> org.wso2.carbon.user.core.common.DefaultRealmService.getTenantUserRealm(DefaultRealmService.java:157) >> at >> org.wso2.carbon.qpid.authorization.service.qpid.QpidAuthorizationPlugin.getUserRealm(QpidAuthorizationPlugin.java:184) >> at >> org.wso2.carbon.qpid.authorization.service.qpid.QpidAuthorizationPlugin.authorise(QpidAuthorizationPlugin.java:124) >> at >> org.apache.qpid.server.security.SecurityManager$11.allowed(SecurityManager.java:390) >> at >> org.apache.qpid.server.security.SecurityManager.checkAllPlugins(SecurityManager.java:245) >> at >> org.apache.qpid.server.security.SecurityManager.authorisePublish(SecurityManager.java:386) >> at >> org.apache.qpid.server.transport.ServerSessionDelegate.messageTransfer(ServerSessionDelegate.java:307) >> at >> org.apache.qpid.server.transport.ServerSessionDelegate.messageTransfer(ServerSessionDelegate.java:96) >> at >> org.apache.qpid.transport.MessageTransfer.dispatch(MessageTransfer.java:108) >> at >> org.apache.qpid.transport.SessionDelegate.command(SessionDelegate.java:50) >> at >> org.apache.qpid.server.transport.ServerSessionDelegate.command(ServerSessionDelegate.java:112) >> at >> org.apache.qpid.server.transport.ServerSessionDelegate.command(ServerSessionDelegate.java:96) >> at org.apache.qpid.transport.Method.delegate(Method.java:159) >> at org.apache.qpid.transport.Session.received(Session.java:500) >> at org.apache.qpid.transport.Connection.dispatch(Connection.java:404) >> at >> org.apache.qpid.transport.ConnectionDelegate.handle(ConnectionDelegate.java:64) >> at >> org.apache.qpid.transport.ConnectionDelegate.handle(ConnectionDelegate.java:40) >> at >> org.apache.qpid.transport.MethodDelegate.messageTransfer(MethodDelegate.java:113) >> at >> org.apache.qpid.transport.MessageTransfer.dispatch(MessageTransfer.java:108) >> at >> org.apache.qpid.transport.ConnectionDelegate.command(ConnectionDelegate.java:54) >> at >> org.apache.qpid.transport.ConnectionDelegate.command(ConnectionDelegate.java:40) >> at org.apache.qpid.transport.Method.delegate(Method.java:159) >> at org.apache.qpid.transport.Connection.received(Connection.java:369) >> at >> org.apache.qpid.server.transport.ServerConnection.received(ServerConnection.java:196) >> at >> org.apache.qpid.server.transport.ServerConnection.received(ServerConnection.java:53) >> at org.apache.qpid.transport.network.Assembler.emit(Assembler.java:95) >> at >> org.apache.qpid.transport.network.Assembler.assemble(Assembler.java:217) >> at org.apache.qpid.transport.network.Assembler.frame(Assembler.java:129) >> at org.apache.qpid.transport.network.Frame.delegate(Frame.java:133) >> at >> org.apache.qpid.transport.network.Assembler.received(Assembler.java:100) >> at org.apache.qpid.transport.network.Assembler.received(Assembler.java:42) >> at >> org.apache.qpid.transport.network.InputHandler.next(InputHandler.java:187) >> at >> org.apache.qpid.transport.network.InputHandler.received(InputHandler.java:103) >> at >> org.apache.qpid.transport.network.InputHandler.received(InputHandler.java:42) >> at >> org.apache.qpid.server.protocol.MultiVersionProtocolEngine.received(MultiVersionProtocolEngin
Re: [Carbon-dev] Events are not getting published in latest packs due to qpid error
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 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. > Please have a look. > > Stacktrace: > > [2011-05-06 17:04:35,518] DEBUG - PublisherUtils Event payload > http://wso2.org/ns/2009/09/bam/server/user-defined/data > "> > https://10.100.0.191:9444 > 0ProxyOutMaxProcessingTime-lafProxy1ProxyOutAvgProcessingTime-lafProxy0.ProxyOutMinProcessingTime-lafProxy0ProxyOutCount-lafProxy27ProxyOutCumulativeCount-lafProxy27ProxyOutFaultCount-lafProxy0ProxyOutIDlafProxy > [2011-05-06 17:04:35,518] DEBUG - BAMMediationStatisticsObserver > ComponentType.PROXYSERVICE http://wso2.org/ns/2009/09/bam/server/user-defined/data > "> > https://10.100.0.191:9444 > 0ProxyOutMaxProcessingTime-lafProxy1ProxyOutAvgProcessingTime-lafProxy0.ProxyOutMinProcessingTime-lafProxy0ProxyOutCount-lafProxy27ProxyOutCumulativeCount-lafProxy27ProxyOutFaultCount-lafProxy0ProxyOutIDlafProxy > [2011-05-06 17:04:35,528] DEBUG - BAMMediationStatisticsObserver Event is > publishedhttp://wso2.org/ns/2009/09/bam/server/user-defined/data > "> > https://10.100.0.191:9444 > 0ProxyOutMaxProcessingTime-lafProxy1ProxyOutAvgProcessingTime-lafProxy0.ProxyOutMinProcessingTime-lafProxy0ProxyOutCount-lafProxy27ProxyOutCumulativeCount-lafProxy27ProxyOutFaultCount-lafProxy0ProxyOutIDlafProxy > [2011-05-06 17:04:35,597] ERROR - DefaultRealmService > java.lang.NullPointerException > at > org.wso2.carbon.user.core.common.DefaultRealmService.getTenantUserRealm(DefaultRealmService.java:157) > at > org.wso2.carbon.qpid.authorization.service.qpid.QpidAuthorizationPlugin.getUserRealm(QpidAuthorizationPlugin.java:184) > at > org.wso2.carbon.qpid.authorization.service.qpid.QpidAuthorizationPlugin.authorise(QpidAuthorizationPlugin.java:124) > at > org.apache.qpid.server.security.SecurityManager$11.allowed(SecurityManager.java:390) > at > org.apache.qpid.server.security.SecurityManager.checkAllPlugins(SecurityManager.java:245) > at > org.apache.qpid.server.security.SecurityManager.authorisePublish(SecurityManager.java:386) > at > org.apache.qpid.server.transport.ServerSessionDelegate.messageTransfer(ServerSessionDelegate.java:307) > at > org.apache.qpid.server.transport.ServerSessionDelegate.messageTransfer(ServerSessionDelegate.java:96) > at > org.apache.qpid.transport.MessageTransfer.dispatch(MessageTransfer.java:108) > at > org.apache.qpid.transport.SessionDelegate.command(SessionDelegate.java:50) > at > org.apache.qpid.server.transport.ServerSessionDelegate.command(ServerSessionDelegate.java:112) > at > org.apache.qpid.server.transport.ServerSessionDelegate.command(ServerSessionDelegate.java:96) > at org.apache.qpid.transport.Method.delegate(Method.java:159) > at org.apache.qpid.transport.Session.received(Session.java:500) > at org.apache.qpid.transport.Connection.dispatch(Connection.java:404) > at > org.apache.qpid.transport.ConnectionDelegate.handle(ConnectionDelegate.java:64) > at > org.apache.qpid.transport.ConnectionDelegate.handle(ConnectionDelegate.java:40) > at > org.apache.qpid.transport.MethodDelegate.messageTransfer(MethodDelegate.java:113) > at > org.apache.qpid.transport.MessageTransfer.dispatch(MessageTransfer.java:108) > at > org.apache.qpid.transport.ConnectionDelegate.command(ConnectionDelegate.java:54) > at > org.apache.qpid.transport.ConnectionDelegate.command(ConnectionDelegate.java:40) > at org.apache.qpid.transport.Method.delegate(Method.java:159) > at org.apache.qpid.transport.Connection.received(Connection.java:369) > at > org.apache.qpid.server.transport.ServerConnection.received(ServerConnection.java:196) > at > org.apache.qpid.server.transport.ServerConnection.received(ServerConnection.java:53) > at org.apache.qpid.transport.network.Assembler.emit(Assembler.java:95) > at org.apache.qpid.transport.network.Assembler.assemble(Assembler.java:217) > at org.apache.qpid.transport.network.Assembler.frame(Assembler.java:129) > at org.apache.qpid.transport.network.Frame.delegate(Frame.java:133) > at > org.apache.qpid.transport.network.Assembler.received(Assembler.java:100) > at org.apache.qpid.transport.network.Assembler.received(Assembler.java:42) > at > org.apache.qpid.transport.network.InputHandler.next(InputHandler.java:187) > at > org.apache.qpid.transport.network.InputHandler.received(InputHandler.java:103) > at > org.apache.qpid.transport.network.InputHandler.received(InputHandler.java:42) > at > org.apache.qpid.server.protocol.MultiVersionProtocolEngine.received(MultiVersionProtocolEngine.java:102) > at > org.apache.qpid.server.protocol.MultiVersionProtocolEngine.received(MultiVersionProtocolEngine.java:36) > at > org.apache.qpid.transport.network.mina.MINANetworkDriver.messageReceived(MINANetworkDriver.java:337
Re: [Carbon-dev] Events are not getting published in latest packs due to 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 wrote: > Tharindu, please do whatever it takes to get a BAM pack ready today. > > On Fri, May 6, 2011 at 5:18 PM, Tharindu Mathew 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. >> Please have a look. >> >> Stacktrace: >> >> [2011-05-06 17:04:35,518] DEBUG - PublisherUtils Event payload >> http://wso2.org/ns/2009/09/bam/server/user-defined/data >> "> >> https://10.100.0.191:9444 >> 0ProxyOutMaxProcessingTime-lafProxy1ProxyOutAvgProcessingTime-lafProxy0.ProxyOutMinProcessingTime-lafProxy0ProxyOutCount-lafProxy27ProxyOutCumulativeCount-lafProxy27ProxyOutFaultCount-lafProxy0ProxyOutIDlafProxy >> [2011-05-06 17:04:35,518] DEBUG - BAMMediationStatisticsObserver >> ComponentType.PROXYSERVICE http://wso2.org/ns/2009/09/bam/server/user-defined/data >> "> >> https://10.100.0.191:9444 >> 0ProxyOutMaxProcessingTime-lafProxy1ProxyOutAvgProcessingTime-lafProxy0.ProxyOutMinProcessingTime-lafProxy0ProxyOutCount-lafProxy27ProxyOutCumulativeCount-lafProxy27ProxyOutFaultCount-lafProxy0ProxyOutIDlafProxy >> [2011-05-06 17:04:35,528] DEBUG - BAMMediationStatisticsObserver Event is >> publishedhttp://wso2.org/ns/2009/09/bam/server/user-defined/data >> "> >> https://10.100.0.191:9444 >> 0ProxyOutMaxProcessingTime-lafProxy1ProxyOutAvgProcessingTime-lafProxy0.ProxyOutMinProcessingTime-lafProxy0ProxyOutCount-lafProxy27ProxyOutCumulativeCount-lafProxy27ProxyOutFaultCount-lafProxy0ProxyOutIDlafProxy >> [2011-05-06 17:04:35,597] ERROR - DefaultRealmService >> java.lang.NullPointerException >> at >> org.wso2.carbon.user.core.common.DefaultRealmService.getTenantUserRealm(DefaultRealmService.java:157) >> at >> org.wso2.carbon.qpid.authorization.service.qpid.QpidAuthorizationPlugin.getUserRealm(QpidAuthorizationPlugin.java:184) >> at >> org.wso2.carbon.qpid.authorization.service.qpid.QpidAuthorizationPlugin.authorise(QpidAuthorizationPlugin.java:124) >> at >> org.apache.qpid.server.security.SecurityManager$11.allowed(SecurityManager.java:390) >> at >> org.apache.qpid.server.security.SecurityManager.checkAllPlugins(SecurityManager.java:245) >> at >> org.apache.qpid.server.security.SecurityManager.authorisePublish(SecurityManager.java:386) >> at >> org.apache.qpid.server.transport.ServerSessionDelegate.messageTransfer(ServerSessionDelegate.java:307) >> at >> org.apache.qpid.server.transport.ServerSessionDelegate.messageTransfer(ServerSessionDelegate.java:96) >> at >> org.apache.qpid.transport.MessageTransfer.dispatch(MessageTransfer.java:108) >> at >> org.apache.qpid.transport.SessionDelegate.command(SessionDelegate.java:50) >> at >> org.apache.qpid.server.transport.ServerSessionDelegate.command(ServerSessionDelegate.java:112) >> at >> org.apache.qpid.server.transport.ServerSessionDelegate.command(ServerSessionDelegate.java:96) >> at org.apache.qpid.transport.Method.delegate(Method.java:159) >> at org.apache.qpid.transport.Session.received(Session.java:500) >> at org.apache.qpid.transport.Connection.dispatch(Connection.java:404) >> at >> org.apache.qpid.transport.ConnectionDelegate.handle(ConnectionDelegate.java:64) >> at >> org.apache.qpid.transport.ConnectionDelegate.handle(ConnectionDelegate.java:40) >> at >> org.apache.qpid.transport.MethodDelegate.messageTransfer(MethodDelegate.java:113) >> at >> org.apache.qpid.transport.MessageTransfer.dispatch(MessageTransfer.java:108) >> at >> org.apache.qpid.transport.ConnectionDelegate.command(ConnectionDelegate.java:54) >> at >> org.apache.qpid.transport.ConnectionDelegate.command(ConnectionDelegate.java:40) >> at org.apache.qpid.transport.Method.delegate(Method.java:159) >> at org.apache.qpid.transport.Connection.received(Connection.java:369) >> at >> org.apache.qpid.server.transport.ServerConnection.received(ServerConnection.java:196) >> at >> org.apache.qpid.server.transport.ServerConnection.received(ServerConnection.java:53) >> at org.apache.qpid.transport.network.Assembler.emit(Assembler.java:95) >> at >> org.apache.qpid.transport.network.Assembler.assemble(Assembler.java:217) >> at org.apache.qpid.transport.network.Assembler.frame(Assembler.java:129) >> at org.apache.qpid.transport.network.Frame.delegate(Frame.java:133) >> at >> org.apache.qpid.transport.network.Assembler.received(Assembler.java:100) >> at org.apache.qpid.transport.network.Assembler.received(Assembler.java:42) >> at >> org.apache.qpid.transport.network.InputHandler.next(InputHandler.java:187) >> at >> org.apache.qpid.transport.network.InputHandler.received(InputHandler.java:103) >> at >> org.apache.qpid.transport.network.InputHandler.received(InputHan
Re: [Carbon-dev] Events are not getting published in latest packs due to 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 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. > Please have a look. > > Stacktrace: > > [2011-05-06 17:04:35,518] DEBUG - PublisherUtils Event payload > http://wso2.org/ns/2009/09/bam/server/user-defined/data > "> > https://10.100.0.191:9444 > 0ProxyOutMaxProcessingTime-lafProxy1ProxyOutAvgProcessingTime-lafProxy0.ProxyOutMinProcessingTime-lafProxy0ProxyOutCount-lafProxy27ProxyOutCumulativeCount-lafProxy27ProxyOutFaultCount-lafProxy0ProxyOutIDlafProxy > [2011-05-06 17:04:35,518] DEBUG - BAMMediationStatisticsObserver > ComponentType.PROXYSERVICE http://wso2.org/ns/2009/09/bam/server/user-defined/data > "> > https://10.100.0.191:9444 > 0ProxyOutMaxProcessingTime-lafProxy1ProxyOutAvgProcessingTime-lafProxy0.ProxyOutMinProcessingTime-lafProxy0ProxyOutCount-lafProxy27ProxyOutCumulativeCount-lafProxy27ProxyOutFaultCount-lafProxy0ProxyOutIDlafProxy > [2011-05-06 17:04:35,528] DEBUG - BAMMediationStatisticsObserver Event is > publishedhttp://wso2.org/ns/2009/09/bam/server/user-defined/data > "> > https://10.100.0.191:9444 > 0ProxyOutMaxProcessingTime-lafProxy1ProxyOutAvgProcessingTime-lafProxy0.ProxyOutMinProcessingTime-lafProxy0ProxyOutCount-lafProxy27ProxyOutCumulativeCount-lafProxy27ProxyOutFaultCount-lafProxy0ProxyOutIDlafProxy > [2011-05-06 17:04:35,597] ERROR - DefaultRealmService > java.lang.NullPointerException > at > org.wso2.carbon.user.core.common.DefaultRealmService.getTenantUserRealm(DefaultRealmService.java:157) > at > org.wso2.carbon.qpid.authorization.service.qpid.QpidAuthorizationPlugin.getUserRealm(QpidAuthorizationPlugin.java:184) > at > org.wso2.carbon.qpid.authorization.service.qpid.QpidAuthorizationPlugin.authorise(QpidAuthorizationPlugin.java:124) > at > org.apache.qpid.server.security.SecurityManager$11.allowed(SecurityManager.java:390) > at > org.apache.qpid.server.security.SecurityManager.checkAllPlugins(SecurityManager.java:245) > at > org.apache.qpid.server.security.SecurityManager.authorisePublish(SecurityManager.java:386) > at > org.apache.qpid.server.transport.ServerSessionDelegate.messageTransfer(ServerSessionDelegate.java:307) > at > org.apache.qpid.server.transport.ServerSessionDelegate.messageTransfer(ServerSessionDelegate.java:96) > at > org.apache.qpid.transport.MessageTransfer.dispatch(MessageTransfer.java:108) > at > org.apache.qpid.transport.SessionDelegate.command(SessionDelegate.java:50) > at > org.apache.qpid.server.transport.ServerSessionDelegate.command(ServerSessionDelegate.java:112) > at > org.apache.qpid.server.transport.ServerSessionDelegate.command(ServerSessionDelegate.java:96) > at org.apache.qpid.transport.Method.delegate(Method.java:159) > at org.apache.qpid.transport.Session.received(Session.java:500) > at org.apache.qpid.transport.Connection.dispatch(Connection.java:404) > at > org.apache.qpid.transport.ConnectionDelegate.handle(ConnectionDelegate.java:64) > at > org.apache.qpid.transport.ConnectionDelegate.handle(ConnectionDelegate.java:40) > at > org.apache.qpid.transport.MethodDelegate.messageTransfer(MethodDelegate.java:113) > at > org.apache.qpid.transport.MessageTransfer.dispatch(MessageTransfer.java:108) > at > org.apache.qpid.transport.ConnectionDelegate.command(ConnectionDelegate.java:54) > at > org.apache.qpid.transport.ConnectionDelegate.command(ConnectionDelegate.java:40) > at org.apache.qpid.transport.Method.delegate(Method.java:159) > at org.apache.qpid.transport.Connection.received(Connection.java:369) > at > org.apache.qpid.server.transport.ServerConnection.received(ServerConnection.java:196) > at > org.apache.qpid.server.transport.ServerConnection.received(ServerConnection.java:53) > at org.apache.qpid.transport.network.Assembler.emit(Assembler.java:95) > at org.apache.qpid.transport.network.Assembler.assemble(Assembler.java:217) > at org.apache.qpid.transport.network.Assembler.frame(Assembler.java:129) > at org.apache.qpid.transport.network.Frame.delegate(Frame.java:133) > at > org.apache.qpid.transport.network.Assembler.received(Assembler.java:100) > at org.apache.qpid.transport.network.Assembler.received(Assembler.java:42) > at > org.apache.qpid.transport.network.InputHandler.next(InputHandler.java:187) > at > org.apache.qpid.transport.network.InputHandler.received(InputHandler.java:103) > at > org.apache.qpid.transport.network.InputHandler.received(InputHandler.java:42) > at > org.apache.qpid.server.protocol.MultiVersionProtocolEngine.received(MultiVersionProtocolEngine.java:102) > at > org.apache.qpid.server.protocol.MultiVersionProtocolEngine.received(MultiVersionProtocolEngine.java:36) > at > org.apache.qpid.transport.network.mina.MINANetworkDriver.messageReceived(MINANetworkDriver.java:337) > at > org.apache.mina.common.support.Abstr
Re: [Carbon-dev] Events are not getting published in latest packs due to qpid error
AmilaJ fixed the issue in DefaultRealmService as I heard. Danushka On Fri, May 6, 2011 at 5:18 PM, Tharindu Mathew 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. > Please have a look. > > Stacktrace: > > [2011-05-06 17:04:35,518] DEBUG - PublisherUtils Event payload > http://wso2.org/ns/2009/09/bam/server/user-defined/data > "> > https://10.100.0.191:9444 > 0ProxyOutMaxProcessingTime-lafProxy1ProxyOutAvgProcessingTime-lafProxy0.ProxyOutMinProcessingTime-lafProxy0ProxyOutCount-lafProxy27ProxyOutCumulativeCount-lafProxy27ProxyOutFaultCount-lafProxy0ProxyOutIDlafProxy > [2011-05-06 17:04:35,518] DEBUG - BAMMediationStatisticsObserver > ComponentType.PROXYSERVICE http://wso2.org/ns/2009/09/bam/server/user-defined/data > "> > https://10.100.0.191:9444 > 0ProxyOutMaxProcessingTime-lafProxy1ProxyOutAvgProcessingTime-lafProxy0.ProxyOutMinProcessingTime-lafProxy0ProxyOutCount-lafProxy27ProxyOutCumulativeCount-lafProxy27ProxyOutFaultCount-lafProxy0ProxyOutIDlafProxy > [2011-05-06 17:04:35,528] DEBUG - BAMMediationStatisticsObserver Event is > publishedhttp://wso2.org/ns/2009/09/bam/server/user-defined/data > "> > https://10.100.0.191:9444 > 0ProxyOutMaxProcessingTime-lafProxy1ProxyOutAvgProcessingTime-lafProxy0.ProxyOutMinProcessingTime-lafProxy0ProxyOutCount-lafProxy27ProxyOutCumulativeCount-lafProxy27ProxyOutFaultCount-lafProxy0ProxyOutIDlafProxy > [2011-05-06 17:04:35,597] ERROR - DefaultRealmService > java.lang.NullPointerException > at > org.wso2.carbon.user.core.common.DefaultRealmService.getTenantUserRealm(DefaultRealmService.java:157) > at > org.wso2.carbon.qpid.authorization.service.qpid.QpidAuthorizationPlugin.getUserRealm(QpidAuthorizationPlugin.java:184) > at > org.wso2.carbon.qpid.authorization.service.qpid.QpidAuthorizationPlugin.authorise(QpidAuthorizationPlugin.java:124) > at > org.apache.qpid.server.security.SecurityManager$11.allowed(SecurityManager.java:390) > at > org.apache.qpid.server.security.SecurityManager.checkAllPlugins(SecurityManager.java:245) > at > org.apache.qpid.server.security.SecurityManager.authorisePublish(SecurityManager.java:386) > at > org.apache.qpid.server.transport.ServerSessionDelegate.messageTransfer(ServerSessionDelegate.java:307) > at > org.apache.qpid.server.transport.ServerSessionDelegate.messageTransfer(ServerSessionDelegate.java:96) > at > org.apache.qpid.transport.MessageTransfer.dispatch(MessageTransfer.java:108) > at > org.apache.qpid.transport.SessionDelegate.command(SessionDelegate.java:50) > at > org.apache.qpid.server.transport.ServerSessionDelegate.command(ServerSessionDelegate.java:112) > at > org.apache.qpid.server.transport.ServerSessionDelegate.command(ServerSessionDelegate.java:96) > at org.apache.qpid.transport.Method.delegate(Method.java:159) > at org.apache.qpid.transport.Session.received(Session.java:500) > at org.apache.qpid.transport.Connection.dispatch(Connection.java:404) > at > org.apache.qpid.transport.ConnectionDelegate.handle(ConnectionDelegate.java:64) > at > org.apache.qpid.transport.ConnectionDelegate.handle(ConnectionDelegate.java:40) > at > org.apache.qpid.transport.MethodDelegate.messageTransfer(MethodDelegate.java:113) > at > org.apache.qpid.transport.MessageTransfer.dispatch(MessageTransfer.java:108) > at > org.apache.qpid.transport.ConnectionDelegate.command(ConnectionDelegate.java:54) > at > org.apache.qpid.transport.ConnectionDelegate.command(ConnectionDelegate.java:40) > at org.apache.qpid.transport.Method.delegate(Method.java:159) > at org.apache.qpid.transport.Connection.received(Connection.java:369) > at > org.apache.qpid.server.transport.ServerConnection.received(ServerConnection.java:196) > at > org.apache.qpid.server.transport.ServerConnection.received(ServerConnection.java:53) > at org.apache.qpid.transport.network.Assembler.emit(Assembler.java:95) > at org.apache.qpid.transport.network.Assembler.assemble(Assembler.java:217) > at org.apache.qpid.transport.network.Assembler.frame(Assembler.java:129) > at org.apache.qpid.transport.network.Frame.delegate(Frame.java:133) > at > org.apache.qpid.transport.network.Assembler.received(Assembler.java:100) > at org.apache.qpid.transport.network.Assembler.received(Assembler.java:42) > at > org.apache.qpid.transport.network.InputHandler.next(InputHandler.java:187) > at > org.apache.qpid.transport.network.InputHandler.received(InputHandler.java:103) > at > org.apache.qpid.transport.network.InputHandler.received(InputHandler.java:42) > at > org.apache.qpid.server.protocol.MultiVersionProtocolEngine.received(MultiVersionProtocolEngine.java:102) > at > org.apache.qpid.server.protocol.MultiVersionProtocolEngine.received(MultiVersionProtocolEngine.java:36) > at > org.apache.qpid.transport.network.mina.MINANetworkDriver.messageReceived(MINANetworkDriver.java:337) > at > org.apache.mina.common.support.Abstra
