Interesting, but I would expect the root cause is somewhere in not having set up all input options for running windup/analysis. Are you able to look at your Eclipse workspace and attach here content of <your_workspace_path>\.metadata\.log file?

Thanks, it seems the RMI connection to server is broken! What version of Windows do you have? I will try to similate that error.

Ok, I tried eclipse + rhamt plugin on windows8 and I can see the same connection issue like you. I need to discover what is the root cause if the windows itself blocking the connection or something else. Good thing is that the same build of plugin works on linux.

yes, I tried to run rhamt-cli with --startServer 1100 and that is the same command used in plugin and that pops up Windows Security Alert dialog to Allow the connection

I will try to try that in eclipse if that works

So that is part of it, but I can get the NullPointerException now too. I filed [WINDUP-1368] Windup on windows cannot start RMI server - JBoss Issue Tracker  and trying to discover root cause, after that we will it.

I would say use linux or MacOSx where the plugin works. Unfortunately whole our team is not using Windows regularly so we were not aware of this issue.

You can use also windup-maven-plugin in your maven project or pure CLI tool.

Hi Antoine, the bug should be fixed now, you can try it with updating from Index of /jbosstools/neon/snapshots/builds/windup-eclipse-plugin-NIGHTLY  or simply uninstall your old one and install the latest version from the URL update site.

Hi Marek,

I am getting the below error with registry. I know i am missing something here. I am new to JBoss and Windup.

I am trying to use Eclipse Neon 4.6.3 with JBoss Wildfly integrated. I got the Plugin for Windup and end up seeing this discussion.

I have updated the windup as mentioned in one of the above comments.

I could start the rmi registry on my windows 7 machine using start rmiregistry 1100 command.

Can you please help me out with a suggestion here ? Thanks.

!ENTRY org.jboss.tools.windup.runtime 1 0 2017-07-04 23:07:22.716

!MESSAGE Attempting to retrieve ExecutionBuilder from registry.

!ENTRY org.jboss.tools.windup.runtime 4 0 2017-07-04 23:07:22.732

!MESSAGE ExecutionBuilder not yet bound.

!STACK 0

java.rmi.NotBoundException: ExecutionBuilder

  at sun.rmi.registry.RegistryImpl.lookup(RegistryImpl.java:209)

  at sun.rmi.registry.RegistryImpl_Skel.dispatch(Unknown Source)

  at sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.java:450)

  at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)

  at sun.rmi.transport.Transport$1.run(Transport.java:200)

  at sun.rmi.transport.Transport$1.run(Transport.java:197)

  at java.security.AccessController.doPrivileged(Native Method)

  at sun.rmi.transport.Transport.serviceCall(Transport.java:196)

  at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:568)

  at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:826)

  at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:683)

  at java.security.AccessController.doPrivileged(Native Method)

  at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:682)

  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

  at java.lang.Thread.run(Thread.java:748)

  at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)

  at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)

  at sun.rmi.server.UnicastRef.invoke(Unknown Source)

  at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source)

  at org.jboss.tools.windup.runtime.WindupRmiClient.getExecutionBuilder(WindupRmiClient.java:164)

  at org.jboss.tools.windup.runtime.WindupRmiClient.updateWindupServer(WindupRmiClient.java:136)

  at org.jboss.tools.windup.ui.util.WindupLauncher$4$1.isDone(WindupLauncher.java:155)

  at org.jboss.tools.windup.ui.util.FutureUtils.waitForFuture(FutureUtils.java:82)

  at org.jboss.tools.windup.ui.util.WindupLauncher$4.doRun(WindupLauncher.java:170)

  at org.jboss.tools.windup.ui.util.FutureUtils$AbstractDelegatingMonitorJob.run(FutureUtils.java:112)

  at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

Hi Santosh,

have you started the RHAMT server in IDE?  I don't know why you should use "start rmiregistry 1100" command. It seems what exception says that the RMI service is not found.