Weird java error, CodeCache is full

[Michael Demers]

Hello,

We've been having some odd errors showing up in the ArchivesSpace logs:

OpenJDK 64-Bit Server VM warning: CodeCache is full. Compiler has been disabled.

OpenJDK 64-Bit Server VM warning: Try increasing the code cache size using -XX:ReservedCodeCacheSize=

CodeCache: size=245760Kb used=243847Kb max_used=243885Kb free=1912Kb

 bounds [0x00007f828d000000, 0x00007f829c000000, 0x00007f829c000000]

 total_blobs=39560 nmethods=38795 adapters=675

 compilation: disabled (not enough contiguous free space left)

and

OpenJDK 64-Bit Server VM warning: C1 initialization failed. Shutting down all compilers
OpenJDK 64-Bit Server VM warning: C2 initialization failed. Shutting down all compilers

I don't know the implications of this. ASpace appears to be working fine.

These coincided with the sudden emergence of an issue where ASpace was repeatedly restarting itself until the disk filled up with expanded war files. I may have fixed this by changing a timeout value and/or provisioning more resources. However, I'm still seeing those particular messages in the log.

Anyone have an insight on this? Should I add that reserved code cache option to the startup script?

Thanks,

Michael Demers

Digital Technologies Librarian

Hagley Museum and Library

PO Box 3630 Wilmington, DE 19807-0630

302-658-2400 ext. 232

[Matthews, Lopez (EOM)]

Hello Everyone:

 

Me again with a different question this time. We would like to know the standard ArchivesSpace setup for our Production environment. The current Test setup is hosting the application

on the same windows server (ArchivesSpace and MySQL). Please suggest ideal setup for hosting our production environment like application hosted on dedicated App server and MySQL Database on the dedicated DB server. The current setup uses localhost to call the DB in the JDBC configuration since both are hosted on same server which brings to our next question - are there any issues making a remote call to database hosted on other server if we were to use two servers.

 

Sincerely,

Lopez

 

Lopez D. Matthews, Jr., PhD

State Archivist and Public Records Administrator

Office of the Secretary

District of Columbia Office of Public Records

1300 Naylor Court, NW

Washington, DC 20001

Office Line – 202-671-1105

Direct Line – 202-671-1108

Cell – 202-573-4035

https://opr.dc.gov

 

 

 

[Joshua D. Shaw]

We are in a container environment with the app, the db, and Solr all in separate containers, so totally feasible to run things on separate servers. You just need to update the various urls in the config file and make sure the servers allow those requests/ports/etc.

Best,

Joshua

---

From: archivesspac...@lyrasislists.org <archivesspac...@lyrasislists.org> on behalf of Matthews, Lopez (EOM) <lopez.m...@dc.gov>
Sent: Thursday, July 25, 2024 1:31 PM
To: archivesspac...@lyrasislists.org <archivesspac...@lyrasislists.org>
Subject: [ArchivesSpace Users Group] Production Environment for Archivespace

 

--
You received this message because you are subscribed to the Google Groups "Archivesspace_Users_Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to Archivesspace_User...@lyrasislists.org.
To view this discussion on the web visit https://groups.google.com/a/lyrasislists.org/d/msgid/Archivesspace_Users_Group/CO6PR09MB87745D27B5BAA5B291035FACEAAB2%40CO6PR09MB8774.namprd09.prod.outlook.com.

[Tom Hanstra]

There are lots of ways in which you can configure things and which way you go is going to depend upon a combination of what is available (either as you set it up or through your IT group) and how comfortable you are using the various options. 

Our site is using AWS. We have ArchivesSpace and Solr both running on the same virtual server, with the database hosted in an AWS RDS instance. That combination is working for us because we have a large AWS presence already.  And we have not had issues with the database being separated from the ArchivesSpace/Solr instance.

Tom

To view this discussion on the web visit https://groups.google.com/a/lyrasislists.org/d/msgid/Archivesspace_Users_Group/BYAPR03MB42938BC6819E9AABB57642B7ABAB2%40BYAPR03MB4293.namprd03.prod.outlook.com.

--

Tom Hanstra

Sr. Systems Administrator

han...@nd.edu

[Matthews, Lopez (EOM)]

Thank you so much!

 

From: 'Tom Hanstra' via Archivesspace_Users_Group <Archivesspac...@lyrasislists.org>
Sent: Friday, July 26, 2024 11:50 AM
To: Joshua D. Shaw <Joshua...@dartmouth.edu>
Cc: archivesspac...@lyrasislists.org
Subject: Re: [ArchivesSpace Users Group] Re: Production Environment for Archivespace

 

CAUTION: This email originated from outside of the DC Government. Do not click on links or open attachments unless you recognize the sender and know that the content is safe. If you believe that this email is suspicious, please forward to phis...@dc.gov for additional analysis by OCTO Security Operations Center (SOC).

 

To view this discussion on the web visit https://groups.google.com/a/lyrasislists.org/d/msgid/Archivesspace_Users_Group/CAA60kZP%3DvJ57r3JNVHyzg8J2viQjw0kZ_5r5SkzTsaQHQ3TSKQ%40mail.gmail.com.