Note that there are some explanatory texts on larger screens.

plurals
  1. POJboss configuration on Eclipse 3.4 : stopping issue
    text
    copied!<p>I have a problem with my jboss configuration on eclipse ide :<br> I had to change the Jboss configuration in jboss-service.xml because the default port used was already in use (1099 port).<br> A server configuration change on eclipse wasn't taken into account : It seems to me that jndi port in server properties isn't taken into account on start action.<br> So I 've modified jboss-service.xml in JBOSS/default/conf repository. </p> <pre><code>&lt;code&gt; &lt;!-- ==================================================================== --&gt; &lt;!-- JNDI --&gt; &lt;!-- ==================================================================== --&gt; &lt;mbean code="org.jboss.naming.NamingService" name="jboss:service=Naming"&gt; &lt;!-- The listening port for the bootstrap JNP service. Set this to -1 to run the NamingService without the JNP invoker listening port. --&gt; &lt;attribute name="Port"&gt;1199&lt;/attribute&gt; &lt;!-- The bootstrap JNP server bind address. This also sets the default RMI service bind address. Empty == all addresses --&gt; &lt;attribute name="BindAddress"&gt;${jboss.bind.address}&lt;/attribute&gt; &lt;!-- The port of the RMI naming service, 0 == anonymous --&gt; &lt;attribute name="RmiPort"&gt;1198&lt;/attribute&gt; &lt;!-- The RMI service bind address. Empty == all addresses --&gt; &lt;attribute name="RmiBindAddress"&gt;${jboss.bind.address}&lt;/attribute&gt; &lt;/mbean&gt; &lt;mbean code="org.jboss.naming.JNDIView" name="jboss:service=JNDIView" xmbean-dd="resource:xmdesc/JNDIView-xmbean.xml"&gt; &lt;/mbean&gt; &lt;/code&gt; </code></pre> <p>This change is well taken into account on JBoss start but I can't stop it normally. The stop action keep 1099 port, so it kills the java process instead of stopping the server.</p> <p>Configuration : JBoss 3.2.5 and eclipse 3.4.0</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload