Uploaded image for project: 'OpenDJ'
  1. OpenDJ
  2. OPENDJ-7840

HTTP embedded listener throws IllegalStateException: Output channel is not set

    XMLWordPrintable

    Details

    • Bug
    • Status: Done
    • Blocker
    • Resolution: Fixed
    • 7.1.0
    • 7.1.0
    • regression, rest

      Description

      With 4-ways test scenario-2 and scenario-3 using idcloud-2021.1 I hit following error:

      [19/Feb/2021:05:11:42 +0000] category=CORE severity=ERROR msgID=140 msg=An uncaught exception during processing for thread "Worker Thread 0" has caused it to terminate abnormally. The stack trace for that exception is: IllegalStateException: Output channel is not set at ReactiveDataProducer.java:106 ReactiveDataProducer.java:100 AtomicThrowable.java:92 HalfSerializer.java:81 StrictSubscriber.java:109 FlowableGenerate.java:196 ApacheRequestProcessor.java:307 ApacheRequestProcessor.java:262 FlowableInternalHelper.java:62 FlowableInternalHelper.java:53 FlowableGenerate.java:108 SubscriptionHelper.java:202 StrictSubscriber.java:87 FlowableGenerate.java:51 Flowable.java:15757 Flowable.java:15706 ReactiveServerExchangeHandler.java:84 ReactiveServerExchangeHandler.java:76 ApacheRequestProcessor.java:259 ApacheRequestProcessor.java:176 PromiseImpl.java:464 PromiseImpl.java:346 PromiseImpl.java:538 PromiseImpl.java:526 PromiseImpl.java:342 PromiseImpl.java:333 PromiseImpl.java:315 PromiseImpl.java:292 ApacheRequestProcessor.java:176 ApacheRequestProcessor.java:163 HTTPConnectionHandler.java:623 TraditionalWorkQueue.java:347
      [19/Feb/2021:05:11:42 +0000] category=CORE severity=NOTICE msgID=139 msg=The Directory Server has sent an alert notification generated by class org.opends.server.api.DirectoryThread (alert type org.opends.server.UncaughtException, alert ID org.opends.messages.core-140): An uncaught exception during processing for thread "Worker Thread 0" has caused it to terminate abnormally. The stack trace for that exception is: IllegalStateException: Output channel is not set at ReactiveDataProducer.java:106 ReactiveDataProducer.java:100 AtomicThrowable.java:92 HalfSerializer.java:81 StrictSubscriber.java:109 FlowableGenerate.java:196 ApacheRequestProcessor.java:307 ApacheRequestProcessor.java:262 FlowableInternalHelper.java:62 FlowableInternalHelper.java:53 FlowableGenerate.java:108 SubscriptionHelper.java:202 StrictSubscriber.java:87 FlowableGenerate.java:51 Flowable.java:15757 Flowable.java:15706 ReactiveServerExchangeHandler.java:84 ReactiveServerExchangeHandler.java:76 ApacheRequestProcessor.java:259 ApacheRequestProcessor.java:176 PromiseImpl.java:464 PromiseImpl.java:346 PromiseImpl.java:538 PromiseImpl.java:526 PromiseImpl.java:342 PromiseImpl.java:333 PromiseImpl.java:315 PromiseImpl.java:292 ApacheRequestProcessor.java:176 ApacheRequestProcessor.java:163 HTTPConnectionHandler.java:623 TraditionalWorkQueue.java:347
      

      The description of the test is here: https://wikis.forgerock.org/confluence/display/QA/Four+replicas
      I used 5 machines on AWS infrastructure type of m4.4xlarge. 400Gb disk space. The duration of the test was 1 day. 

      Reports can be found here: report 

       

        Attachments

        1. errors
          19 kB
        2. replication
          31 kB
        3. server.out
          6 kB

          Issue Links

            Activity

              People

              cforel carole forel
              ondrej.fuchsik Ondrej Fuchsik
              Nicolas Capponi Nicolas Capponi
              carole forel carole forel
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: