on 06-23-2016 7:30 PM
It is obvious, that you need to initialize tenant, but it is not always clear which of them.
I was faced with this exception when I worked with Spring Integration Framework. Some of its executors automatically run within each tenant's Spring context. In my case it was both master and junit tenants. The master was initialized, but junit was not and threw exception all the time.
Quick decision was just initialize junit tenant. The final decision was to rewrite Spring's automated -executors by Hybris CronJobs.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
5 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.