Closed ascheider closed 11 months ago
Do you have a call stack of the error? Imho this can only happen if the dataport was configured to be executed automatically (see checkbox Automatically execute on new data
)
@BlackbitDevs Here the profile no Mapping and never executed, only created: We have automatically execute on new data but on another data ports. I made some stack traces on this point:
The first one is executed if you open up the data port where you have "XML / HTML" selected.
The second one is executed when you change object from another dataport which has 'Automatically execute on new data'. Hope it helps.
Have fixed this proble. Please update to latest 3.5.x-dev.
If you create a new data port in data director and do not configure it properly the data source type is "XML / HTML" preselected by default. In this case data director writes a lot of application logger messages. We had full disc at the weekend on one server, without doing import or another stuff with the profile. The customer just created it for the later configuration. The error is produced by data director in XmlParser class. Maybe you can improve it and trigger this error, only if import with this data port is running, but not if the config is just not done yet.