UCF broker reports no advertised connectors

[Daniel Blanco]

Hello, So I noticed that SOI stopped clearing alerts from SOI to other domain managers. Upon investigating in the SOI\tomcat\logs\catalyst.log file we are seeing:

2016-09-07 16:59:52,490 WARN [FailedSyncProcessor Thread] () ucf.UCFFacadeImpl.replaceMdrListCache(307) - Broker appears to be down: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character '2' (code 50) in prolog; expected '<'
at [row,col {unknown-source}]: [1,1]
2016-09-07 16:59:52,490 WARN [FailedSyncProcessor Thread] () ucf.UCFFacadeImpl.replaceMdrListCache(313) - UCF broker reports no advertised connectors
2016-09-07 16:59:52,490 DEBUG [FailedSyncProcessor Thread] () ucf.UCFFacadeImpl.getMdrList(222) - No connectors found
2016-09-07 16:59:52,490 DEBUG [FailedSyncProcessor Thread] () ucf.UCFFacadeImpl.getMdrList(276) - Returning mdr's: 0

Have a case going and will post steps on how to fix....

[Daniel Blanco]

Ok upon investigating this, turns out somehow my SOI UCF Broker got corrupted. Working with support to fix this. When I learn how to will post steps...

corrupt ucf broker

2016-09-07 16:59:51,091 DEBUG [UnplannedShutdownCleanupHelperThread] () impl.SessionImpl.close(122) - 101 - closed
2016-09-07 16:59:52,490 WARN [FailedSyncProcessor Thread] () ucf.UCFFacadeImpl.replaceMdrListCache(307) - Broker appears to be down: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character '2' (code 50) in prolog; expected '<'
at [row,col {unknown-source}]: [1,1]
2016-09-07 16:59:52,490 WARN [FailedSyncProcessor Thread] () ucf.UCFFacadeImpl.replaceMdrListCache(313) - UCF broker reports no advertised connectors
2016-09-07 16:59:52,490 DEBUG [FailedSyncProcessor Thread] () ucf.UCFFacadeImpl.getMdrList(222) - No connectors found
2016-09-07 16:59:52,490 DEBUG [FailedSyncProcessor Thread] () ucf.UCFFacadeImpl.getMdrList(276) - Returning mdr's: 0
2016-09-07 16:59:52,490 DEBUG [FailedSyncProcessor Thread] () executor.AMQEventStoreHandlerImpl.getBackedUpMdrs(124) - BackedUpMdr List :
2016-09-07 17:00:42,942 DEBUG [ConnectionManager init] () impl.SessionImpl.beginTransaction(95) SOI - 154 - beginning transaction
2016-09-07 17:00:42,948 DEBUG [ConnectionManager init] () impl.SessionImpl.commit(108) SOI - 154 - committed
2016-09-07 17:00:42,949 DEBUG [ConnectionManager init] () impl.SessionImpl.close(122) SOI - 154 - closed
2016-09-07 17:00:52,722 WARN [FailedSyncProcessor Thread] () ucf.UCFFacadeImpl.replaceMdrListCache(307) - Broker appears to be down: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character '2' (code 50) in prolog; expected '<'
at [row,col {unknown-source}]: [1,1]

 

[Legacy User]

Hi David,

 

Could you try cleaning AMQ and see if this helps resolving this issue. I

have seen those issue long back where 'Broker appears to be down:' when AMQ

has problems.

 

Thanks,

Ashay

 

On Thu, Sep 8, 2016 at 7:02 PM, DBlanco1 <

[Daniel Blanco]

Okay it turned out to be related to our integration with our helpdesk ticketing system. I never applied the updated jar files and this was the cause. Once I applied the updated jar fixes, the UCF catalyst issue went away.