[FOLIO-976] Use real module jar rather than module.jar in Docker container Created: 11/Dec/17  Updated: 12/Nov/18  Resolved: 20/Apr/18

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Task Priority: P3
Reporter: Adam Dickmeiss Assignee: Adam Dickmeiss
Resolution: Done Votes: 0
Labels: sprint28
Remaining Estimate: Not Specified
Time Spent: 30 minutes
Original estimate: Not Specified

Attachments: File folio-976.patch    
Issue links:
Relates
relates to FOLIO-974 proxyRequestResponse failure Closed
relates to FOLIO-886 add java remote debugging as standard... Closed
Sprint:

 Description   

This makes it a ton easier to track a module,



 Comments   
Comment by Adam Dickmeiss [ 11/Dec/17 ]

Is this folio-976.patch OK, John Malconian?

I'll apply to moc-codex-mux first. I think other modules should do the same.

Comment by shale99 [ 11/Dec/17 ]

is it possible to also add something like nmon - or that sar will collect info (mem, io, cpu, etc...) so that we can see how the container is behaving during usage? this will also allow us to cross reference requests to allocation spikes (at least during testing)

Comment by Adam Dickmeiss [ 11/Dec/17 ]

@shale99 isn't that a program/utility that should be part of the Virtual hosting box itself.. Not something we run per-container or am I missing something? First time I hear about nmon, it looks cool.

Comment by shale99 [ 11/Dec/17 ]

i think we may need this running per container? copy the script and run it on startup

Comment by John Malconian [ 11/Dec/17 ]

The patch is fine and I support the change. We are about to change the Dockerfiles rather dramatically, however, so you may want to hold off on making the change to additional modules.

Comment by Adam Dickmeiss [ 20/Apr/18 ]

Closing because I do see the fat jar with module product in it.

Generated at Thu Feb 08 23:09:55 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.