[jboss-jira] [JBoss JIRA] Closed: (JBAS-5269) securityDomain property not being picked up / initiated in JRMPInvoker's RMIServerSocketFactoryBean attribute
[ http://jira.jboss.com/jira/browse/JBAS-5269?page=all ]
Adrian Brock closed JBAS-5269.
------------------------------
Resolution: Rejected
Assignee: (was: Ron Sigal)
Why are you raising bug reports as subtasks of closed issues in old releases?
1) Check whether it is fixed in the latest version before raising bug reports
2) Raise a top level bug report against the latest release, not as a subtask
of a closed issue.
3) Show relevant information (config, logs, etc.)
4) While an NPE is always a bug (it should give a proper error message telling you
what is wrong) it usually means missing configuration. Use the forums to ask for help.
> securityDomain property not being picked up / initiated in JRMPInvoker's
RMIServerSocketFactoryBean attribute
>
-------------------------------------------------------------------------------------------------------------
>
> Key: JBAS-5269
> URL: http://jira.jboss.com/jira/browse/JBAS-5269
> Project: JBoss Application Server
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: Security, Remoting
> Affects Versions: JBossAS-4.0.5.GA
> Environment: Redhat Linux, JBoss 4.0.5GA
> Reporter: Yukai Wang
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> securityDomain property has not been picked up / initiated in JRMPInvoker's
RMIServerSocketFactoryBean attribute so that when this property is set, JBoss can not
start the related MBean service and gives out NullPointerException.
> Reference from http://lists.jboss.org/pipermail/jbossws-users/2007-March/001817.html
> I did already check out:
> http://jira.jboss.com/jira/browse/JBAS-1983
> but was not able to configure the ciphersuites accordingly
> (this included JBAS-2785). I wasn't unable to check out,
> if these settings would change anything on WebServices,
> since JBoss doesn't start due to a null pointer exception
> (see attachment). As some debugging reveals, this is
> because the member "securityDomain" within:
> org.jboss.security.ssl.ServerSocketFactory
> seems to not get initialized.
>