You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by "GurbirSinghSehmi (via GitHub)" <gi...@apache.org> on 2025/04/28 07:50:44 UTC

[I] Pulsar send message going in infinite wait state due to DLL conflict [pulsar-dotpulsar]

GurbirSinghSehmi opened a new issue, #264:
URL: https://github.com/apache/pulsar-dotpulsar/issues/264

   ### Description
   
   Pulsar Send Message goes into an infinite wait state if we call it from a different project that is referencing System.Runtime.CompilerServices.Unsafe.dll.
   
   This particular DLL is used in almost all of our projects and cannot be removed.
   We are using direct DLL references instead of nugget package to implement pulsar as nugget package installation creates many of conflicts in our solution.
   
   Please find the tool via below link where this issue got reproduced.
   
   https://github.com/GurbirSinghSehmi/PulsarIssues
   
   In this mention tool if you add a depency reference to System.Runtime.CompilerServices.Unsafe.dll. then issue will get reproduced.
   
   ### Reproduction Steps
   
   Please follow below steps :
   1. Create a console application in .Net 4.7.2 framework.
   2. Add a reference to System.Runtime.CompilerServices.Unsafe.dll.
   3. Create another project as class library in .Net 4.7.2 and write the logic for sending message in this class. Use direct DLL references, dont use nugget package of pulsar for this.
   4. Now from the console application call the method of the class library created.
   5. The send message method in class library will go in infinite waiting state.
   
   ### Expected behavior
   
   The send Message of pulsar should work properly and should not go in infinite wait state
   
   ### Actual behavior
   
    The send message method in class library will go in infinite waiting state.
   
   ### Regression?
   
   _No response_
   
   ### Known Workarounds
   
   _No response_
   
   ### Configuration
   
   _No response_
   
   ### Other information
   
   _No response_


-- 
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: commits-unsubscribe@pulsar.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Pulsar send message going in infinite wait state due to DLL conflict [pulsar-dotpulsar]

Posted by "blankensteiner (via GitHub)" <gi...@apache.org>.
blankensteiner commented on issue #264:
URL: https://github.com/apache/pulsar-dotpulsar/issues/264#issuecomment-2871240936

   Ok, but it is still a red flag that you are not able to add DotPulsar via NuGet and need to make direct references. You need to address that first, since that solution might fix the other issue.
   I added a NuGet reference to [System.Runtime.CompilerServices.Unsafe](https://www.nuget.org/packages/System.Runtime.CompilerServices.Unsafe/6.1.2) to the Consuming and Producing samples in this repo. They both continue to work just fine.


-- 
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: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Pulsar send message going in infinite wait state due to DLL conflict [pulsar-dotpulsar]

Posted by "blankensteiner (via GitHub)" <gi...@apache.org>.
blankensteiner commented on issue #264:
URL: https://github.com/apache/pulsar-dotpulsar/issues/264#issuecomment-2847038248

   Hi
   Regarding 1, I have never heard of this issue. Referencing DotPulsar.dll directly (not using NuGet) fixes this and you are able to compile your project? If yes, is DotPulsar the only NuGet package you have issues with?


-- 
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: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Pulsar send message going in infinite wait state due to DLL conflict [pulsar-dotpulsar]

Posted by "GurbirSinghSehmi (via GitHub)" <gi...@apache.org>.
GurbirSinghSehmi commented on issue #264:
URL: https://github.com/apache/pulsar-dotpulsar/issues/264#issuecomment-2850778066

   Yes, I have added references to all dlls that DotPulsar refer to. The issue is only with System.Runtime.CompilerServices.Unsafe.dll, as I mentioned, this dll usage is only giving me the thread abort exception.


-- 
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: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Pulsar send message going in infinite wait state due to DLL conflict [pulsar-dotpulsar]

Posted by "GurbirSinghSehmi (via GitHub)" <gi...@apache.org>.
GurbirSinghSehmi commented on issue #264:
URL: https://github.com/apache/pulsar-dotpulsar/issues/264#issuecomment-2857475209

   "I don't think this is a System.Runtime.CompilerServices.Unsafe.dll <-> DotPulsar issue. You could try to delete the reference to the unsafe dll and see if DotPulsar starts working" --> This is tested from our end and if we remove reference to this dll it works as expected.a


-- 
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: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Pulsar send message going in infinite wait state due to DLL conflict [pulsar-dotpulsar]

Posted by "GurbirSinghSehmi (via GitHub)" <gi...@apache.org>.
GurbirSinghSehmi commented on issue #264:
URL: https://github.com/apache/pulsar-dotpulsar/issues/264#issuecomment-2834809188

   Hi,
   1. once i download Dot pulsar nugget package in our solution, then it is unable to identify string , bool and other primitive types.
   2. After a long period of time, I get thread abort exception.
   3. The state is disconnected at the time of send message.
   4. There are many different projects in my organization that use this dll and call our project as it is a shared solution, so the usage is unknown, but it is required in many other dll references. 


-- 
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: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Pulsar send message going in infinite wait state due to DLL conflict [pulsar-dotpulsar]

Posted by "blankensteiner (via GitHub)" <gi...@apache.org>.
blankensteiner commented on issue #264:
URL: https://github.com/apache/pulsar-dotpulsar/issues/264#issuecomment-2891478182

   If you manage to use DotPulsar via NuGet and have the same problem, please feel free to create a new issue. I am closing this one :-)


