WSO2 API manager claims cache -
i've switched using wso2 api manager version 1.9 1.8, looks good, except i'm getting exception when trying populate claims in jwt token.
java.lang.illegalstateexception: cache status not started @ org.wso2.carbon.caching.impl.cacheimpl.checkstatusstarted(cacheimpl.java:287) @ org.wso2.carbon.caching.impl.cacheimpl.get(cacheimpl.java:171) @ org.wso2.carbon.apimgt.impl.token.defaultclaimsretriever.getclaims(defaultclaimsretriever.java:82) @ org.wso2.carbon.apimgt.impl.token.jwtgenerator.populatecustomclaims(jwtgenerator.java:92) @ org.wso2.carbon.apimgt.impl.token.abstractjwtgenerator.buildbody(abstractjwtgenerator.java:185) @ org.wso2.carbon.apimgt.impl.token.abstractjwtgenerator.generatetoken(abstractjwtgenerator.java:141) @ org.wso2.carbon.apimgt.keymgt.handlers.abstractkeyvalidationhandler.generateconsumertoken(abstractkeyvalidationhandler.java:146) @ org.wso2.carbon.apimgt.keymgt.service.apikeyvalidationservice.validatekey(apikeyvalidationservice.java:169) @ org.wso2.carbon.apimgt.keymgt.service.thrift.apikeyvalidationserviceimpl.validatekey(apikeyvalidationserviceimpl.java:131) @ org.wso2.carbon.apimgt.impl.generated.thrift.apikeyvalidationservice$processor$validatekey.getresult(apikeyvalidationservice.java:278) @ org.wso2.carbon.apimgt.impl.generated.thrift.apikeyvalidationservice$processor$validatekey.getresult(apikeyvalidationservice.java:266) @ org.apache.thrift.processfunction.process(processfunction.java:32) @ org.apache.thrift.tbaseprocessor.process(tbaseprocessor.java:34) @ org.apache.thrift.server.tthreadpoolserver$workerprocess.run(tthreadpoolserver.java:176) @ java.util.concurrent.threadpoolexecutor.runworker(threadpoolexecutor.java:1145) @ java.util.concurrent.threadpoolexecutor$worker.run(threadpoolexecutor.java:615) @ java.lang.thread.run(thread.java:745)
this seems similar bug https://wso2.org/jira/browse/appm-958 on app manager, doesn't seem have been ported api manager.
is there workaround, or can configure?
thanks
edit: bug on 1.5 of api manager looks similar. https://wso2.org/jira/browse/apimanager-1504
it bug [1] in api manager 1.9.0 , fixed next version. if customer of wso2, can patch issue them.
Comments
Post a Comment