jacorb.orb警告EM EAP的Jboss 7/Wildfly 10

问题描述：

所以...我收到奇怪来自JBoss的EAP一个应用程序警告7/Wildfly 10：jacorb.orb警告EM EAP的Jboss 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队列。

我应该担心吗？这是什么WARNING意思？

将帖子

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

答

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

我遵循这一解决方案，都成为OK：https://thejavablog.wordpress.com/tag/antlr/

答

那是CORBA子系统，它允许与旧的CORBA服务器的互操作。你可以忽略这个。我对Wildfly 9更加熟悉，所以我不确定你可以从Wildfly 10中删除ORB（Object Request Broker），但是如果警告困扰你，可能值得考虑。

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

此应用程序有十个一年使用CORBA从您的WEB-INF \ lib中。 – Jroger

jacorb.orb警告EM EAP的Jboss 7/Wildfly 10

相关推荐