-
Bug
-
Resolution: Done
-
Major
-
JBossAS-4.0.4RC1, JBossAS-4.0.4.CR2
-
None
I'm seeing an error in the testsuite where the MBean deployment is failing. The deployment problem occurrs when deploying pooled.jar from testsuite/output/lib. The mbean which is the offender is pasted below.
The problem stems from an attribute being defined:
<attribute name="ServerSocketFactory"
attributeClass="org.jboss.security.ssl.DomainServerSocketFactory"
serialDataType="javaBean">
While the attribute ServerSocketFactory does exist, it does not have a getter or setter in the file /server/src/main/org/jboss/invocation/pooled/server/PooledInvokerMBean.java.
We define an attribute named
<mbean code="org.jboss.invocation.pooled.server.PooledInvoker"
name="jboss:service=invoker,type=pooled,socketType=SSLSocketFactory,wantsClientAuth=true">
<attribute name="NumAcceptThreads">1</attribute>
<attribute name="MaxPoolSize">300</attribute>
<attribute name="ClientMaxPoolSize">300</attribute>
<attribute name="SocketTimeout">60000</attribute>
<attribute name="ServerBindAddress">${jboss.bind.address}</attribute>
<attribute name="ServerBindPort">0</attribute>
<attribute name="ClientConnectAddress">${jboss.bind.address}</attribute>
<attribute name="ClientConnectPort">0</attribute>
<attribute name="ClientRetryCount">1</attribute>
<attribute name="EnableTcpNoDelay">false</attribute>
<!-- Customized socket factory attributes -->
<attribute name="ClientSocketFactoryName">org.jboss.security.ssl.ClientSocketFactory</attribute>
<attribute name="ServerSocketFactoryName"
attributeClass="org.jboss.security.ssl.DomainServerSocketFactory"
serialDataType="javaBean">
<property name="bindAddress">${jboss.bind.address}</property>
<property name="securityDomain">java:/jaas/pooled-ssl</property>
<property name="wantsClientAuth">true</property>
<property name="needsClientAuth">true</property>
<property name="CiperSuites">TLS_DHE_DSS_WITH_AES_128_CBC_SHA</property>
<property name="Protocols">SSLv2Hello,SSLv3,TLSv1</property>
</attribute>
</mbean>