You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When invoking the hop/registerPipeline REST API with the payload provided below, the API throws a NullPointerException if the log_file flag is set to Y and a log_filename is specified.
The specified log file gets created in the container, but the exception occurs afterward, halting further execution.
Error Details:
Exception Message:
java.lang.NullPointerException
at java.base/java.util.concurrent.ConcurrentHashMap.putVal(ConcurrentHashMap.java:1011)
at java.base/java.util.concurrent.ConcurrentHashMap.put(ConcurrentHashMap.java:1006)
at org.apache.hop.core.logging.LoggingRegistry.registerLogChannelFileWriterBuffer(LoggingRegistry.java:261)
at org.apache.hop.core.logging.LogChannelFileWriter.(LogChannelFileWriter.java:74)
at org.apache.hop.core.logging.LogChannelFileWriter.(LogChannelFileWriter.java:87)
at org.apache.hop.www.BaseWorkflowServlet.createPipeline(BaseWorkflowServlet.java:146)
at org.apache.hop.www.RegisterPipelineServlet.generateBody(RegisterPipelineServlet.java:56)
Steps to Reproduce:
Start the Apache Hop server using the provided Docker script:
docker run -it --rm
--env HOP_SERVER_USER=admin
--env HOP_SERVER_PASS=admin
--env HOP_SERVER_SHUTDOWNPORT=8080
--env HOP_SERVER_PORT=8181
--env HOP_SERVER_HOSTNAME=0.0.0.0
-p 8080:8080
-p 8181:8181
--name my-hop-server-container
apache/hop:2.7.0
Make a POST request to hop/registerPipeline REST API with the following payload:
<pipeline_configuration>
...
<log_file>Y</log_file>
<log_filename>/tmp/generateRowsLog.log</log_filename>
...
</pipeline_configuration>
Observe that the log file is created inside the container, but a NullPointerException is thrown during the pipeline registration process.
In BaseWorkflowServlet.java, SimpleLoggingObject is created at line 118
Which further creating LogChannelFileWriter at line 143, serveletLoggingObject is used to get log channel Id which is of type SimpleLoggingObject.
SimpleLoggingObject class return LogChannelId as null at line 88
Above LogChannelFileWriter if furter send to registerLogChannelFileWriterBuffer which is using Log Channel Id as key thus further throwing null pointer exception at line 261
Apache Hop version?
2.7.0
Java version?
22.0.2
Operating system
Windows
What happened?
When invoking the hop/registerPipeline REST API with the payload provided below, the API throws a NullPointerException if the log_file flag is set to Y and a log_filename is specified.
The specified log file gets created in the container, but the exception occurs afterward, halting further execution.
Error Details:
Exception Message:
java.lang.NullPointerException
at java.base/java.util.concurrent.ConcurrentHashMap.putVal(ConcurrentHashMap.java:1011)
at java.base/java.util.concurrent.ConcurrentHashMap.put(ConcurrentHashMap.java:1006)
at org.apache.hop.core.logging.LoggingRegistry.registerLogChannelFileWriterBuffer(LoggingRegistry.java:261)
at org.apache.hop.core.logging.LogChannelFileWriter.(LogChannelFileWriter.java:74)
at org.apache.hop.core.logging.LogChannelFileWriter.(LogChannelFileWriter.java:87)
at org.apache.hop.www.BaseWorkflowServlet.createPipeline(BaseWorkflowServlet.java:146)
at org.apache.hop.www.RegisterPipelineServlet.generateBody(RegisterPipelineServlet.java:56)
Steps to Reproduce:
Start the Apache Hop server using the provided Docker script:
docker run -it --rm
--env HOP_SERVER_USER=admin
--env HOP_SERVER_PASS=admin
--env HOP_SERVER_SHUTDOWNPORT=8080
--env HOP_SERVER_PORT=8181
--env HOP_SERVER_HOSTNAME=0.0.0.0
-p 8080:8080
-p 8181:8181
--name my-hop-server-container
apache/hop:2.7.0
Make a POST request to hop/registerPipeline REST API with the following payload:
<pipeline_configuration>
...
<log_file>Y</log_file>
<log_filename>/tmp/generateRowsLog.log</log_filename>
...
</pipeline_configuration>
Observe that the log file is created inside the container, but a NullPointerException is thrown during the pipeline registration process.
Attached full xml payload
payload.txt
Expected Behavior:
The pipeline should register successfully, and logs should be written to the specified file without errors.
Issue Priority
Priority: 3
Issue Component
Component: Hop Server
The text was updated successfully, but these errors were encountered: