Martin Vogel from sirius-net GmbH informed me in an email about a possible problem with DAOS and Java agents.
If DAOS is activated on a database, in addition to the attachments from data documents, the jar files contained in a Java agent are also transferred to the DAOS repository if they exceed the set size.
I have been able to reproduce the problem with Domino V11.
I started with a freshly installed server, activated DAOS on the server
and enabled the database for DAOS.
load compact -c -DAOS ON barcode.nsf [0B1C:0004-2C3C] 23.01.2020 18:26:48 Informational, DAOS has been enabled for database barcode.nsf. [0B1C:0004-2C3C] 23.01.2020 18:26:48 Compacting barcode.nsf (barcode), -c -DAOS ON barcode.nsf [0B1C:0004-2C3C] 23.01.2020 18:26:48 Recovery Manager: Assigning new DBIID for C:\Domino\Data\barcode.nsf (need new backup for media recovery). [0B1C:0004-2C3C] Clearing DBIID 5B9C3856 for DB C:\Domino\Data\barcode.ORIG [0B1C:0004-2C3C] 23.01.2020 18:26:49 Compacted barcode.nsf, 5K bytes recovered (<1%), -c -DAOS ON barcode.nsf [0B1C:0002-2F14] 23.01.2020 18:26:50 Database compactor process shutdown
Result: Both archive files contained in the agent were transferred to the DAOS repository as NLO.
The agent continues to run without any issue.
2 thoughts on “DAOS – JAR files in Java agents.”
If the agent continues to run without issue, what is the problem?
I found about this issue too the other day when looking at backup.
DAOS should NEVER do anything on design elements Period.
Comments are closed.