problems shutting down jboss obscure i change jndi port

1st phase

i have problem shutting down controlling jboss instance underneath obscure given i changed
jndi pier jboss. impetus i close down console perspective nonetheless with
stop symbol (it still searches jndi pier during default 1099 port). i'm looking
disrespectful any solutions. conclude you!

used environment:

• jboss 4.0.2 (using default)


• eclipse 3.4.0. (using jboss collection 2.1.1.ga)

default ports: 1098, 1099
changed ports: 11098, 11099

i altered following biased jbosspath/server/default/conf/jboss-service.xml:

   <!-- ==================================================================== -->
   <!-- jndi                                                                 -->
   <!-- ==================================================================== -->

   <mbean code="org.jboss.naming.namingservice"
      name="jboss:service=naming"
      xmbean-dd="resource:xmdesc/namingservice-xmbean.xml">
      <!-- value mode. loyal lookups unmarshalled using
      caller's tcl, fake vm lookups relapse value reference.
      -->
      <attribute name="callbyvalue">false</attribute>
      <!-- listening pier bootstrap jnp service. set -1
        run namingservice but jnp invoker listening port.
      -->
      <attribute name="port">11099</attribute>
      <!-- bootstrap jnp server bond address. also sets default
      rmi use bond address. lifeless == addresses
       -->
      <attribute name="bindaddress">${jboss.bind.address}</attribute>
      <!-- pier rmi controlling service, 0 == opposite -->
      <attribute name="rmiport">11098</attribute>
      <!-- rmi use bond address. lifeless == addresses
       -->
      <attribute name="rmibindaddress">${jboss.bind.address}</attribute>
      <!-- thread pool use used control bootstrap lookups -->
      <depends optional-attribute-name="lookuppool"
         proxy-type="attribute">jboss.system:service=threadpool</depends>
   </mbean>

   <mbean code="org.jboss.naming.jndiview"
        name="jboss:service=jndiview"
        xmbean-dd="resource:xmdesc/jndiview-xmbean.xml">
   </mbean>

eclipse setup:

about jboss collection preferences:
i before version, i got problem, i review bugfix jbosstools, updated 2.1.1.ga. buttons changed, i've got new preferences view, nonetheless i can't cgange anything...seems divergent well:

error dialog:

the stacktrace:

javax.naming.communicationexception: obtain tie any urls: localhost:1099 [root difference javax.naming.communicationexception: unsuccessful bond server localhost:1099 [root difference javax.naming.serviceunavailableexception: unsuccessful bond server localhost:1099 [root difference java.net.connectexception: tie refused: connect]]]
    during org.jnp.interfaces.namingcontext.checkref(namingcontext.java:1385)
    during org.jnp.interfaces.namingcontext.lookup(namingcontext.java:579)
    during org.jnp.interfaces.namingcontext.lookup(namingcontext.java:572)
    during javax.naming.initialcontext.lookup(initialcontext.java:347)
    during org.jboss.shutdown.main(shutdown.java:202)
caused by: javax.naming.communicationexception: unsuccessful bond server localhost:1099 [root difference javax.naming.serviceunavailableexception: unsuccessful bond server localhost:1099 [root difference java.net.connectexception: tie refused: connect]]
    during org.jnp.interfaces.namingcontext.getserver(namingcontext.java:254)
    during org.jnp.interfaces.namingcontext.checkref(namingcontext.java:1370)
    ... 4 more
caused by: javax.naming.serviceunavailableexception: unsuccessful bond server localhost:1099 [root difference java.net.connectexception: tie refused: connect]
    during org.jnp.interfaces.namingcontext.getserver(namingcontext.java:228)
    ... 5 more
caused by: java.net.connectexception: tie refused: connect
    during java.net.plainsocketimpl.socketconnect(native method)
    during java.net.plainsocketimpl.doconnect(plainsocketimpl.java:305)
    during java.net.plainsocketimpl.connecttoaddress(plainsocketimpl.java:171)
    during java.net.plainsocketimpl.connect(plainsocketimpl.java:158)
    during java.net.socket.connect(socket.java:452)
    during java.net.socket.connect(socket.java:402)
    during java.net.socket.<init>(socket.java:309)
    during java.net.socket.<init>(socket.java:211)
    during org.jnp.interfaces.timedsocketfactory.createsocket(timedsocketfactory.java:69)
    during org.jnp.interfaces.timedsocketfactory.createsocket(timedsocketfactory.java:62)
    during org.jnp.interfaces.namingcontext.getserver(namingcontext.java:224)
    ... 5 more
exception thread "main" 

2nd phase:

after formulating new server file/new/other/server, seem preferences tab. stop symbol operative (the server receives shutdown messages but any additional alteration jndi pier -- there event now) nonetheless still throws an blunder message, nonetheless different, it's but difference smoke-stack trace: "server jboss 4.0 server unsuccessful stop."