OK, this is the second bug we are finding running the samples. This time it is EIP, but that too falls under "try them out" samples.
We really got to get the integration tests going. Thanks, Samisa... Samisa Abeysinghe Vice President Training WSO2 Inc. http://wso2.com On Thu, Dec 12, 2013 at 6:34 AM, Miyuru Wanninayaka <[email protected]> wrote: > Seems eventing component does not properly sets thread local CC. > > > On Thu, Dec 12, 2013 at 6:15 AM, Chanaka Fernando <[email protected]>wrote: > >> Looks like this is a bug in the ESB 4.8.0. PrabathS has also reported the >> same issue in the support dev mailing list. >> I got the same results when I tried this sample. There was a similar >> issue reported [1] and it was fixed. But In this case, no clustering >> involved. >> >> https://wso2.org/jira/browse/CARBON-14299 >> >> Looping in carbon team. >> >> Thanks, >> Chanaka >> >> >> >> >> On Wed, Dec 11, 2013 at 4:22 AM, Vimuth Fernando <[email protected]> wrote: >> >>> I tried to run the Publish-Subscribe Chanel scenario in the EIP guide ( >>> http://docs.wso2.org/display/IntegrationPatterns/Publish-Subscribe+Channel >>> ). >>> As it says in the guide, i added a new Topic and subscribed with the >>> urls of the two server instances.But I am getting the following exception >>> at the ESB when i try to run the client. >>> >>> [2013-12-11 14:30:08,656] ERROR - DefaultRealmService Tenant domain has >>> not been set in CarbonContext >>> java.lang.NullPointerException: Tenant domain has not been set in >>> CarbonContext >>> at >>> org.wso2.carbon.caching.impl.CacheManagerFactoryImpl.getCacheManager(CacheManagerFactoryImpl.java:79) >>> at >>> org.wso2.carbon.user.core.tenant.TenantCache.getTenantCache(TenantCache.java:39) >>> at >>> org.wso2.carbon.user.core.tenant.TenantCache.getValueFromCache(TenantCache.java:77) >>> at >>> org.wso2.carbon.user.core.tenant.JDBCTenantManager.getTenant(JDBCTenantManager.java:224) >>> at >>> org.wso2.carbon.user.core.tenant.JDBCTenantManager.getTenant(JDBCTenantManager.java:54) >>> at >>> org.wso2.carbon.user.core.common.DefaultRealmService.getTenantUserRealm(DefaultRealmService.java:159) >>> at >>> org.wso2.carbon.event.core.internal.delivery.inmemory.InMemoryDeliveryManager.publish(InMemoryDeliveryManager.java:87) >>> at >>> org.wso2.carbon.event.core.internal.EventPublisher.run(EventPublisher.java:56) >>> at >>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) >>> at >>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) >>> at java.lang.Thread.run(Thread.java:744) >>> [2013-12-11 14:30:08,657] ERROR - EventPublisher Can not publish the >>> message >>> org.wso2.carbon.event.core.exception.EventBrokerException: Can not >>> access the user store manager >>> at >>> org.wso2.carbon.event.core.internal.delivery.inmemory.InMemoryDeliveryManager.publish(InMemoryDeliveryManager.java:109) >>> at >>> org.wso2.carbon.event.core.internal.EventPublisher.run(EventPublisher.java:56) >>> at >>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) >>> at >>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) >>> at java.lang.Thread.run(Thread.java:744) >>> >>> >>> Thanks, >>> Vimuth >>> >>> >>> >>> _______________________________________________ >>> Dev mailing list >>> [email protected] >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> -- >> Chanaka Fernando >> Technical Lead >> WSO2, Inc.; http://wso2.com >> lean.enterprise.middleware >> >> mobile: +94 773337238 >> Blog : http://soatutorials.blogspot.com >> LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0 >> Twitter:https://twitter.com/chanakaudaya >> Wordpress:http://chanakaudaya.wordpress.com >> >> >> >> > > > -- > Miyuru Wanninayaka > Technical Lead > WSO2 Inc. : http://wso2.com > > Mobile : +94 77 209 9788 > Blog : http://miyurudw.blogspot.com > Flickr : http://www.flickr.com/photos/miyuru_daminda >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
