[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-2050) Add support for ServiceBindingManager for port discovery. (Was AS (running/stopped) state is not retrieved in Eclipse if the server configuration is not the "default" but another one with different port bindings.)

[Rob Stryker (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBIDE-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12479402#action_12479402 ] 

Rob Stryker commented on JBIDE-2050:
------------------------------------

JBIDE-4729 is a duplicate of this bug.  From Denis: 

I got problem to start JBoss AS 5.1.0 because I have hudson running the local build for something. I guessed that Port group in JBoss AS Server editor provides the way to change the ports and realized that it just ports for pooling. So I cannot change the ports As it can be done for tomcat.

I understand that is not just so simple because actually there are a lot more ports used in AS. So I found the way to shift all ports and have AS and hudson up at the same time. Here is the description http://www.jboss.org/community/wiki/ConfigurePorts. Is that worth to support this in JBoss AS Tools? I mean the case with system property -Djboss.service.binding.set=ports-01

> Add support for ServiceBindingManager for port discovery.  (Was AS (running/stopped) state is not retrieved in Eclipse if the server configuration is not the "default" but another one with different port bindings.)
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-2050
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-2050
>             Project: JBoss Tools
>          Issue Type: Feature Request
>          Components: JBossAS
>    Affects Versions: 2.0.1
>         Environment: Linux 2.6.22-14-generic, Eclipse Europa Version: 3.3.2, JbossToolsPlugin 2.0.1GA-ALL linux, JbossAS 4.2.2.GA
>            Reporter: Mario Balaban
>            Assignee: Rob Stryker
>            Priority: Minor
>             Fix For: LATER
>
>
> On the same machine I had to create 2 instances of JbossAS, one for testing and another for development. The instance used for testing is using the "default" configuration. The test (default) instance I am able to start and to stop correctly from the Eclipse IDE. The "devel" instance that is a copy of the "default" configuration but has different port bindings (modified jboss-service.xml by uncommenting the tag <mbean code="org.jboss.services.binding.ServiceBindingManager"..../> )  has problems when starting and stopping  from eclipse IDE. In the console window of IDE  I see " [Server] JBoss (MX MicroKernel) [4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139)] Started in 15s:993ms" but the state of the server in the "Servers" window of the IDE is Starting... It remains "Starting..." till an OutOfMemory is visualized in the IDE. This error happens even when no applications are deployed to the deploy directory of the "devel" configuration. It seems that the problem is associated to different port bindings used by "devel" configuration.   

-- 
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