dermasmid commented on issue #29683:
URL: https://github.com/apache/beam/issues/29683#issuecomment-1875977894

   im getting the same with the typescript direct runner (which also uses the 
python logging server)
   
   ```
   2024-01-03 22:45:28 Jan 03, 2024 8:45:28 PM 
org.apache.beam.fn.harness.FnHarness main
   2024-01-03 22:45:28 SEVERE: Shutting down harness due to exception
   2024-01-03 22:45:28 java.util.concurrent.ExecutionException: 
org.apache.beam.vendor.grpc.v1p54p0.io.grpc.StatusRuntimeException: 
UNAVAILABLE: Network closed for unknown reason
   2024-01-03 22:45:28     at 
java.base/java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:395)
   2024-01-03 22:45:28     at 
java.base/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:2005)
   2024-01-03 22:45:28     at 
org.apache.beam.fn.harness.FnHarness.main(FnHarness.java:381)
   2024-01-03 22:45:28     at 
org.apache.beam.fn.harness.FnHarness.main(FnHarness.java:203)
   2024-01-03 22:45:28     at 
org.apache.beam.fn.harness.FnHarness.main(FnHarness.java:165)
   2024-01-03 22:45:28     at 
org.apache.beam.fn.harness.FnHarness.main(FnHarness.java:111)
   2024-01-03 22:45:28     Suppressed: java.lang.RuntimeException: 
java.lang.IllegalStateException: Logging stream terminated unexpectedly before 
it was closed by the client with error: 
org.apache.beam.vendor.grpc.v1p54p0.io.grpc.StatusRuntimeException: 
UNAVAILABLE: Network closed for unknown reason
   ```
   
   ```
   2024-01-03 22:45:28 Jan 03, 2024 8:45:28 PM 
org.apache.beam.fn.harness.FnHarness main
   2024-01-03 22:45:28 INFO: Shutting SDK harness down.
   2024-01-03 22:45:28 2024/01/03 20:45:28 boot.go: error logging message over 
FnAPI. endpoint host.docker.internal:60714 error: EOF message follows
   2024-01-03 22:45:28 2024/01/03 20:45:28 CRITICAL Java exited: <nil>
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to