Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

[BUG] Server won't start (and channels won't deploy) on a Turkish JVM locale

未關閉
#483 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 2 天內回覆

還沒有人認領這個 Issue。

評估

難度
3/5
預估耗時
1-2 天
新手友好度
66/100
Issue 類型
缺陷
描述清晰度
描述清楚
活躍度
活躍
技術堆疊
java

研究方向

Start with JdbcDao.addMetaDataColumn, where StringUtils.lowerCase builds the query name, and with the MyBatis mapper files that hold the type aliases. Reproduce by running the server with -Duser.language=tr -Duser.country=TR and deploying a channel. Done means startup and channel deploy both succeed under the Turkish locale, using Locale.ROOT for case-insensitive lookups or explicit class names in the mappers.

由索引模型根據 Issue 內容生成。

描述

Spun off from #476. It all started with a test failing on my Italian machine. Out of curiosity I tried Turkish, the classic locale troublemaker, and things got worse: the server doesn't even start.

Describe the bug
Turkish has a dotted and a dotless i, so "I".toLowerCase() gives ı. OIE trips over this twice:

  1. Startup: MyBatis 3.1.1 lowercases type aliases with the default locale, so "Integer" becomes "ınteger", nobody knows what that is, and startup loops.
  2. Deploy: with (1) worked around, every channel deploy fails. JdbcDao.addMetaDataColumn builds the query name with StringUtils.lowerCase, so it looks for addMetaDataColumnStrıng, finds nothing, and Derby says "SQL text pointer is null".

Consistently reproducible.

To Reproduce
Run the server with -Duser.language=tr -Duser.country=TR, then deploy any channel.

Expected behavior
OIE works regardless of the system locale.

Environment

  • OS: macOS
  • Java: Zulu 17.0.17
  • Version: main @ a13e6afb6

Workaround(s)
Run the JVM with an English locale.

Notes
As offered in #476, happy to look into a fix if that works for you. Rough ideas:

  • for (1), use java.lang.Integer in the mappers (25 lines; MyBatis is fixed upstream since 3.2.0, but that's a big jump);
  • for (2), use Locale.ROOT where casing is used for lookups;
  • add a tr_TR smoke scenario so it stays fixed. That covers the CI half of #476.

Open to other approaches, of course.

主要語言
Java
星號
227
分支
81
平均合併
3 天 6 小時
30 天內合併 PR
15

環境準備

  • 提供 Dockerfile 或 Docker Compose 檔案
  • 沒有 Pull Request 範本
  • 閱讀貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

OpenIntegrationEngine/engine 的其他 Issue

查看 OpenIntegrationEngine/engine 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。