8 Replies Latest reply on Feb 22, 2017 3:36 AM by manarh

TitanConfiguration.properties Windup execution failed due to: null java.lang.NullPointerException

phaniramkakaraparthi Feb 21, 2017 8:57 AM

Hello

I am getting a null pointer exception when i am trying to run docker image of Windup. Could you please help me in fixing the issue.

JBoss Windup, version 2.4.0.Final. JBoss Forge, version 2.19.0.Final

Core rulesets: Installed: 3.0.0.CR1 Latest release: 3.0.0.CR1

The input application is large. Processing may take a very long time. Please consult the Windup User Guide for performance tips. Would you like to continue? [Y,n] Y

WARNING: No packages were set in --packages. This will cause all .jar files to be decompiled and can possibly take a long time. Check the Windup User Guide for performance tips.

Writing graph config to /tmp/windupgraph_0CrM12/TitanConfiguration.properties

Windup execution failed due to: null

java.lang.NullPointerException

at org.jboss.windup.config.metadata.RuleProviderRegistryCache.getAvailableSourceTechnologies(RuleProviderRegistryCache.java:61)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:606)

at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:87)

at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)

at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:103)

at org.jboss.windup.config.metadata.RuleProviderRegistryCache_$$_javassist_50d955d0-92f5-4f78-bb57-0f04a51398cc.getAvailableSourceTechnologies(RuleProviderRegistryCache_$$_javassist_50d955d0-92f5-4f78-bb57-0f04a51398cc.java)

at org.jboss.windup.exec.configuration.options.SourceOption.getAvailableValues(SourceOption.java:31)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:606)

at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:87)

at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)

at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:103)

at org.jboss.windup.exec.configuration.options.SourceOption_$$_javassist_e16b82c7-35d0-47f2-9371-0233e14d2423.getAvailableValues(SourceOption_$$_javassist_e16b82c7-35d0-47f2-9371-0233e14d2423.java)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:606)

at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:123)

at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)

at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:96)

at org.jboss.windup.exec.configuration.options.SourceOption_$$_javassist_3fc0c86d-3b7b-4916-8c86-51f2d7cb71bc.getAvailableValues(SourceOption_$$_javassist_3fc0c86d-3b7b-4916-8c86-51f2d7cb71bc.java)

at org.jboss.windup.bootstrap.commands.windup.GenerateCompletionDataCommand.generateCompletionData(GenerateCompletionDataCommand.java:98)

at org.jboss.windup.bootstrap.commands.windup.GenerateCompletionDataCommand.execute(GenerateCompletionDataCommand.java:47)

at org.jboss.windup.bootstrap.commands.windup.RunWindupCommand.runWindup(RunWindupCommand.java:199)

at org.jboss.windup.bootstrap.commands.windup.RunWindupCommand.execute(RunWindupCommand.java:53)

at org.jboss.windup.bootstrap.Bootstrap.executePhase(Bootstrap.java:286)

at org.jboss.windup.bootstrap.Bootstrap.run(Bootstrap.java:165)

at org.jboss.windup.bootstrap.Bootstrap.main(Bootstrap.java:95)

1. Re: Writing graph config to /tmp/windupgraph_0CrM12/TitanConfiguration.properties Windup execution failed due to: null java.lang.NullPointerException

manarh Feb 21, 2017 9:34 AM (in response to phaniramkakaraparthi)

How did you launched the docker container?

There is already 3.0.0.Final released, why are you using so old version?
Actions
2. Re: Writing graph config to /tmp/windupgraph_0CrM12/TitanConfiguration.properties Windup execution failed due to: null java.lang.NullPointerException

phaniramkakaraparthi Feb 21, 2017 9:46 AM (in response to manarh)

Hello Markel,

I launched the container using below command.

sudo docker run -it -v /var/lib/docker/data:/var/lib/docker/data:rw jboss/windup /opt/jboss/windup/bin/windup --input /var/lib/docker/data/jee-example-app-1.0.0.ear --output /var/lib/docker/data/windupreport --target eap6

Is this the issue because of the mismatch in the rule set version and Windup Version?
Actions
3. Re: Writing graph config to /tmp/windupgraph_0CrM12/TitanConfiguration.properties Windup execution failed due to: null java.lang.NullPointerException

manarh Feb 21, 2017 9:57 AM (in response to phaniramkakaraparthi)

