[mwr0707]

From the JBossIDE2.0 announcement thread:

Also, we have 4 new "demotorials" to help you migrate from JBossIDE 1.6 to JBossIDE 2.0, particularly surrounding our new JBossAS Adapter. You can find the links on the JBossAS Adapter New and Noteworthy page here:
http://docs.jboss.com/jbosside/jboss-as/NewAndNoteworthy/jbosside2.0.0.beta2.html

Watching these video demos is not optional! The entire ejb project creation, doclet setup, and deployment process has changed from what is described in the 1.X tutorial. Using the new process results in a different project type that is recognized by the "publish to server" dialog.

[sidewinder]

I have an installed 3.2.6 runtime and the EclipseIDE-Bundle.

I added a server runtime and a server and now tried to start it. Worked well, but it remained "Starting...".

I watched the demos at http://docs.jboss.com/jbosside/jboss-as/demos/create_server.htm and tried the "timeout trick". Now the IDE progress stops but the server still is in Starting-mode.

yes, my console output ends with "15:18:57,156 INFO [Server] JBoss (MX MicroKernel) [3.2.6 (build: CVSTag=JBoss_3_2_6 date=200410140106)] Started in 1m:6s:32ms"

i dont have a password-protected jboss-server (i use the default-configuration "AS-IS").

Environment:
OS: WinXP Prof. SP2
Eclipse: JBossIDE-2.0.0.Beta2-Bundle-win32.zip
JBoss: 3.2.6

so what else can i do?

interesting: my twiddle launch configuraton says "-S -s localhost:1099 " instead of "-S" as in case of the demo. but i cant delete the other argument.

please help :-)

best regards,
sidewinder

[sidewinder]

Add: It works well with JBoss 4.0.4 (even without the timeout-trick). So maybe the configuration is wrong for 3.2.6.

I can't move on to 4.0.4 so maybe there is a fix?

best regards,
sidewinder

[stanil]

The same situation, and the exception shown on console when i stop the server is as follows:

Exception in thread "main" java.lang.SecurityException: Failed to authenticate principal=null, securityDomain=jmx-console
at org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:97)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:179)
at sun.reflect.GeneratedMethodAccessor82.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:819)
at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:420)
at sun.reflect.GeneratedMethodAccessor81.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305)
at sun.rmi.transport.Transport$1.run(Transport.java:159)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:619)
at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:255)
at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:233)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:142)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown Source)
at org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:70)
at org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:100)
at $Proxy0.invoke(Unknown Source)
at org.jboss.Shutdown$ServerProxyHandler.invoke(Shutdown.java:266)
at $Proxy1.shutdown(Unknown Source)
at org.jboss.Shutdown.main(Shutdown.java:237)

[rob.stryker]

When starting JBoss from the command line, you don't need to provide a username or password. However, if your JBoss installation *is* password protected, you do need to provide that password to shut it down.

The IDE also uses some JMX code in order to ask the server if it's up yet. This also requires a username / password if your JMXConsole is password protected.

In order to provide the username / password (currently), you need to double-click on your chosen server, then click "edit launch configuration", and then to both the Stop Args and Twiddle Args tabs, add a username and password.

For shutdown, the syntax is -u user -p pass, or --user=user --password=pass

For twiddle, the arguments are exactly the same.