ERROR - Caching: (1/935) Image not available.

0
Anybody a guess what the caching error means? We see this one pop up regularly with the complete base64 encoded image string in the logs. Strange to say image not found and then place what looks like the complete image base64 encoded in the logs. And it clutters up the logs a bit. Regards, Ronald Jan 29 13:28:17 127.0.0.1 tr10000: ERROR - Caching: (1/935) Image not available. URI: data:image/jpeg;base64,0M8R4KGxGuEAAAAAAAAAAAAAAAAAAAAAPgADAP7/CQAGAAAAAAAAAAAAAAABAAAAMgAAAAAAAAAA Jan 29 13:28:17 127.0.0.1 tr10000: ERROR - Caching: (2/935) EAAA/v///wAAAAD+////AAAAADEAAAD///////////////////////////////////////////// Jan 29 13:28:17 127.0.0.1 tr10000: ERROR - Caching: (3/935) //////////////////////////////////////////////////////////////////////////// Jan 29 13:28:17 127.0.0.1 tr10000: ERROR - Caching: (4/935) //////////////////////////////////////////////////////////////////////////// Jan 29 13:28:17 127.0.0.1 tr10000: ERROR - Caching: (5/935) //////////////////////////////////////////////////////////////////////////// Jan 29 13:28:17 127.0.0.1 tr10000: ERROR - Caching: (6/935) //////////////////////////////////////////////////////////////////////////// Jan 29 13:28:17 127.0.0.1 tr10000: ERROR - Caching: (7/935) //////////////////////////////////////////////////////////////////////////// Jan 29 13:28:17 127.0.0.1 tr10000: ERROR - Caching: (8/935) //////////////////////////////////////////////////////////////////////////// Jan 29 13:28:17 127.0.0.1 tr10000: ERROR - Caching: (9/935) //////////////////////////////////////////////////////////////////////////8J Jan 29 13:28:17 127.0.0.1 tr10000: ERROR - Caching: (10/935) CBAAAAYFAFQ4zQfJwAEABgcAAOEAAgCwBMEAAgAAAOIAAABcAHAAEAAAUm9uYWxkIENhdGVyc2Vs Jan 29 13:28:17 127.0.0.1 tr10000: ERROR - Caching: (11/935) cyAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg Jan 29 13:28:17 127.0.0.1 tr10000: ERROR - Caching: (12/935) ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIEIAAgCwBGEBAgAAAMABAAA9AQIA Jan 29 13:28:17 127.0.0.1 tr10000: ERROR - Caching: (13/935) AQCcAAIAEQAZAAIAAAASAAIAAAATAAIAAACvAQIAAAC8AQIAAAA9ABIAAAAAAHBi0S44AAAAAAAB Jan 29 13:28:17 127.0.0.1 tr10000: ERROR - Caching: (14/935) AFgCQAACAAAAjQACAAAAIgACAAAADgACAAEAtwECAAAA2gACAAAAMQAqAMgAAAD/f5ABAAAAAAAA Jan 29 13:28:17 127.0.0.1 tr10000: ERROR - Caching: (15/935) DQFNAFMAIABTAGEAbgBzACAAUwBlAHIAaQBmADEAKgDIAAEA/3+8AgAAAAAAAA0BTQBTACAAUwBh Jan 29 13:28:17 127.0.0.1 tr10000: ERROR - Caching: (16/935) AG4AcwAgAFMAZQByAGkAZgAxACoAyAACAP9/kAEAAAAAAAANAU0AUwAgAFMAYQBuAHMAIABTAGUA Jan 29 13:28:17 127.0.0.1 tr10000: ERROR - Caching: (17/935) cgBpAGYAMQAqAMgAAwD/f7wCAAAAAAAADQFNAFMAIABTAGEAbgBzACAAUwBlAHIAaQBmADEAKgDI Jan 29 13:28:17 127.0.0.1 tr10000: ERROR - Caching: (18/935) AAAA/3+QAQAAAAAAAA0BTQBTACAAUwBhAG4AcwAgAFMAZQByAGkAZgAxACoAyAAEAAwAkAEAAAEA Jan 29 13:28:17 127.0.0.1 tr10000: ERROR - Caching: (19/935) AAANAU0AUwAgAFMAYQBuAHMAIABTAGUAcgBpAGYAMQAqAMgABAAOAJABAAABAAAADQFNAFMAIABT Jan 29 13:28:17 127.0.0.1 tr10000: ERROR - Caching: (20/935) AGEAbgBzACAAUwBlAHIAaQBmADEAHgBoAQEAOAC8AgAAAAIAAAcBQwBhAG0AYgByAGkAYQAxAB4A Jan 29 13:28:17 127.0.0.1 tr10000: ERROR - Caching: (21/935) LAEBADgAvAIAAAACAAAHAUMAYQBsAGkAYgByAGkAMQAeAAQBAQA4ALwCAAAAAgAABwFDAGEAbABp Jan 29 13:28:17 127.0.0.1 tr10000: ERROR - Caching: (22/935) AGIAcgBpADEAHgDcAAEAOAC8AgAAAAIAAAcBQwBhAGwAaQBiAHIAaQAxAB4A3AAAABEAkAEAAAAC Jan 29 13:28:17 127.0.0.1 tr10000: ERROR - Caching: (23/935) AAcHAUMAYQBsAGkAYgByAGkAMQAeANwAAAAUAJABAAAAAgAHBwFDAGEAbABpAGIAcgBpADEAHgDc Jan 29 13:28:17 127.0.0.1 tr10000: ERROR - Caching: (24/935) AAAAPACQAQAAAAIABwcBQwBhAGwAaQBiAHIAaQAxAB4A3AAAAD4AkAEAAAACAAcHAUMAYQBsAGkA
asked
1 answers
0

This message doesn't sound familiar to me at all and I quickly searched the source code but can't find it either. Though it could be an error coming from the ehcache library that is being forwarded.

A quick search on the string "Image not available. URI:" on google reveals that it might also be coming from the Apache FOP library. We're using this when generating PDF files but I haven't seen this error before. Are you also using the FOP library in a custom implementation? If not, can you verify that the errors occurs when you are generating documents? It could also be coming from another custom Java action/library that is used in either an appstore module or your own implementation and that just happens to have an overlapping exception message.

Hope this helps a little in finding the cause.

answered