Unable to sync QVDs after December upgrade

[lachlanwwells]

Hi there,

After getting it up and running on the initial September release for QDC, we thought we'd upgrade to December to take a look at the differences/ability to delete datasets.

Everything goes smoothly, more or less the same as the September release, however we aren't able to sync/update any QVD metadata.

We have also started the installation again from scratch (on a new server) and experience the same issue.

Our logs report as followed:

2020-01-17 08:17:55,699 ERROR Terminating exception [QvdMetadataSyncManagerImpl[Podium-task-7-connector-1-qvd-sync]]
com.podiumdata.base.error.PodiumFault: core.error.code.QS_CONNECTION_FAILED - Could not fetch data from QS due to issues with connection for connector Id:1, name:DEV.
at com.nvs.core.service.impl.QSRestClientSvcImpl.getApps(QSRestClientSvcImpl.java:185)
at com.nvs.core.service.impl.QSConnectorInfoSvcImpl.getAppForConnector(QSConnectorInfoSvcImpl.java:168)
at com.nvs.core.service.impl.QvdMetadataSyncManagerImpl.sync(QvdMetadataSyncManagerImpl.java:108)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:333)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:190)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157)
at org.springframework.aop.framework.adapter.AfterReturningAdviceInterceptor.invoke(AfterReturningAdviceInterceptor.java:52)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
at org.springframework.transaction.interceptor.TransactionInterceptor$1.proceedWithInvocation(TransactionInterceptor.java:99)
at org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:281)
at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:96)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:92)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:213)
at com.sun.proxy.$Proxy263.sync(Unknown Source)
at com.nvs.ui.service.impl.QSConnectorServiceImpl.syncInternal(QSConnectorServiceImpl.java:229)
at com.nvs.ui.service.impl.QSConnectorServiceImpl.access$000(QSConnectorServiceImpl.java:58)
at com.nvs.ui.service.impl.QSConnectorServiceImpl$1.run(QSConnectorServiceImpl.java:214)
at com.nvs.core.service.impl.ThreadingSvcImpl$CallableAdapterForRunnable.call(ThreadingSvcImpl.java:319)
at com.nvs.core.service.impl.ThreadingSvcImpl$CallableAdapterForRunnable.call(ThreadingSvcImpl.java:309)
at com.nvs.core.service.impl.ThreadingSvcImpl$DecoratedCallable.callWithTimingAndLogging(ThreadingSvcImpl.java:391)
at com.nvs.core.service.impl.ThreadingSvcImpl$DecoratedCallable.callWithGarbageCollectionAndCounting(ThreadingSvcImpl.java:369)
at com.nvs.core.service.impl.ThreadingSvcImpl$DecoratedCallable.call(ThreadingSvcImpl.java:354)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
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)
Caused by: com.fasterxml.jackson.databind.JsonMappingException: Can not deserialize instance of java.lang.String out of START_OBJECT token
at [Source: java.io.StringReader@210ca3d8; line: 1, column: 120038] (through reference chain: java.util.HashSet[135]->com.nvs.core.model.QSAppInfo["customProperties"]->java.lang.Object[][0])
at com.fasterxml.jackson.databind.JsonMappingException.from(JsonMappingException.java:270)
at com.fasterxml.jackson.databind.DeserializationContext.reportMappingException(DeserializationContext.java:1234)
at com.fasterxml.jackson.databind.DeserializationContext.handleUnexpectedToken(DeserializationContext.java:1122)
at com.fasterxml.jackson.databind.DeserializationContext.handleUnexpectedToken(DeserializationContext.java:1075)
at com.fasterxml.jackson.databind.deser.std.StdDeserializer._parseString(StdDeserializer.java:863)
at com.fasterxml.jackson.databind.deser.std.StringArrayDeserializer.deserialize(StringArrayDeserializer.java:106)
at com.fasterxml.jackson.databind.deser.std.StringArrayDeserializer.deserialize(StringArrayDeserializer.java:18)
at com.fasterxml.jackson.databind.deser.SettableBeanProperty.deserialize(SettableBeanProperty.java:499)
at com.fasterxml.jackson.databind.deser.impl.MethodProperty.deserializeAndSet(MethodProperty.java:101)
at com.fasterxml.jackson.databind.deser.BeanDeserializer.vanillaDeserialize(BeanDeserializer.java:276)
at com.fasterxml.jackson.databind.deser.BeanDeserializer.deserialize(BeanDeserializer.java:140)
at com.fasterxml.jackson.databind.deser.std.CollectionDeserializer.deserialize(CollectionDeserializer.java:287)
at com.fasterxml.jackson.databind.deser.std.CollectionDeserializer.deserialize(CollectionDeserializer.java:259)
at com.fasterxml.jackson.databind.deser.std.CollectionDeserializer.deserialize(CollectionDeserializer.java:26)
at com.fasterxml.jackson.databind.ObjectMapper._readMapAndClose(ObjectMapper.java:3798)
at com.fasterxml.jackson.databind.ObjectMapper.readValue(ObjectMapper.java:2861)
at com.nvs.core.service.impl.QSRestClientSvcImpl.getApps(QSRestClientSvcImpl.java:179)
... 31 more

AWS - CentOS 7 1901_01 - Java openjdk 1.8.0-232

Any thoughts?

Thanks,

Lachlan

[lachlanwwells]

Good news and bad news!

Happy to report the loading from Qlik is working fine now, but now whenever we add any entity metadata (i.e. business name) to a QVD with a space in the name, it is replaced with a unicode representation....