[jboss-jira] [JBoss JIRA] Commented: (JBAS-1458) EJB containers require JRMP invoker

[Frank Grimes (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBAS-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12466828#action_12466828 ] 

Frank Grimes commented on JBAS-1458:
------------------------------------

We recently have been bitten by this.
Our customers run our software (which bundles JBoss) with multiple instances on one *NIX server.
They also run other third-party software to which they assign ports explicitly per instance.

Because JBoss was picking up a handful random ports from the OS based on the default server config, we hit conflicts where JBoss was holding a port to be used by another service.

Since we truly have no need for any remote access to these JBoss instances, we set about trying to disable all port bindings except port 80 for HTTP.
We have been able to eliminate all of them except for the RMIObjectPort, and only because the EJB container can't seem to run without it.

I see this issue has been in limbo for 3 years... any chance this could be addressed?
Is it a trivial change? 
Would you accept a patch for this?

> EJB containers require JRMP invoker
> -----------------------------------
>
>                 Key: JBAS-1458
>                 URL: https://jira.jboss.org/jira/browse/JBAS-1458
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: EJB2
>    Affects Versions: JBossAS-3.2.6 Final, JBossAS-3.2.7 Final, JBossAS-4.0.1 Final
>            Reporter: Andrew Oliver
>            Priority: Minor
>
> EJBs require the JRMP invoker even if the container-configuration is not bound to the JRMP invoker.  It should be possible to deploy EJBs that are not remotely accessible (even if they have Remote interfaces) via any invoker except for local.  Specifying the local invoker in the proxy binding doesn't work either.  Consider standard WEB->EJB applications with no remote clients.  
> While you can just block the port, it would be nice not to have to expend resources listening on a port that is blocked.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira