This repository has been archived by the owner on Jan 5, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1
Vitro Logging
Aaron Collier edited this page Jun 14, 2018
·
4 revisions
In general, these steps are helpful when debugging a specific module during local development.
- Start Tomcat,
- Go to http://localhost:8080/vitro/admin/log4j.jsp
- Find the module you are using (i.e.
com.hp.hpl.jena.sparql.engine.http.HttpQuery
)- Note: Logger instances do not appear in the Log4J control page until the class they represent has been instantiated, so if the module is
edu.cornell.mannlib.vitro.webapp.searchindex.tasks.UpdateUrisTask
for instance, after starting Tomcat, login to the site admin panel and start a reindex before step #2
- Note: Logger instances do not appear in the Log4J control page until the class they represent has been instantiated, so if the module is
- Set the log level to DEBUG
- Scroll to the bottom of the page and click
Submit
- Watch the
vitro.all.log
file grow quickly.
- RIALTO Wiki Homepage
- RIALTO Use Cases
- RIALTO Architecture
- RIALTO Data Models
- RIALTO Acceptance Criteria
- RIALTO Data Sources
- Demo Videos
- Neptune/λ Integration
- Core/Combine Integration
- SPARQL Proxy λ
- Derivatives λ
- Entity Resolver Service
- Rebuild Trigger Task
- Solr Setup
- Ingest Service
- Combine Data Sources
- Data Mappings
- Load Procedure
- Starting & Monitoring ETL
- Counting # of Publications
- Jena/TDB vs Blazegraph
- Vitro Ingest Options
- VIVO/Vitro Assessment
- VIVO Community Convo Notes
- Vitro vs Stand-Alone Datastore
- Provisioning a VM
- Deployment Process
- Toggle inferencing
- Check Inferencing is On
- Recompute inferences
- Toggle indexing
- Working with Vitro Solr
- Vitro Solr Samples
- Ingest via Fuseki SPARQL-over-HTTP
- Ingest via Jena ARQ
- Ingest via Jena tdbloader
- Ingest via Vitro SPARQL-over-HTTP
- Ingest via TDB Java API
- Vitro Logging
- Detecting TDB Changes