-- 
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: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Pulsar send message going in infinite wait state due to DLL conflict [pulsar-dotpulsar]

Posted by "blankensteiner (via GitHub)" <gi...@apache.org>.
blankensteiner closed issue #264: Pulsar send message going in infinite wait state due to DLL conflict
URL: https://github.com/apache/pulsar-dotpulsar/issues/264


-- 
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: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Pulsar send message going in infinite wait state due to DLL conflict [pulsar-dotpulsar]

Posted by "entvex (via GitHub)" <gi...@apache.org>.
entvex commented on issue #264:
URL: https://github.com/apache/pulsar-dotpulsar/issues/264#issuecomment-2834736181

   Hi @GurbirSinghSehmi,
   
   Thanks for reaching out. I have a few follow-up questions.
   
   1. What kinds of conflicts do you get in your solution, I am curries because I have never heard of DotPulsar causing conflicts before
   2. Are you receiving any information from the [exception handler](https://github.com/apache/pulsar-dotpulsar/wiki/Resilience)
   3. What does your [state](https://github.com/apache/pulsar-dotpulsar/wiki/Monitoring) indicate
   4. What is the purpose of using System.Runtime.CompilerServices.Unsafe.dll in your project


-- 
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: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Pulsar send message going in infinite wait state due to DLL conflict [pulsar-dotpulsar]

Posted by "GurbirSinghSehmi (via GitHub)" <gi...@apache.org>.
GurbirSinghSehmi commented on issue #264:
URL: https://github.com/apache/pulsar-dotpulsar/issues/264#issuecomment-2849296510

   Hi,
   Yes I am able to compile my solution if i directly reference DotPulsar.dll .
   This compilation issue happens with other nugget packages as well, as it is a common solution used by different teams , we are not advised to use direct nugget packages, hence we are directly referring the dll.


-- 
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: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Pulsar send message going in infinite wait state due to DLL conflict [pulsar-dotpulsar]

Posted by "blankensteiner (via GitHub)" <gi...@apache.org>.
blankensteiner commented on issue #264:
URL: https://github.com/apache/pulsar-dotpulsar/issues/264#issuecomment-2850245083

   Not being able to install NuGet packages is an indicator that something is wrong. Have you also manually added references to all DotPulsar's dependencies and their dependencies and their dependencies and so on, to ensure that all dlls are there?


-- 
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: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Pulsar send message going in infinite wait state due to DLL conflict [pulsar-dotpulsar]

Posted by "blankensteiner (via GitHub)" <gi...@apache.org>.
blankensteiner commented on issue #264:
URL: https://github.com/apache/pulsar-dotpulsar/issues/264#issuecomment-2857444425

   Since DotPulsar, and other NuGet packages, can't be installed the right way, without breaking the solution, there is an issue with the solution. I don't think this is a System.Runtime.CompilerServices.Unsafe.dll <-> DotPulsar issue. You could try to delete the reference to the unsafe dll and see if DotPulsar starts working.
   Before I can help you, you would need to solve the issue forcing your to use DotPulsar via direct references, since this is a major red flag.


-- 
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: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org