Should this code change be enough to fix our problem since we use Andes Release 3,2,82 and not the latest release ?
This is the call stack that we are getting:
@timestamp August 14th 2019, 14:36:37.100
t @version 1
t _id l-prkWwBy3L127wNCMzB
t _index rq-wso2-2019.08.14
_score -
t _type doc
t beat.hostname SFUCO4170
t beat.name SFUCO4170
t beat.version 6.8.0
t client wso2
t host.name SFUCO4170
t level ERROR
? log.file.path /var/log/wso2ei/message-broker/wso2carbon.log
? log.flags multiline
t logger-name org.wso2.andes.kernel.subscription.AndesSubscriptionManager
t message Could not add subscription: subscriptionId=cc1cb030-de11-4cec-853a-ff283f914995,storageQueue=carbon:biztalkname6,protocolType=AMQP,isActive=true,subscriberConnection=Y29ubmVjdGVkSVA9LzE3Mi4zMC4xNTIuMzI6MTQ2MTYvMSxjb25uZWN0ZWROb2RlPVNGVUNPNDE2OS5wcm9kLm1ycSxwcm90b2NvbENoYW5uZWxJRD1iZDEzOWJmNS1iYTgxLTQyNWEtYmFjYi1lMTA1ZmU2MDM3OWU=
offset 1,541,508
t source /var/log/wso2ei/message-broker/wso2carbon.log
t stacktrace org.wso2.andes.kernel.subscription.SubscriptionException: StorageQueue: carbon:biztalkname6
is not registered while creating subscription id=cc1cb030-de11-4cec-853a-ff283f914995
at org.wso2.andes.kernel.subscription.AndesSubscription.(AndesSubscription.java:136)
at org.wso2.andes.kernel.subscription.AndesSubscriptionManager.reloadSubscriptionsFromStorage(AndesSubscriptionManager.java:1065)
at org.wso2.andes.kernel.disruptor.inbound.InboundDBSyncRequestEvent.reloadSubscriptions(InboundDBSyncRequestEvent.java:208)
at org.wso2.andes.kernel.disruptor.inbound.InboundDBSyncRequestEvent.updateState(InboundDBSyncRequestEvent.java:76)
at org.wso2.andes.kernel.disruptor.inbound.InboundEventContainer.updateState(InboundEventContainer.java:268)
at org.wso2.andes.kernel.disruptor.inbound.StateEventHandler.onEvent(StateEventHandler.java:70)
at org.wso2.andes.kernel.disruptor.inbound.StateEventHandler.onEvent(StateEventHandler.java:40)
at com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:128)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
t tags beats_input_codec_plain_applied
Do you think that the patch should fix that issue too ?
Which other changes made to Andes since September 17 2018 would be required for your fix to work with our setup ?
If we upgrade Andes to the latest release, will il require upgrading the whole WSO2 too ? We currently use WSO2 6.4
Related Issues: Similar exception to issue https://github.com/wso2/product-ei/issues/4415 ...but with DURABLE subscriptions instead of NON Durable as in the other reported issue.
Should this code change be enough to fix our problem since we use Andes Release 3,2,82 and not the latest release ?
This is the call stack that we are getting:
t @version 1 t _id l-prkWwBy3L127wNCMzB t _index rq-wso2-2019.08.14
_score -
t _type doc t beat.hostname SFUCO4170 t beat.name SFUCO4170 t beat.version 6.8.0 t client wso2 t host.name SFUCO4170 t level ERROR ? log.file.path /var/log/wso2ei/message-broker/wso2carbon.log ? log.flags multiline t logger-name org.wso2.andes.kernel.subscription.AndesSubscriptionManager t message Could not add subscription: subscriptionId=cc1cb030-de11-4cec-853a-ff283f914995,storageQueue=carbon:biztalkname6,protocolType=AMQP,isActive=true,subscriberConnection=Y29ubmVjdGVkSVA9LzE3Mi4zMC4xNTIuMzI6MTQ2MTYvMSxjb25uZWN0ZWROb2RlPVNGVUNPNDE2OS5wcm9kLm1ycSxwcm90b2NvbENoYW5uZWxJRD1iZDEzOWJmNS1iYTgxLTQyNWEtYmFjYi1lMTA1ZmU2MDM3OWU=
offset 1,541,508
t source /var/log/wso2ei/message-broker/wso2carbon.log t stacktrace org.wso2.andes.kernel.subscription.SubscriptionException: StorageQueue: carbon:biztalkname6 is not registered while creating subscription id=cc1cb030-de11-4cec-853a-ff283f914995 at org.wso2.andes.kernel.subscription.AndesSubscription.(AndesSubscription.java:136)
at org.wso2.andes.kernel.subscription.AndesSubscriptionManager.reloadSubscriptionsFromStorage(AndesSubscriptionManager.java:1065)
at org.wso2.andes.kernel.disruptor.inbound.InboundDBSyncRequestEvent.reloadSubscriptions(InboundDBSyncRequestEvent.java:208)
at org.wso2.andes.kernel.disruptor.inbound.InboundDBSyncRequestEvent.updateState(InboundDBSyncRequestEvent.java:76)
at org.wso2.andes.kernel.disruptor.inbound.InboundEventContainer.updateState(InboundEventContainer.java:268)
at org.wso2.andes.kernel.disruptor.inbound.StateEventHandler.onEvent(StateEventHandler.java:70)
at org.wso2.andes.kernel.disruptor.inbound.StateEventHandler.onEvent(StateEventHandler.java:40)
at com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:128)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
t tags beats_input_codec_plain_applied
Do you think that the patch should fix that issue too ?
Which other changes made to Andes since September 17 2018 would be required for your fix to work with our setup ?
If we upgrade Andes to the latest release, will il require upgrading the whole WSO2 too ? We currently use WSO2 6.4
Thanks