Why do my container logs contain "Cannot add to Component Factory" messages?

Document created by ashwini_ambatipudi1 Employee on Jul 21, 2015Last modified by vreddy on Mar 1, 2016
Version 2Show Document
  • View in full screen mode
For a process that uses Environment extensions to define a specific component and these extension values are changed, the container log entries might look similar to these:

 

Jun 15, 2015 2:13:10 PM EST FINE [com.boomi.component.ComponentFactory getComponentFile] Loading component from <Atom_Installation_Folder>/processes/<process_ID>/<component_ID>.xml
Jun 15, 2015 2:13:10 PM EST FINE [com.boomi.component.ComponentFactory getComponentFile] No component found, trying override directory: <Atom_Installation_Folder>/settings/<component_ID>.xml
Jun 15, 2015 2:13:10 PM EST FINE [com.boomi.component.ComponentFactory loadComponentMetaData] Unable to load component <component_ID> metadata, file<Atom_Installation_Folder>/settings/<component_ID>.xml does not exist.
Jun 15, 2015 2:13:10 PM EST WARNING [com.boomi.component.ComponentFactory indexComponents] Component <component_ID> does not exist in processes/<component_ID>, cannot add to Component Factory.
The "component not found" messages are merely warnings. They are caused by our component indexing logic, which is used when you perform certain actions e.g process deployment.

 

So once you modify the extensions, there is a chance that these messages are seen in the logs for that Atom around that time. Therefore, we recommend to not consider these as indicative of an issue.

Attachments

    Outcomes