Uploaded image for project: 'Java Driver'
  1. Java Driver
  2. JAVA-4446

can't connect to server

    • Type: Icon: Question Question
    • Resolution: Incomplete
    • Priority: Icon: Unknown Unknown
    • None
    • Affects Version/s: 4.4.0, 4.4.1
    • Component/s: Reactive Streams

      Summary

      i'm using mongodb-driver-reactivestreams to connect to my mongodb server, the version is 

      4.4.0, i have receive warn alarm some times, i found the alarm interface are connect to the mongodb. my project throw error 

      and i found the netty info is here

       

      the server version is:

      the mongo server is cluster mode, the program connect to the load balance proxy.

       

      my application is reform from a block system to a reactive system, from spring mvc to spring webflux, using kotlin and kotlin coroutines, when i work with the block driver, the issure dosn't appear, when i upgrade to reactive stream version, the error appear occasionally, i have read some code, the driver dosn't log any error message. 

      Please provide the version of the driver. If applicable, please provide the MongoDB server version and topology (standalone, replica set, or sharded cluster).

      i have wrote a mongo adapter to work with mongo server, the mongo adapter inject an mongoClient instance which product by spring

      mmy code is here

       

       

       

       

      my prog log is here:

      Steps to reproduce. If possible, please include a Short, Self Contained, Correct (Compilable), Example.

      Additional Background

      Please provide any additional background information that may be helpful in diagnosing the bug.

        1. image-2022-01-20-10-33-35-310.png
          image-2022-01-20-10-33-35-310.png
          6 kB
        2. image-2022-01-20-10-34-22-363.png
          image-2022-01-20-10-34-22-363.png
          44 kB
        3. image-2022-01-20-10-36-44-226.png
          image-2022-01-20-10-36-44-226.png
          5 kB
        4. image-2022-01-20-10-44-51-350.png
          image-2022-01-20-10-44-51-350.png
          10 kB
        5. image-2022-01-20-10-47-14-797.png
          image-2022-01-20-10-47-14-797.png
          154 kB
        6. image-2022-01-20-10-47-44-109.png
          image-2022-01-20-10-47-44-109.png
          136 kB
        7. image-2022-01-20-10-48-35-473.png
          image-2022-01-20-10-48-35-473.png
          100 kB
        8. image-2022-01-20-10-48-46-127.png
          image-2022-01-20-10-48-46-127.png
          100 kB
        9. image-2022-01-20-10-50-10-031.png
          image-2022-01-20-10-50-10-031.png
          41 kB
        10. image-2022-01-20-10-50-36-022.png
          image-2022-01-20-10-50-36-022.png
          17 kB
        11. image-2022-01-20-10-50-43-995.png
          image-2022-01-20-10-50-43-995.png
          17 kB
        12. image-2022-01-20-10-50-48-027.png
          image-2022-01-20-10-50-48-027.png
          17 kB
        13. image-2022-01-20-10-51-48-988.png
          image-2022-01-20-10-51-48-988.png
          56 kB
        14. screenshot-1.png
          screenshot-1.png
          146 kB
        15. screenshot-2.png
          screenshot-2.png
          126 kB
        16. screenshot-3.png
          screenshot-3.png
          128 kB
        17. bussiness error.log
          0.7 kB
        18. netty error report.log
          5.53 MB

            Assignee:
            ross@mongodb.com Ross Lawley
            Reporter:
            lovewebmail@gmail.com 夕 一
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: