Aireed opened a new issue, #4384:
URL: https://github.com/apache/amoro/issues/4384
### What happened?
```
java.lang.RuntimeException: Fail to init user group information
at
org.apache.amoro.table.TableMetaStore$RuntimeContext.getUGI(TableMetaStore.java:396)
~[amoro-common-0.9.0-incubating.jar:0.9.0-incubating]
at
org.apache.amoro.table.TableMetaStore.getUGI(TableMetaStore.java:243)
~[amoro-common-0.9.0-incubating.jar:0.9.0-incubating]
at org.apache.amoro.table.TableMetaStore.doAs(TableMetaStore.java:252)
~[amoro-common-0.9.0-incubating.jar:0.9.0-incubating]
at
org.apache.amoro.server.catalog.ExternalCatalog.<init>(ExternalCatalog.java:47)
~[amoro-ams-0.9.0-incubating.jar:0.9.0-incubating]
at
org.apache.amoro.server.catalog.CatalogBuilder.buildServerCatalog(CatalogBuilder.java:98)
~[amoro-ams-0.9.0-incubating.jar:0.9.0-incubating]
at
org.apache.amoro.server.catalog.DefaultCatalogManager.lambda$getServerCatalog$3(DefaultCatalogManager.java:140)
~[amoro-ams-0.9.0-incubating.jar:0.9.0-incubating]
at
java.util.concurrent.ConcurrentHashMap.computeIfAbsent(ConcurrentHashMap.java:1708)
~[?:?]
at
org.apache.amoro.server.catalog.DefaultCatalogManager.getServerCatalog(DefaultCatalogManager.java:138)
~[amoro-ams-0.9.0-incubating.jar:0.9.0-incubating]
at
org.apache.amoro.server.catalog.DefaultCatalogManager.loadTable(DefaultCatalogManager.java:268)
~[amoro-ams-0.9.0-incubating.jar:0.9.0-incubating]
at
org.apache.amoro.server.table.DefaultTableService.loadTable(DefaultTableService.java:350)
~[amoro-ams-0.9.0-incubating.jar:0.9.0-incubating]
at
org.apache.amoro.server.scheduler.PeriodicTableScheduler.loadTable(PeriodicTableScheduler.java:197)
~[amoro-ams-0.9.0-incubating.jar:0.9.0-incubating]
at
org.apache.amoro.server.scheduler.inline.TableRuntimeRefreshExecutor.execute(TableRuntimeRefreshExecutor.java:159)
~[amoro-ams-0.9.0-incubating.jar:0.9.0-incubating]
at
org.apache.amoro.server.scheduler.PeriodicTableScheduler.executeTask(PeriodicTableScheduler.java:105)
~[amoro-ams-0.9.0-incubating.jar:0.9.0-incubating]
at
org.apache.amoro.server.scheduler.PeriodicTableScheduler.lambda$scheduleTableExecution$1(PeriodicTableScheduler.java:95)
~[amoro-ams-0.9.0-incubating.jar:0.9.0-incubating]
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) [?:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
[?:?]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
[?:?]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
[?:?]
at java.lang.Thread.run(Thread.java:840) [?:?]
Caused by: java.lang.IllegalAccessException: class
org.apache.amoro.utils.ReflectionUtils cannot access class
sun.security.krb5.Config (in module java.security.jgss) because module
java.security.jgss does not export sun.security.krb5 to unnamed module @4988d8b8
at
jdk.internal.reflect.Reflection.newIllegalAccessException(Reflection.java:392)
~[?:?]
at
java.lang.reflect.AccessibleObject.checkAccess(AccessibleObject.java:674) ~[?:?]
at java.lang.reflect.Method.invoke(Method.java:561) ~[?:?]
at
org.apache.amoro.utils.ReflectionUtils.invoke(ReflectionUtils.java:53)
~[amoro-common-0.9.0-incubating.jar:0.9.0-incubating]
at
org.apache.amoro.table.TableMetaStore$RuntimeContext.constructKerberosUgi(TableMetaStore.java:428)
~[amoro-common-0.9.0-incubating.jar:0.9.0-incubating]
at
org.apache.amoro.table.TableMetaStore$RuntimeContext.getUGI(TableMetaStore.java:392)
~[amoro-common-0.9.0-incubating.jar:0.9.0-incubating]
... 19 more
```
### Affects Versions
master
### What table formats are you seeing the problem on?
_No response_
### What engines are you seeing the problem on?
AMS
### How to reproduce
try to run ams with jdk17
### Relevant log output
```shell
```
### Anything else
_No response_
### Are you willing to submit a PR?
- [x] Yes I am willing to submit a PR!
### Code of Conduct
- [x] I agree to follow this project's Code of Conduct
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
