In this article

...

• jcc_json–Main log for tracking SnapLogic application event and error messages. 
• jcc_error.json–As errors are encountered, verbose error messages are written to this log.
• jcc.output.log–As the JCC is booting up, any informational, debugging, and error messages are written to this log.
• jcc_access.log–All requests to the node are written to this log. 
• jcc.status.log–JCC status is periodically written to this log.
• monitor.log–As the status of the monitor process initializes, events and errors are written to this log during boot up.
• monitor.json–The main log for tracking the monitoring application.
• monitor_error.json–Verbose error messages are written to this log, such as the stack traces.plex_Scheduler_stats.json–A debug snapshot available on both Groundplex and Cloudplex. This log file is only generated on demand like a thread dump or other diagnostic/debugging logs. 

• feed_master.json—The log for tracking FeedMaster event and error messages.

• feed_master_error.json—As errors are encountered, verbose error messages are written to this log.

• feed_master_access.log—All requests to the node are written to this log.

...

Compressed Class Space

In Java, you have Objects and Classes. Objects are instantiations of Classes. In terms of memory allocation, object data is stored on the heap and class data is stored in non-heap space. To prevent Pipeline preparation errors, the default compressed class space size is raised to 2G when the JVM heap space size is more than 10GB. If you get a Pipeline Failed to Prepare error related to compressed class space, add aCompressedClassSpaceSize option to the global.properties file to override the default. For example:

jcc.jvm_options = -XX:CompressedClassSpaceSize=2G

HTTP Proxy Configuration

Refer to the Node Proxies section for information about configuring through an HTTP proxy.

...

The Snaplex process creates outbound WebSocket connections to the SnapLogic cloud to be able to process incoming requests from the cloud. If running several nested Pipelines, or Pipelines using ForEach, there could be timeout errors if no connection is available to process an inbound request. By default, 20 connections are created. This can be increased if a higher number of cloud triggered Pipelines need to be run concurrently on the Snaplex node. The maximum allow value is 60. Setting this too high causes increased network overhead. If this has to be set to a larger value, it is an indication that more nodes need to be added to the Snaplex. Pipeline execution requests is automatically be load balanced across the available nodes.

...

The http_client_socket_timeout must be set to higher than the maximum child Pipeline execution time. 

Ring Buffer

The size of the buffer between Snaps is configured by setting the jcc.disruptor_ring_buffer_size in the global.properties. The default value is 1024.

...