It could be the cause. The schema changed between 2.4.0.Final and 3.0.0.Final. Are you trying it as in another thread https://developer.jboss.org/message/968993?et=watches.email.thread#968993 Byapaneni Swathi ?
Actions
4. Re: Writing graph config to /tmp/windupgraph_0CrM12/TitanConfiguration.properties Windup execution failed due to: null java.lang.NullPointerException

manarh Feb 21, 2017 10:00 AM (in response to phaniramkakaraparthi)

In mounting path you should use
-v /var/lib/docker/data:/opt/jboss/application:rw

First path is your local path you would like to mount and second after colon is the path in container and I guess there is not such path there.
Actions
5. Re: Writing graph config to /tmp/windupgraph_0CrM12/TitanConfiguration.properties Windup execution failed due to: null java.lang.NullPointerException

phaniramkakaraparthi Feb 21, 2017 10:25 AM (in response to manarh)

I tried this option as well. Got the below exception.

sudo docker run -it -v /var/lib/docker/data:/opt/jboss/application:rw jboss/windup /opt/jboss/windup/bin/windup --input /var/lib/docker/jee-example-app-1.0.0.ear --output /var/lib/docker/data/windupreport --target eap6
Using Windup at /opt/jboss/windup
> JBoss Windup, version 2.4.0.Final. JBoss Forge, version 2.19.0.Final
Core rulesets: Installed: 3.0.0.CR1 Latest release: 3.0.0.CR1
ERROR: input must exist!

but the input file is present in the path mentioned in --input
Actions
6. Re: Writing graph config to /tmp/windupgraph_0CrM12/TitanConfiguration.properties Windup execution failed due to: null java.lang.NullPointerException

phaniramkakaraparthi Feb 21, 2017 11:00 AM (in response to phaniramkakaraparthi)

Is there any documentation available where we can check how to get windup reports by using docker. Because it's been hard to generate reports with the documentation available in the docker hub. It would be very great if you can help in providing a working example of running windup image in docker(linux), with launch command
Actions
7. Re: Writing graph config to /tmp/windupgraph_0CrM12/TitanConfiguration.properties Windup execution failed due to: null java.lang.NullPointerException

jsightler Feb 21, 2017 11:13 AM (in response to phaniramkakaraparthi)

The command looks ok to me, and a similar one (just different paths) works for me locally.

The issue seems to be that the rules are somehow on version 3, but the core windup version is on version 2. Perhaps you can pull down the docker image again? It seems that the core problem here is just the mismatched rules versions.
Actions
8. Re: Writing graph config to /tmp/windupgraph_0CrM12/TitanConfiguration.properties Windup execution failed due to: null java.lang.NullPointerException

manarh Feb 22, 2017 3:36 AM (in response to phaniramkakaraparthi)
Hey Phaniram,
the logic is the same as without using docker. If you don't use --output option the report will be generated next to application input - so in the mounted volume of an input application.

I use the following command for running the docker and it is not very different from docker hub README:
export REPORT=<whatever_absolute_path_on_host> # example of our sample application export APP_NAME=jee-example-app-1.0.0.ear docker run -ti --rm -v $REPORTS:/opt/jboss/reports -v $(pwd):/opt/jboss/application jboss/windup:2.4.0.Final /opt/jboss/windup/bin/windup --input application/$APP_NAME --output /opt/jboss/reports --target eap --batchMode
where mounting special volume for generated reports is the additional thing from README. I will enhance the optional documentation based on your feedback.

The catch is that all official jboss docker images uses jboss user with id 1000 in docker container, so you need to have use user account with id=1000 on your local host.
The alternative way how to not use user with id=1000 is to build new windup docker image for your local purpose which wraps the official windup docker image from jboss.

Like the following Dockerfile:
FROM jboss/windup:2.4.0.Final MAINTAINER Local user <user@domain.com> USER root RUN groupadd -r mylocaluser -g <mylocal_groupId> && useradd -u <mylocal_userId_different_than_1000> -r -g mylocalgroup -m -d /opt/jboss -s /sbin/nologin -c "JBoss user for mylocaluser" <mylocaluser> && chown -R <mylocaluser>:<mylocalgroup> /opt/jboss && \ chmod 755 /opt/jboss USER mylocaluser # Set the default command to run on boot # This will boot the Windup CLI CMD ["/opt/jboss/windup/bin/windup"]
Actions

Go to original post