1

所以...我从 JBoss-EAP 7 / Wildfly 10 中的应用程序收到奇怪的警告：

[Server:teste] INFO  2017-02-15 13:52:02,669 [jacorb.orb] Initialising ORB with ID:
[Server:teste] WARN  2017-02-15 13:52:02,701 [jacorb.orb] unable to build ORBInitializer from class true: Ignoring
[Server:teste] INFO  2017-02-15 13:52:02,750 [orb.interceptors] InterceptorManager started with 0 Server Interceptors, 0 Client Interceptors and 1 IOR Interceptors

这个应用程序有十年了，需要 CORBA 库才能使用 JMS 队列。

我应该担心吗？这个警告是什么意思？

[编辑]

Additional logs popout out now:

javax.naming.InvalidNameException: Couldn't resolve initial reference: NameService [Root exception is org.omg.CORBA.ORBPackage.InvalidName: IDL:omg.org/CORBA/ORB/InvalidName:1.0]
        at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:52)
        at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:644)
        at weblogic.corba.j2ee.naming.ORBHelper.getORBReference(ORBHelper.java:594)
        at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:85)
        at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:31)
        at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:46)
        at org.jboss.as.naming.InitialContext.getDefaultInitCtx(InitialContext.java:114)
        at org.jboss.as.naming.InitialContext.init(InitialContext.java:99)
        at javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:154)
        at org.jboss.as.naming.InitialContext.<init>(InitialContext.java:89)
        at org.jboss.as.naming.InitialContextFactory.getInitialContext(InitialContextFactory.java:43)
        at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684)
        at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:313)
        at javax.naming.InitialContext.init(InitialContext.java:244)
        at javax.naming.InitialContext.<init>(InitialContext.java:216)
        at com.alu.feeder.tasks.ExpediterRfbNotificationConsumerTask.executarProcesso(ExpediterRfbNotificationConsumerTask.java:88)
        at com.alu.feeder.tasks.ExpediterRfbNotificationConsumerTask.run(ExpediterRfbNotificationConsumerTask.java:51)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.springframework.util.MethodInvoker.invoke(MethodInvoker.java:273)
        at org.springframework.scheduling.quartz.MethodInvokingJobDetailFactoryBean$MethodInvokingJob.executeInternal(MethodInvokingJobDetailFactoryBean.java:260)
        at org.springframework.scheduling.quartz.QuartzJobBean.execute(QuartzJobBean.java:86)
        at org.quartz.core.JobRunShell.run(JobRunShell.java:216)
        at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:549)
Caused by: org.omg.CORBA.ORBPackage.InvalidName: IDL:omg.org/CORBA/ORB/InvalidName:1.0
        at org.jacorb.orb.ORB.resolve_initial_references(ORB.java:1609)
        at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:631)
        ... 24 more
4

2 回答 2

1

这就是允许与旧 CORBA 服务器互操作的 CORBA 子系统。你可以忽略这个。我对 Wildfly 9 更熟悉，所以我不确定您是否可以从 Wildfly 10 中删除 ORB（对象请求代理），但如果警告困扰您，可能值得研究一下。

我在 90 年代使用了 CORBA。这不是一次愉快的经历，所以我怀疑你会想要使用它。

于 2017-02-15T16:08:40.017 回答
0

所以，问题的发生是因为 weblogic.jar 包含一个由类加载器加载的 antlr.jar 版本，而休眠的东西是由另一个类加载器加载的。因此，当服务器运行时，它使用的是与 weblogic 捆绑在一起的 antlr 版本，它看不到休眠类。

我遵循这个解决方案，一切都变好了：https ://thejavablog.wordpress.com/tag/antlr/

于 2017-03-30T17:46:31.737 回答