[JBoss JIRA] Created: (JBIDE-2050) AS (running/stopped) state is not retrieved in Eclipse if the server configuration is not the "default" but another one with different port bindings.
10:34 a.m.
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: http://jira.jboss.com/jira/browse/JBIDE-2050
Project: Tools (JBoss Tools)
Issue Type: Bug
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
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:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:14 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-2050) AS (running/stopped) state is not retrieved in Eclipse if the server configuration is not the "default" but another one with different port bindings.
[ http://jira.jboss.com/jira/browse/JBIDE-2050?page=all ]
Max Andersen updated JBIDE-2050:
--------------------------------
Fix Version/s: 2.1
Assignee: Rob Stryker
Rob - any idea what is going on here ? don't we pick up the jmx settings correctly
and/or is there a way to override it per server that he can use ?
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: http://jira.jboss.com/jira/browse/JBIDE-2050
Project: Tools (JBoss Tools)
Issue Type: Bug
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
Assigned To: Rob Stryker
Fix For: 2.1
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:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:48 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-2050) AS (running/stopped) state is not retrieved in Eclipse if the server configuration is not the "default" but another one with different port bindings.
[ http://jira.jboss.com/jira/browse/JBIDE-2050?page=comments#action_12408869 ]
Rob Stryker commented on JBIDE-2050:
------------------------------------
Step one is to use the JBoss Servers View, select your server, and expand its "Event
Log" to see what's going on in JMX. It will provide more information.
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: http://jira.jboss.com/jira/browse/JBIDE-2050
Project: Tools (JBoss Tools)
Issue Type: Bug
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
Assigned To: Rob Stryker
Fix For: 2.1
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:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:21 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-2050) AS (running/stopped) state is not retrieved in Eclipse if the server configuration is not the "default" but another one with different port bindings.
[ http://jira.jboss.com/jira/browse/JBIDE-2050?page=comments#action_12409913 ]
Rob Stryker commented on JBIDE-2050:
------------------------------------
Found the bug. Investigating a solution
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: http://jira.jboss.com/jira/browse/JBIDE-2050
Project: Tools (JBoss Tools)
Issue Type: Bug
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
Assigned To: Rob Stryker
Fix For: 2.1
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:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:15 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-2050) AS (running/stopped) state is not retrieved in Eclipse if the server configuration is not the "default" but another one with different port bindings.
[ http://jira.jboss.com/jira/browse/JBIDE-2050?page=comments#action_12410624 ]
Rob Stryker commented on JBIDE-2050:
------------------------------------
Ok my last message was innaccurate. This is interesting. I had never used that specific
feature of JBoss before.
So... when trying to startup / shutdown, the tooling needs to know the JNDI port... The
question ultimately is how to find it. It is usually hard-coded in jboss-service.xml, and
that's where the tooling would usually find it.
You, however, have made use of the service binding feature. Rather than editing these
ports directly in the jboss-service.xml, you've kept them in another file in a named
configuration.
As of now, here's the best work-around I can offer you, which is actually pretty damn
good!
So, for the sake of example, let's call my new configuration "testConfig".
The first thing I did was open server/testConfig/conf/jboss-service.xml and modify the
store url to make sure the store file would be somewhere in testConfig.
<mbean code="org.jboss.services.binding.ServiceBindingManager"
name="jboss.system:service=ServiceBindingManager">
<attribute name="ServerName">ports-01</attribute>
<attribute
name="StoreURL">${jboss.home.url}/server/testConfig/conf/sample-bindings.xml</attribute>
<attribute name="StoreFactoryClassName">
org.jboss.services.binding.XMLServicesStoreFactory
</attribute>
</mbean>
The next thing I did was, in the JBoss Servers View, select my server, and in the lower
half, browse into XML Configuration -> Ports. In the properties view, you should see
one that says "JNDI". Right-click on that and select "Delete XPath".
Then right-click in the same area and select "New XPath".
The XPath's name ***must*** be JNDI
The XPath's pattern should be
//service-bindings/server[@name='ports-01']/service-config[@name='jboss:service=Naming']/binding
And in the "Attribute Name" field, put "port"
What this is basically doing is it's telling the tooling NOT to look in
jboss-service.xml for the JNDI port anymore, but to instead look in the new XPath. It
should find the real port there.
(The reason we had to delete and re-create the xpath rather than modify is that the xpath
UI does not currently display another field which limits the searching for the xpath to
one specific file.)
I realize this is a little convoluted. I'll leave the bug opened but modify it so that
it's a feature request to add support for service bindings more easily.
Hope this helps! Post here if you need any further assistance!
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: http://jira.jboss.com/jira/browse/JBIDE-2050
Project: Tools (JBoss Tools)
Issue Type: Bug
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
Assigned To: Rob Stryker
Fix For: 2.1
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:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:17 p.m.
New subject: [JBoss JIRA] Updated: (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.)
[ http://jira.jboss.com/jira/browse/JBIDE-2050?page=all ]
Rob Stryker updated JBIDE-2050:
-------------------------------
Summary: 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.) (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.)
Issue Type: Feature Request (was: Bug)
Fix Version/s: 2.2.x
(was: 2.1)
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: http://jira.jboss.com/jira/browse/JBIDE-2050
Project: Tools (JBoss Tools)
Issue Type: Feature Request
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
Assigned To: Rob Stryker
Fix For: 2.2.x
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:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:19 p.m.
New subject: [JBoss JIRA] Updated: (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.)
[ http://jira.jboss.com/jira/browse/JBIDE-2050?page=all ]
Rob Stryker updated JBIDE-2050:
-------------------------------
Component/s: JBossAS
Priority: Minor (was: Major)
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: http://jira.jboss.com/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
Assigned To: Rob Stryker
Priority: Minor
Fix For: 2.2.x
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:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:27 p.m.
New subject: [JBoss JIRA] Updated: (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.)
[
https://jira.jboss.org/jira/browse/JBIDE-2050?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen updated JBIDE-2050:
---------------------------------------
Fix Version/s: 3.0.0.beta
(was: 3.0.0.alpha)
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: 3.0.0.beta
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
10:30 a.m.
New subject: [JBoss JIRA] Updated: (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.)
[
https://jira.jboss.org/jira/browse/JBIDE-2050?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen updated JBIDE-2050:
---------------------------------------
Fix Version/s: 3.0.0.cr1
(was: 3.0.0.beta1)
slip all minor and below
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: 3.0.0.cr1
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
9:24 a.m.
New subject: [JBoss JIRA] Updated: (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.)
[
https://jira.jboss.org/jira/browse/JBIDE-2050?page=com.atlassian.jira.plu...
]
Rob Stryker updated JBIDE-2050:
-------------------------------
Fix Version/s: 3.0.1.GA
(was: 3.0.0.cr1)
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: 3.0.1.GA
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
1:32 a.m.
New subject: [JBoss JIRA] Updated: (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.)
[
https://jira.jboss.org/jira/browse/JBIDE-2050?page=com.atlassian.jira.plu...
]
Rob Stryker updated JBIDE-2050:
-------------------------------
Fix Version/s: 3.1.0
(was: 3.0.1.GA)
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: 3.1.0
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
1:04 p.m.
New subject: [JBoss JIRA] Updated: (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.)
[
https://jira.jboss.org/jira/browse/JBIDE-2050?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen updated JBIDE-2050:
---------------------------------------
Fix Version/s: 3.1.0.M3
(was: 3.1.0.M2)
slip to M3 because of no updates from assignee
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: 3.1.0.M3
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
6:27 a.m.
New subject: [JBoss JIRA] Updated: (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.)
[
https://jira.jboss.org/jira/browse/JBIDE-2050?page=com.atlassian.jira.plu...
]
Rob Stryker updated JBIDE-2050:
-------------------------------
Fix Version/s: LATER
(was: 3.1.0.M3)
Reboot... start from scratch
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
7:53 p.m.
New subject: [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.)
[
https://jira.jboss.org/jira/browse/JBIDE-2050?page=com.atlassian.jira.plu...
]
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
7:46 a.m.
New subject: [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.)
[
https://jira.jboss.org/jira/browse/JBIDE-2050?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen commented on JBIDE-2050:
--------------------------------------------
I think JBIDE-4729 looks like a good thing to support (i.e. have combo box with possible
port bindings in bindings.xml as values to select or type in whatever the user wants -
including choosing (Default) which will not set the property.
But shouldn't this be an issue for its self since this would be specific for AS5 and
the above is for 4.x family? i.e. JBIDE-4729 for AS5 would be the most interesting to do
first.
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
1:34 p.m.
New subject: [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.)
[
https://jira.jboss.org/jira/browse/JBIDE-2050?page=com.atlassian.jira.plu...
]
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
5464
days inactive
6021
days old
jbosstools-issues@lists.jboss.org
15 comments
5 participants
participants (5)
-
Andy Goldstein (JIRA) -
Mario Balaban (JIRA)
-
Max Andersen (JIRA)
-
Max Rydahl Andersen (JIRA)
-
Rob Stryker (JIRA)