9:33 p.m.
hi,
anybody can help me here?
I'm runing windup against a monster .ear file from JBossAS6, and when it comes to the
SOAP5 rules it stops processing (something like rule 107x of 12xx), and even after the
whole night running, no report.
Is there a way to:
* Know what is happening? If something is running or not?
* disable some rules?
Thanks
BTW: I'm using Windup 2.1.0.Final
Posted by forums
Original post: https://developer.jboss.org/message/918962#918962
6:08 a.m.
This was reproduced on a simple example and consists of 2 problems at the end (freezing
and then problem with generating report).
For the first one, there is already an issue WINDUP-516
(https://issues.jboss.org/browse/WINDUP-516) that I am working on now.
Posted by forums
Original post: https://developer.jboss.org/message/919329#919329
1:38 a.m.
Hello Matej,
I am having issues with the Windup tool run. It produces an error with my soa5 esb
project.
Please find the attached log trace. It does say memory heap issue but i have tons of
memory on my PC
Could you please help me out here
[bin]$ windup-migrate-app --sourceMode true --input C:\online_Dispatcher --outpu
t C:\results
Overwrite all contents of "C:\results" (anything already in the directory will
b
e deleted)? [y/N] y
Properties: {index.search.directory=C:\results\graph\graphsearch, cache.db-cache
-time=0, cache.db-cache=true, index.search.backend=lucene, cache.db-cache-size=0
.05, cache.db-cache-clean-wait=0, storage.backend=berkeleyje, storage.directory=
C:\results\graph\titangraph, storage.berkeleydb.cache-percentage=1}
Using user rules dir: C:\Users\pooja.malini\.windup\rules
Using user rules dir: C:\windup-distribution-2.1.0.A-offline\windup-distribution
-2.1.0.A\rules
***INFO*** Executing Rules: [0/1199] ...
***INFO*** Executing Rules: :class org.jboss.windup.config.phase.Implicit - org.
jboss.windup.rules.apps:rules-java.JavaFileMappingRuleProvider [Uncategorized] o
rg.jboss.windup.rules.files.FileMapping_8dfa6153-f2ba-419e-9bc5-74250b277c6e
[0/1199] ...
***INFO*** Executing Rules: :class org.jboss.windup.config.phase.Implicit - org.
jboss.windup.rules.apps:rules-java.JavaFileMappingRuleProvider [Uncategorized] o
rg.jboss.windup.rules.files.FileMapping_9a582219-d2fa-4b06-ae7d-0c6a7ff3034a
[1/1199] ...
***INFO*** Executing Rules: :class org.jboss.windup.config.phase.Initialization
- org.jboss.windup.rules.apps:rules-java.CopyJavaConfigToGraphRuleProvider [Unca
tegorized] GeneratedID_w:apps:rules-java.CopyJavaConfigToGraphRuleProvider_1
[2/1199] ...
***INFO*** Executing Rules: :class org.jboss.windup.config.phase.Initialization
- org.jboss.windup.rules.apps:rules-java-archives.IgnoredArchivesConfigLoadingRu
leProvider [Uncategorized] GeneratedID_w:apps:rules-java-archives.IgnoredArchive
sConfigLoadingRuleProvider_1 [3/1199] ...
***INFO*** Executing Rules: :class org.jboss.windup.config.phase.Initialization
- org.jboss.windup.rules.apps:rules-java-archives.ArchiveIdentificationConfigLoa
dingRuleProvider [Uncategorized] GeneratedID_w:apps:rules-java-archives.ArchiveI
dentificationConfigLoadingRuleProvider_1 [4/1199] ...
***ERROR*** Error while executing 'Windup Migrate App'
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoad
erInterceptor.java:87)
at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java
:42)
at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoad
erInterceptor.java:103)
at org.jboss.windup.exec.WindupProcessorImpl_$$_javassist_80f05268-d79f-
4dfd-85bf-ef4b7fe2c9e5.execute(WindupProcessorImpl_$$_javassist_80f05268-d79f-4d
fd-85bf-ef4b7fe2c9e5.java)
at org.jboss.windup.ui.WindupCommand.execute(WindupCommand.java:243)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoad
erInterceptor.java:87)
at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java
:42)
at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoad
erInterceptor.java:103)
at org.jboss.windup.ui.WindupCommand_$$_javassist_a51b3fee-579f-4dce-aab
c-b28023f2fb88.execute(WindupCommand_$$_javassist_a51b3fee-579f-4dce-aabc-b28023
f2fb88.java)
at org.jboss.forge.addon.ui.impl.controller.SingleCommandControllerImpl.
execute(SingleCommandControllerImpl.java:90)
at org.jboss.forge.addon.shell.aesh.CommandAdapter.execute(CommandAdapte
r.java:74)
at org.jboss.aesh.console.AeshConsoleImpl$AeshConsoleCallbackImpl.execut
e(AeshConsoleImpl.java:325)
at org.jboss.aesh.console.AeshProcess.run(AeshProcess.java:40)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.
java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOfRange(Arrays.java:2694)
at java.lang.String.<init>(String.java:203)
at java.lang.String.substring(String.java:1913)
at org.apache.commons.lang.StringUtils.splitWorker(StringUtils.java:2510
)
at org.apache.commons.lang.StringUtils.split(StringUtils.java:2137)
at org.jboss.windup.rules.apps.java.archives.identify.IdentifiedArchives
.addMappingsFrom(IdentifiedArchives.java:54)
at org.jboss.windup.rules.apps.java.archives.config.ArchiveIdentificatio
nConfigLoadingRuleProvider$1$1.visit(ArchiveIdentificationConfigLoadingRuleProvi
der.java:55)
at org.jboss.windup.rules.apps.java.archives.config.ArchiveIdentificatio
nConfigLoadingRuleProvider$1$1.visit(ArchiveIdentificationConfigLoadingRuleProvi
der.java:48)
at org.jboss.windup.util.file.FileVisit.visit(FileVisit.java:34)
at org.jboss.windup.rules.apps.java.archives.config.ArchiveIdentificatio
nConfigLoadingRuleProvider$1.perform(ArchiveIdentificationConfigLoadingRuleProvi
der.java:66)
at org.jboss.windup.config.operation.GraphOperation.perform(GraphOperati
on.java:24)
at org.ocpsoft.rewrite.config.RuleBuilder.perform(RuleBuilder.java:168)
at org.jboss.windup.config.RuleSubset.perform(RuleSubset.java:239)
at org.jboss.windup.exec.WindupProcessorImpl.execute(WindupProcessorImpl
.java:115)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoad
erInterceptor.java:87)
at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java
:42)
at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoad
erInterceptor.java:103)
at org.jboss.windup.exec.WindupProcessorImpl_$$_javassist_80f05268-d79f-
4dfd-85bf-ef4b7fe2c9e5.execute(WindupProcessorImpl_$$_javassist_80f05268-d79f-4d
fd-85bf-ef4b7fe2c9e5.java)
at org.jboss.windup.ui.WindupCommand.execute(WindupCommand.java:243)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoad
erInterceptor.java:87)
at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java
:42)
at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoad
erInterceptor.java:103)
at org.jboss.windup.ui.WindupCommand_$$_javassist_a51b3fee-579f-4dce-aab
c-b28023f2fb88.execute(WindupCommand_$$_javassist_a51b3fee-579f-4dce-aabc-b28023
f2fb88.java)
at org.jboss.forge.addon.ui.impl.controller.SingleCommandControllerImpl.
execute(SingleCommandControllerImpl.java:90)
[bin]$
Posted by forums
Original post: https://developer.jboss.org/message/920779#920779
2:01 a.m.
Hello Pooja,
I surely will try to help you and will contact colleagues in your timezone to address this
issue.
Can you please try the most current version firstly located in windup/windup · GitHub
(https://github.com/windup/windup) ? It will tell us if the problem is still there.
You need to clone it (git clone windup/windup · GitHub
(https://github.com/windup/windup)), compile it (mvn clean install -DskipTests) and then
unzip the windup that will be located in the windup/dist/target directory (that is the
most current version we have).
The ArchiveIdentificationConfigLoadingRuleProvider that causes this was introduced
recently (1 month?), so there is also other option which is to try slightly older windup
version instead.
Posted by forums
Original post: https://developer.jboss.org/message/920781#920781
2:11 a.m.
Hi Matej,
I am using windup-distribution-2.1.0.A which I believe is the latest version?
Posted by forums
Original post: https://developer.jboss.org/message/920783#920783
2:24 a.m.
I meant the 2.2.0-SNAPSHOT, e.g the latest windup version used within development. It is
default in the master branch, right after cloning the git repository.
I don't think it will resolve the issue, but it may be worth a try. I think the
problem is specific to the application you are running windup on (it may contain some
specific files/configuration that causes this behaviour)
Posted by forums
Original post: https://developer.jboss.org/message/920784#920784
2:31 a.m.
Oh OK thanks Matej.
But my application is very very small. Doesnt have any JAVA files. It only has a
jboss-esb.xml and few xml schemas.
What happens if the 2.2.0 snapshot doesnt resolve my issue? Could you help me out with
next steps please?
Posted by forums
Original post: https://developer.jboss.org/message/920785#920785
2:45 a.m.
Sure, I'm sorry that you experience this problem with such small application then. We
have two options here.
1. You may try older version that will lack some functionality introduced recently, but
you will have the result immediately. We however do huge steps each day
{emoticon:class=jive_macro
jive_emote|src=https://static.jboss.org/developer/6.0.3.60ddddd/images/em...
The previous versions you may find here: Releases · windup/windup · GitHub
(https://github.com/windup/windup/releases)
2. You may submit new issue (that this definitely is) here: WindUp - JBoss Issue Tracker
(https://issues.jboss.org/browse/WINDUP/) (the create button is on the top) along with
providing the application and marking the issue as RH internal. I think in order to fix
this we will need that application to see what exactly happens here. This will however
take few days to reproduce&fix.
Posted by forums
Original post: https://developer.jboss.org/message/920787#920787
4:37 a.m.
Thanks Matej! Which one do you suggest I use please?
Posted by forums
Original post: https://developer.jboss.org/message/920800#920800
5:07 a.m.
I suggest opening new JIRA, because it will help us investigate what's going on here
and it will give you the most updated functionality. We don't have any such problem
when we try windup on our test projects.
Posted by forums
Original post: https://developer.jboss.org/message/920806#920806
3:35 a.m.
I believe that the default max heap on WIndows is very small. Perhaps try running it with
a larger max heap?
set MAX_MEMORY=2048m
windup.bat
Posted by forums
Original post: https://developer.jboss.org/message/920793#920793
3:56 a.m.
I did try to increase the space to 4096m no luck {emoticon:class=jive_macro
jive_emote|src=https://static.jboss.org/developer/6.0.3.60ddddd/images/em...
Posted by forums
Original post: https://developer.jboss.org/message/920797#920797
3586
days inactive
3603
days old
11 comments
1 participants
participants (1)
-
windup-users＠lists.jboss.org