Problem configuring service jboss:service=CorbaORB
kamikatze Feb 19, 2005 9:20 AMHi!
I'm trying to get JBoss-Portal-2.0 run on my multi-homed SuSe 9.2 Linux box on JBoss-4.0.0.
I get the following message:
2005-02-19 14:58:22,550 DEBUG [org.jboss.system.ServiceCreator] Created bean: jboss:service=CorbaORB 2005-02-19 14:58:22,551 DEBUG [org.jboss.system.ServiceConfigurator] ORBClass set to org.jacorb.orb.ORB in jboss:service=CorbaORB 2005-02-19 14:58:22,551 DEBUG [org.jboss.system.ServiceConfigurator] ORBSingletonClass set to org.jboss.system.ORBSingleton in jboss:service=CorbaORB 2005-02-19 14:58:22,552 DEBUG [org.jboss.system.ServiceConfigurator] ORBSingletonDelegate set to org.jacorb.orb.ORBSingleton in jboss:service=CorbaORB 2005-02-19 14:58:22,553 DEBUG [org.jboss.system.ServiceConfigurator] ORBPropertiesFileName set to jacorb.properties in jboss:service=CorbaORB 2005-02-19 14:58:22,553 DEBUG [org.jboss.system.ServiceConfigurator] SunJDK14IsLocalBugFix set to false in jboss:service=CorbaORB 2005-02-19 14:58:22,553 INFO [org.jboss.system.ServiceConfigurator] Problem configuring service jboss:service=CorbaORB java.lang.IllegalArgumentException: [interceptor-initializers: null] at java.beans.PropertyEditorSupport.setAsText(PropertyEditorSupport.java:138) at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:313) at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:160) at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:114) at org.jboss.system.ServiceController.install(ServiceController.java:200) at sun.reflect.GeneratedMethodAccessor42.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) at org.jboss.mx.server.Invocation.invoke(Invocation.java:72) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
that would point me to an potentially incorrect iiop-service.xml:
<mbean code="org.jboss.iiop.CorbaORBService" name="jboss:service=CorbaORB"> <attribute name="ORBClass">org.jacorb.orb.ORB</attribute> <attribute name="ORBSingletonClass">org.jboss.system.ORBSingleton</attribute> <attribute name="ORBSingletonDelegate">org.jacorb.orb.ORBSingleton</attribute> <attribute name="ORBPropertiesFileName">jacorb.properties</attribute> <attribute name="SunJDK14IsLocalBugFix">false</attribute> <attribute name="PortableInterceptorInitializers"> <interceptor-initializers> <initializer>org.jboss.iiop.codebase.CodebaseInterceptorInitializer</initializer> <!-- comment out to disable null transaction propagation over IIOP --> <initializer>org.jboss.tm.iiop.TxIORInterceptorInitializer</initializer> <initializer>org.jboss.tm.iiop.TxServerClientInterceptorInitializer</initializer> <!-- comment out to disable transaction demarcation over IIOP --> <initializer>org.jboss.tm.iiop.TxServerInterceptorInitializer</initializer> <!-- Enable Security Attibute Service interceptors --> <initializer>org.jboss.iiop.csiv2.SASInitializer</initializer> <initializer>org.jboss.iiop.csiv2.CSIv2Initializer</initializer> </interceptor-initializers> </attribute> <!-- (uncomment to use IIOP over SSL) <attribute name="SecurityDomain">java:/jaas/IIOP+SSL</attribute> <depends>jboss.security:service=JaasSecurityDomain,domain=IIOP+SSL</depends> --> </mbean>
All what I can see, this is well-formed and as the other attributes are read without problems, I wonder why the <interceptor-initializers> are lost. The JDK14 attribute I've put in later, so the problem already existed with an unchanged iiop-service.xml
My configuration is different from the usual one, because I'm running on a multi-homed server. I start jboss with "-b 192.168.0.2 -c all" and I have amended the jacorb.properties to use the 192.168.0.2 as bind address as well: "OAIAddr=192.168.0.2"
Any idea?
Cheers, Mika