My client is the last Windows System in my little universe. Due to some
constraints with my customers I have to deal with it for the time being.
The switches, Vicente has provided, solved the problem for me so far.
But my "inner monk" is still not satisfied, because practical no one
knows of
Oh, wow, yes this did it. After using these switches, the response times
in dev mode are getting down to the values I'm used to have with TomEE
8.0.6.
Thank you very much.
I surely will not use this in production, my production targets are
solely linux system, because I refuse to admin/manage
Just when I think I've started to learn everything about the JVM,
someone posts some strange esoteric JVM switch... I've never even seen
those before. More details about what they do here:
https://bugs.openjdk.org/browse/JDK-8301001
I also don't know jack about crap about Windows, but if someone
Great news! (though I am not a Windows user anymore).
You should be able to build TomEE on Windows, too. If that does not
work out-of-the-box, you could try to build within a docker container
or via git-bash in Windows
(I am not 100% sure a Windows build will work out of the box)
I agree, that
I want through this, now I remember. Try with these system switches
-Dsun.io.useCanonCaches=true -Dsun.io.useCanonPrefixCache=true
Dont use this in production, be aware.
We ended up removing these flash and using a dirty trick with tomcat
DirResourcesSet
I can send you this tonight. Try the
I have a first result on this issue:
The problem does not occur if TomEE is running on Linux. I've tested my
own built 8.0.8, a freshly extracted 8.0.8 and 8.0.15 from the releases,
and none of them showed the dev mode performance problem.
Using TomEE 8.0.8 on Windows does show the dev mode
Thanks Richard (and Vicente),
I've changed to JDK 8 and now the builds are successful (both 8.0.6 and
8.0.8).
I'll script me some test scripts to ease the build, run and test for
every bisect step.
A build needs around 3 to 4 minutes. Running a test with my application
will need some manual
Perfect,
Mind you these errors occurred in the process of migrating multiple apps
from Tomee 8 to Tomee 9.
So if the app needs to be configured differently in that environment,
please send me a PR on the repo.
Met Vriendelijke Groet / With Kind Regards
Bart van Leeuwen
From: "Jean-Louis
Thanks for reporting and reproducing the issue. It definitely helps us
Le ven. 27 oct. 2023, 11:36, Bart van Leeuwen
a écrit :
> Hi,
>
> I've created a simple testcase which creates a war file which when
> deployed for a second time with a different name generates the error
>
>
Hi,
you need Java/JDK 8 to build TomEE 8.
The Maven command is
mvn --fail-at-end clean install -pl tomee/apache-tomee -am -
Dfile.encoding=UTF-8 -DskipTests=true
You will find the tar.gz/zip in ./tomee/apache-tomee/target
Gruß
Richard
P.S. 8.0.7 is here:
You need java 8 to compile tomee 8. Corba packages were removed in jdk 11.
Try it
On Fri, Oct 27, 2023 at 10:51 AM Jens Zurawski wrote:
> Hi Richard,
>
> to identify the "bad" version was easy. I didn't find a 8.0.7 release on
> the download page, so I started with 8.0.8. And this version
Hi,
I've created a simple testcase which creates a war file which when
deployed for a second time with a different name generates the error
https://github.com/semanticfire/tomee-test
Take a Tomee Plus 9.1.0 and copy test.war to webapps/test1.war and
webapps/test2.war
The deployment of
Hi Richard,
to identify the "bad" version was easy. I didn't find a 8.0.7 release on
the download page, so I started with 8.0.8. And this version already has
the slow dev mode. So for my problem I can say:
good: 8.0.6
bad: 8.0.8
Now, I think, I need a little help from you. I tried to build a
13 matches
Mail list logo
