[GLASSFISH-16482] [UB]We need to document restrictions on cloud configuration if an app client is using RMI-IIOP and IIOP FOLB. Created: 27/Apr/11  Updated: 15/Mar/13  Resolved: 15/Mar/13

Status: Closed
Project: glassfish
Component/s: docs
Affects Version/s: 4.0
Fix Version/s: not determined

Type: Task Priority: Blocker
Reporter: Ken Cavanaugh Assignee: Paul Davies
Resolution: Invalid Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

As discussed in RFEs 16480 and 16481, there are some issues with the use of IIOP FOLB in a cloud
environment. We are not currently planning on implementing 16480 and 16481 in GF 3.2, so the
restrictions need to be documented. The restrictions are:

1. All instances in the cloud-based GF cluster must have iiop listeners configured on publicly accessible
IP addresses.

2. All instances in the cloud-based GF cluster must have statically-assigned (that is, not using DHCP)
IP addresses for the iiop listeners.

Without these restrictions, IIOP cannot be used in a cloud-based cluster.



 Comments   
Comment by Paul Davies [ 20/Dec/11 ]

[UB]: Unbundled documentation

Comment by Mike Fitch [ 15/Mar/13 ]

This issue is being closed as invalid because it calls for documentation of a limitation that doesn't exist, given that the situation that would give rise to the limitation is not a committed feature of any in-progress or planned GlassFish release.

Generated at Sat Apr 25 17:08:35 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.