[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.)

Tue Oct 20 14:34:06 EDT 2009

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

Andy Goldstein commented on JBIDE-2050:
---------------------------------------

I just ran into this too.  I have 2 servers and I manually edited jboss-service.xml on each one to specify a ports configuration to use with the Service Binding Manager.  Unfortunately JBoss Tools doesn't appear to pick up this setting and assumes that I'm using the default ports, so it gets confused when I try to shut down server 2 for example - it instead shuts down server 1 (it thinks both servers are using the same default port settings).  I guess I'll go the xpath modification route for now.

> 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: Tools (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