HangfireIO/Hangfire

System.Globalization.CultureNotFoundException. Culture is not supported.

Open

#964 创建于 2017年8月11日

在 GitHub 查看
 (1 评论) (0 反应) (0 负责人)C# (10,068 star) (1,748 fork)batch import
a: corehelp wanted

描述

I'm using:

  • HangFire.Core v1.4.6
  • Hangfire.SqlServer v1.4.6
  • Windows 10 x64
  • IIS 8.5 (not important probably but still)

Suddenly I got failed jobs containing next exception:

System.Globalization.CultureNotFoundException

Culture is not supported. Parameter name: name en-SI is an invalid culture identifier.

System.Globalization.CultureNotFoundException: Culture is not supported.
Parameter name: name
en-SI is an invalid culture identifier.
   at System.Globalization.CultureInfo..ctor(String name, Boolean useUserOverride)
   at Hangfire.CaptureCultureAttribute.OnPerforming(PerformingContext filterContext)
   at Hangfire.Server.BackgroundJobPerformer.InvokePerformFilter(IServerFilter filter, PerformingContext preContext, Func`1 continuation)

Hangfire was using two servers if that makes any difference. After deleting all Hangfire tables it now works, but still don't know why this happened.

But why does CultureNotFoundException occurs? Thread is always running under valid culturename. I found next post: https://stackoverflow.com/questions/38690850/disable-preservecultureattribute-in-hangfire

贡献者指南

技术栈
csharp
领域
backend
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
under 1 hour
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
C#.NET globalizationHangfire basics
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
70
研究方向
The issue is a CultureNotFoundException when Hangfire encounters the 'en SI' culture identifier. The key file is CaptureCultureAttribute.cs, specifically the OnPerforming method. Investigate how the culture is captured and consider adding validation to fall back to InvariantCulture or the system default culture when the specified culture is not supported. The StackOverflow link provided may offer additional insights. A potential fix could involve wrapping the culture creation in a try catch or using a culture factory method.