Tomcat 9.0.93 Patching | Error- A fatal error has been detected by the Java Runtime Environment | Problematic frame:sigar-amd64-winnt.dll+0x14ed4

[Man Mohan]

Hi Team,


Recently I was patching one of my Tomcat server from 9.0.88 to 9.0.90/93 and 
then  we are getting below issue while starting the tomcat after the patching 
and it is generating mdmp file after each start and  after that services got 
stopped.

OS: Window
JAVA: 1.8.421
Tomcat : 9.0.90/93 (both having issue)

Error:
# A fatal error has been detected by the Java Runtime Environment:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc005) at pc=0x10014ed4, pid=7624, 
tid=0x0ad0
#
# JRE version: Java(TM) SE Runtime Environment (8.0_421) (build 1.8.0_421-b09)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.421-b09 mixed mode 
windows-amd64 )
# Problematic frame:
# C  [sigar-amd64-winnt.dll+0x14ed4]
#
# Core dump written. Default location: C:\Program Files\Apache Software 
Foundation\Tomcat 9.0\hs_err_pid7624.mdmp
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.

Attached the full error file.

We have not patching before many time but we are facing this issue only this 
time , Requesting your help on this as this is stopping us to patch our 
environment with latest one.

Regards
Man Mohan
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc005) at pc=0x10014ed4, pid=7624, 
tid=0x0ad0
#
# JRE version: Java(TM) SE Runtime Environment (8.0_421) (build 1.8.0_421-b09)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.421-b09 mixed mode 
windows-amd64 )
# Problematic frame:
# C  [sigar-amd64-winnt.dll+0x14ed4]
#
# Core dump written. Default location: C:\Program Files\Apache Software 
Foundation\Tomcat 9.0\hs_err_pid7624.mdmp
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

---  T H R E A D  ---

Current thread (0x009c7313e000):  JavaThread "ServerThread" daemon 
[_thread_in_native, id=2768, stack(0x009c7999,0x009c79a9)]

siginfo: ExceptionCode=0xc005, reading address 0x7a250d58

Registers:
RAX=0x7a250c20, RBX=0x009c79ac74f8, RCX=0x009c7313e200, 
RDX=0x009c79a8d690
RSP=0x009c79a8d4d0, RBP=0x009c79a8d670, RSI=0x00200021, 
RDI=0x009ad86083d4
R8 =0x0062, R9 =0x009bfb861378, R10=0x023c, 
R11=0x7ffc39760c3c
R12=0x0128, R13=0x009c79ac74f0, R14=0x009c79a8d698, 
R15=0x009c7313e000
RIP=0x10014ed4, EFLAGS=0x00010202

Top of Stack: (sp=0x009c79a8d4d0)
0x009c79a8d4d0:   009c7313e200 009c79a8d690
0x009c79a8d4e0:   009c7313e000 
0x009c79a8d4f0:   7a250c20 7ffc3903270c
0x009c79a8d500:   009ad86083d4 10018291
0x009c79a8d510:   009c7313e200 009c79a8d690
0x009c79a8d520:   00200021 009c7313e000
0x009c79a8d530:   009c79a8d698 009c79ac74f0
0x009c79a8d540:   009c79ac74f8 0128
0x009c79a8d550:   009c7313e000 0128
0x009c79a8d560:   009c79a8d670 7ffc39006272
0x009c79a8d570:   009c79a8d5a0 009c7313e000
0x009c79a8d580:   009c79ac74f8 009c6f211e08
0x009c79a8d590:   009c79ac74f8 009c7313e000
0x009c79a8d5a0:   009c79ac74f8 009c7313e000
0x009c79a8d5b0:   009ad86083d4 00200021
0x009c79a8d5c0:   009c79ac74f8 009ad8619e86 

Instructions: (pc=0x10014ed4)
0x10014eb4:   7c 24 20 00 75 15 48 8d 15 df 58 04 00 48 8b 4c
0x10014ec4:   24 40 e8 45 00 00 00 33 c0 eb 32 48 8b 44 24 20
0x10014ed4:   83 b8 38 01 00 00 00 74 1f 48 8b 44 24 20 44 8b
0x10014ee4:   80 38 01 00 00 48 8b 54 24 20 48 8b 4c 24 40 e8 


Register to memory mapping:

RAX=0x7a250c20 is an unknown value
RBX={method} {0x009c79ac7500} 'gather' '(Lorg/hyperic/sigar/Sigar;)V' in 
'org/hyperic/sigar/Cpu'
RCX=0x009c7313e200 is an unknown value
RDX=0x009c79a8d690 is pointing into the stack for thread: 0x009c7313e000
RSP=0x009c79a8d4d0 is pointing into the stack for thread: 0x009c7313e000
RBP=0x009c79a8d670 is pointing into the stack for thread: 0x009c7313e000
RSI=0x00200021 is an unknown value
RDI=0x009ad86083d4 is at code_begin+2292 in an Interpreter codelet
invoke return entry points  [0x009ad8607ae0, 0x009ad86084c0]  2528 bytes
R8 =0x0062 is an unknown value
R9 =0x009bfb861378 is an oop
org.hyperic.sigar.Sigar 
 - klass: 'org/hyperic/sigar/Sigar'
 -  fields (total size 8 words):
 - 'longSigarWrapper' 'J' @16  0 (0 0)
 - 'sigarWrapper' 'I' @24  2049248288 (7a250c20)
 - private 'open' 'Z' @28  true
 - private 'mounts' 'Lorg

Re: Tomcat 9.0.93 Patching | Error- A fatal error has been detected by the Java Runtime Environment | Problematic frame:sigar-amd64-winnt.dll+0x14ed4

[Mark Thomas]

Not a Tomcat issue. You need to contact whoever provided the file:

C:\Program Files\Apache Software Foundation\Tomcat 
9.0\webapps\ROOT\WEB-INF\lib\sigar-amd64-winnt.dll


Mark


On 03/09/2024 08:33, Man Mohan wrote:

Hi Team,

Recently I was patching one of my Tomcat server from *9.0.88 to 
9.0.90/93* and then  we are getting below issue while starting the 
tomcat after the patching and it is generating mdmp file after each 
start and  after that services got stopped.


*OS: Window *

*JAVA: 1.8.421*

*Tomcat : 9.0.90/93* (both having issue)

Error:

# A fatal error has been detected by the Java Runtime Environment:

#

#  EXCEPTION_ACCESS_VIOLATION (0xc005) at pc=0x10014ed4, 
pid=7624, tid=0x0ad0


#

# JRE version: Java(TM) SE Runtime Environment (8.0_421) (build 
1.8.0_421-b09)


# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.421-b09 mixed mode 
windows-amd64 )


# Problematic frame:

*# C  [sigar-amd64-winnt.dll+0x14ed4]*

*#*

# Core dump written. Default location: C:\Program Files\Apache Software 
Foundation\Tomcat 9.0\hs_err_pid7624.mdmp


#

# If you would like to submit a bug report, please visit:

#   http://bugreport.java.com/bugreport/crash.jsp

# The crash happened outside the Java Virtual Machine in native code.

# See problematic frame for where to report the bug.

Attached the full error file.

We have not patching before many time but we are facing this issue only 
this time , Requesting your help on this as this is stopping us to patch 
our environment with latest one.


Regards

Man Mohan



-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: Tomcat 9.0.93 Patching | Error- A fatal error has been detected by the Java Runtime Environment | Problematic frame:sigar-amd64-winnt.dll+0x14ed4

[Man Mohan]

Hi Mark


Thanks for the reply but same application is working fine with Tomcat 9.0.88.

Regards
Man Mohan

-Original Message-
From: Mark Thomas  
Sent: 03 September 2024 18:29
To: Tomcat Users List 
Subject: Re: Tomcat 9.0.93 Patching | Error- A fatal error has been detected by 
the Java Runtime Environment | Problematic frame:sigar-amd64-winnt.dll+0x14ed4

Not a Tomcat issue. You need to contact whoever provided the file:

C:\Program Files\Apache Software Foundation\Tomcat 
9.0\webapps\ROOT\WEB-INF\lib\sigar-amd64-winnt.dll

Mark


On 03/09/2024 08:33, Man Mohan wrote:
> Hi Team,
> 
> Recently I was patching one of my Tomcat server from *9.0.88 to
> 9.0.90/93* and then  we are getting below issue while starting the 
> tomcat after the patching and it is generating mdmp file after each 
> start and  after that services got stopped.
> 
> *OS: Window *
> 
> *JAVA: 1.8.421*
> 
> *Tomcat : 9.0.90/93* (both having issue)
> 
> Error:
> 
> # A fatal error has been detected by the Java Runtime Environment:
> 
> #
> 
> #  EXCEPTION_ACCESS_VIOLATION (0xc005) at pc=0x10014ed4, 
> pid=7624, tid=0x0ad0
> 
> #
> 
> # JRE version: Java(TM) SE Runtime Environment (8.0_421) (build
> 1.8.0_421-b09)
> 
> # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.421-b09 mixed mode
> windows-amd64 )
> 
> # Problematic frame:
> 
> *# C  [sigar-amd64-winnt.dll+0x14ed4]*
> 
> *#*
> 
> # Core dump written. Default location: C:\Program Files\Apache 
> Software Foundation\Tomcat 9.0\hs_err_pid7624.mdmp
> 
> #
> 
> # If you would like to submit a bug report, please visit:
> 
> #   http://bugreport.java.com/bugreport/crash.jsp
> 
> # The crash happened outside the Java Virtual Machine in native code.
> 
> # See problematic frame for where to report the bug.
> 
> Attached the full error file.
> 
> We have not patching before many time but we are facing this issue 
> only this time , Requesting your help on this as this is stopping us 
> to patch our environment with latest one.
> 
> Regards
> 
> Man Mohan
> 
> 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat 9.0.93 Patching | Error- A fatal error has been detected by the Java Runtime Environment | Problematic frame:sigar-amd64-winnt.dll+0x14ed4

[Tim Funk]

"sigar-amd64-winnt.dll" is triggering the error. The details will be
in the core dump.

The vendor which supports "sigar-amd64-winnt.dll" will need to fix it.
Based on the release revisions, I suspect the DLL is using a reference
to a request or response object *after* the request was already completed.
This is not allowed since 9.0.90. In particular - see the notes about
"RECYCLE_FACADES" here
https://tomcat.apache.org/tomcat-9.0-doc/changelog.html


An alternative is removing "sigar-amd64-winnt.dll" from lib (but I suspect
the application will be broken)

-Tim

On Tue, Sep 3, 2024 at 7:08 AM Man Mohan 
wrote:

> Hi Mark
>
>
> Thanks for the reply but same application is working fine with Tomcat
> 9.0.88.
>
> Regards
> Man Mohan
>
> -Original Message-
> From: Mark Thomas 
> Sent: 03 September 2024 18:29
> To: Tomcat Users List 
> Subject: Re: Tomcat 9.0.93 Patching | Error- A fatal error has been
> detected by the Java Runtime Environment | Problematic
> frame:sigar-amd64-winnt.dll+0x14ed4
>
> Not a Tomcat issue. You need to contact whoever provided the file:
>
> C:\Program Files\Apache Software Foundation\Tomcat
> 9.0\webapps\ROOT\WEB-INF\lib\sigar-amd64-winnt.dll
>
> Mark
>
>
> On 03/09/2024 08:33, Man Mohan wrote:
> > Hi Team,
> >
> > Recently I was patching one of my Tomcat server from *9.0.88 to
> > 9.0.90/93* and then  we are getting below issue while starting the
> > tomcat after the patching and it is generating mdmp file after each
> > start and  after that services got stopped.
> >
> > *OS: Window *
> >
> > *JAVA: 1.8.421*
> >
> > *Tomcat : 9.0.90/93* (both having issue)
> >
> > Error:
> >
> > # A fatal error has been detected by the Java Runtime Environment:
> >
> > #
> >
> > #  EXCEPTION_ACCESS_VIOLATION (0xc005) at pc=0x10014ed4,
> > pid=7624, tid=0x0ad0
> >
> > #
> >
> > # JRE version: Java(TM) SE Runtime Environment (8.0_421) (build
> > 1.8.0_421-b09)
> >
> > # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.421-b09 mixed mode
> > windows-amd64 )
> >
> > # Problematic frame:
> >
> > *# C  [sigar-amd64-winnt.dll+0x14ed4]*
> >
> > *#*
> >
> > # Core dump written. Default location: C:\Program Files\Apache
> > Software Foundation\Tomcat 9.0\hs_err_pid7624.mdmp
> >
> > #
> >
> > # If you would like to submit a bug report, please visit:
> >
> > #   http://bugreport.java.com/bugreport/crash.jsp
> >
> > # The crash happened outside the Java Virtual Machine in native code.
> >
> > # See problematic frame for where to report the bug.
>
>

RE: Tomcat 9.0.93 Patching | Error- A fatal error has been detected by the Java Runtime Environment | Problematic frame:sigar-amd64-winnt.dll+0x14ed4

[Man Mohan]

Hi Tim


Thanks for the reply let me check the same with the app team.

Regards
Man Mohan

-Original Message-
From: Tim Funk  
Sent: 03 September 2024 19:48
To: Tomcat Users List 
Subject: Re: Tomcat 9.0.93 Patching | Error- A fatal error has been detected by 
the Java Runtime Environment | Problematic frame:sigar-amd64-winnt.dll+0x14ed4

"sigar-amd64-winnt.dll" is triggering the error. The details will be in the 
core dump.

The vendor which supports "sigar-amd64-winnt.dll" will need to fix it.
Based on the release revisions, I suspect the DLL is using a reference to a 
request or response object *after* the request was already completed.
This is not allowed since 9.0.90. In particular - see the notes about 
"RECYCLE_FACADES" here https://tomcat.apache.org/tomcat-9.0-doc/changelog.html


An alternative is removing "sigar-amd64-winnt.dll" from lib (but I suspect the 
application will be broken)

-Tim

On Tue, Sep 3, 2024 at 7:08 AM Man Mohan 
wrote:

> Hi Mark
>
>
> Thanks for the reply but same application is working fine with Tomcat 
> 9.0.88.
>
> Regards
> Man Mohan
>
> -Original Message-
> From: Mark Thomas 
> Sent: 03 September 2024 18:29
> To: Tomcat Users List 
> Subject: Re: Tomcat 9.0.93 Patching | Error- A fatal error has been 
> detected by the Java Runtime Environment | Problematic
> frame:sigar-amd64-winnt.dll+0x14ed4
>
> Not a Tomcat issue. You need to contact whoever provided the file:
>
> C:\Program Files\Apache Software Foundation\Tomcat 
> 9.0\webapps\ROOT\WEB-INF\lib\sigar-amd64-winnt.dll
>
> Mark
>
>
> On 03/09/2024 08:33, Man Mohan wrote:
> > Hi Team,
> >
> > Recently I was patching one of my Tomcat server from *9.0.88 to
> > 9.0.90/93* and then  we are getting below issue while starting the 
> > tomcat after the patching and it is generating mdmp file after each 
> > start and  after that services got stopped.
> >
> > *OS: Window *
> >
> > *JAVA: 1.8.421*
> >
> > *Tomcat : 9.0.90/93* (both having issue)
> >
> > Error:
> >
> > # A fatal error has been detected by the Java Runtime Environment:
> >
> > #
> >
> > #  EXCEPTION_ACCESS_VIOLATION (0xc005) at pc=0x10014ed4, 
> > pid=7624, tid=0x0ad0
> >
> > #
> >
> > # JRE version: Java(TM) SE Runtime Environment (8.0_421) (build
> > 1.8.0_421-b09)
> >
> > # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.421-b09 mixed mode
> > windows-amd64 )
> >
> > # Problematic frame:
> >
> > *# C  [sigar-amd64-winnt.dll+0x14ed4]*
> >
> > *#*
> >
> > # Core dump written. Default location: C:\Program Files\Apache 
> > Software Foundation\Tomcat 9.0\hs_err_pid7624.mdmp
> >
> > #
> >
> > # If you would like to submit a bug report, please visit:
> >
> > #   http://bugreport.java.com/bugreport/crash.jsp
> >
> > # The crash happened outside the Java Virtual Machine in native code.
> >
> > # See problematic frame for where to report the bug.
>
>

Re: How to resolve 403 forbidden error in Tomcat level

[jagadish sahu]

Hi Team,

Any update on this?

Thanks,
Jagadish

On Fri, Aug 30, 2024 at 8:22 PM jagadish sahu 
wrote:

> Hi Christopher and Team,
>
> Please find the attached text screenshot as you requested.
>
> Thanks,
> Jagadish
>
>
>
>
> On Fri, Aug 30, 2024 at 3:37 AM Christopher Schultz <
> ch...@christopherschultz.net> wrote:
>
>> Jadgish,
>>
>> This list does not accept image attachments. We are not seeing what you
>> are posting. Please post text-only.
>>
>> -chris
>>
>> On 8/29/24 11:01, jagadish sahu wrote:
>> > Hi Team and Christopher,
>> >
>> > We have attached a 403 error screenshot with full information.
>> > The error seems to be generated from Tomcat level.
>> >
>> > We don't have any changes in the java code and our application is
>> > working as expected in Tomcat 9.0.14.
>> >
>> > After upgrading to latest version Tomcat,we have been facing this
>> > issue(Error communicating with web server status:403)
>> >
>> > Please find attached screenshot for authentication and web.xml.
>> >
>> > It would be great help if you provide a solution for this.
>> >
>> > Thanks,
>> > Jagadish
>> >
>> >
>> >
>> > On Thu, Aug 29, 2024 at 6:30 PM Christopher Schultz
>> > mailto:ch...@christopherschultz.net>>
>> wrote:
>> >
>> > Jagdesh,
>> >
>> > On 8/29/24 06:29, jagadish sahu wrote:
>> >  > We have tested our application in Apache tomcat 9.0.14. It is
>> > working as
>> >  > expected, After upgrading from 9.0.14 to the latest versions it
>> > is not
>> >  > working.
>> >  >
>> >  >When we leave the session for 30 mins, we will get some
>> > warning like
>> >  > due to an inactive session, you can click on Ok to continue the
>> > session,
>> >  > after clicking Ok we are getting a 403 error message (attached
>> >  > screenshot for your reference).
>> >
>> > Your screenshot has been stripped from the list. Is this an
>> > application-generated 403 or one from Tomcat?
>> >
>> >  > The correct functionality is it should not get any error message,
>> > after
>> >  > clicking waring message it should redirect to login page again,
>> > but in
>> >  > the latest version of tomcat its not working, so we are
>> > contacting you
>> >  > people.
>> >  >
>> >  > Please provide a solution/ workaround for this issue.
>> >
>> > What kind of authentication are you using? What kind of login
>> mechanism
>> > are you using -- e.g. FORM versus HTTP BASIC/DIGEST, etc.?
>> >
>> > Can you post the relevant parts of your web.xml?
>> >
>> > -chris
>> >
>> >
>>  -
>> > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>> > 
>> > For additional commands, e-mail: users-h...@tomcat.apache.org
>> > 
>> >
>> >
>> >
>> > -
>> > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>> > For additional commands, e-mail: users-h...@tomcat.apache.org
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>> For additional commands, e-mail: users-h...@tomcat.apache.org
>>
>>

Re: How to resolve 403 forbidden error in Tomcat level

[Sebastian Trost]

Jadgish,

please don't attach any .doc- or similar files. Don't send screenshots 
of text. Send texts within the body of the email.


Sebastian

On 03.09.2024 17:05, jagadish sahu wrote:

Hi Team,

Any update on this?

Thanks,
Jagadish

On Fri, Aug 30, 2024 at 8:22 PM jagadish sahu 
wrote:


Hi Christopher and Team,

Please find the attached text screenshot as you requested.

Thanks,
Jagadish




On Fri, Aug 30, 2024 at 3:37 AM Christopher Schultz <
ch...@christopherschultz.net> wrote:


Jadgish,

This list does not accept image attachments. We are not seeing what you
are posting. Please post text-only.

-chris

On 8/29/24 11:01, jagadish sahu wrote:

Hi Team and Christopher,

We have attached a 403 error screenshot with full information.
The error seems to be generated from Tomcat level.

We don't have any changes in the java code and our application is
working as expected in Tomcat 9.0.14.

After upgrading to latest version Tomcat,we have been facing this
issue(Error communicating with web server status:403)

Please find attached screenshot for authentication and web.xml.

It would be great help if you provide a solution for this.

Thanks,
Jagadish



On Thu, Aug 29, 2024 at 6:30 PM Christopher Schultz
mailto:ch...@christopherschultz.net>>

wrote:

 Jagdesh,

 On 8/29/24 06:29, jagadish sahu wrote:
  > We have tested our application in Apache tomcat 9.0.14. It is
 working as
  > expected, After upgrading from 9.0.14 to the latest versions it
 is not
  > working.
  >
  >When we leave the session for 30 mins, we will get some
 warning like
  > due to an inactive session, you can click on Ok to continue the
 session,
  > after clicking Ok we are getting a 403 error message (attached
  > screenshot for your reference).

 Your screenshot has been stripped from the list. Is this an
 application-generated 403 or one from Tomcat?

  > The correct functionality is it should not get any error message,
 after
  > clicking waring message it should redirect to login page again,
 but in
  > the latest version of tomcat its not working, so we are
 contacting you
  > people.
  >
  > Please provide a solution/ workaround for this issue.

 What kind of authentication are you using? What kind of login

mechanism

 are you using -- e.g. FORM versus HTTP BASIC/DIGEST, etc.?

 Can you post the relevant parts of your web.xml?

 -chris



  -

 To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 
 For additional commands, e-mail: users-h...@tomcat.apache.org
 



-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org





-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Migration of Spring MVC 4 app to Spring MVC 6

[charliedidonato]

I am migrating a Spring MVC app from 4.x to 6.x so I am going from Tomcat
9.1 Java 8 to Tomcat 10.1 Java 17.

I noticed that in the migration steps on the Tomcat site that there is a
tool to help with the javax to Jakarta package conversions

 

I have downloaded the migration tool from Github
https://github.com/apache/tomcat-jakartaee-migration

I currently have 2 versions of Java on my machine.  Java 8 (Oracle) and Java
17 (Open JDK)

 

And am trying to build it and am getting the following error in Eclipse when
running maven verify.

It appears to be using my Java 8 JRE to run the maven build even though I
have JRE_HOME set to below

JRE_HOME=C:\Program Files\OpenLogic\jdk-17.0.12.7-hotspot

 

And my PATH has the Open JDK first in the PATH variable

Path=C:\Program Files\OpenLogic\jdk-17.0.12.7-hotspot\bin;C:\Program
Files\Microsoft\jdk-11.0.16.101-hotspot\bin;C:\Program
Files\Java\jre-1.8;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C
:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\P
rogram Files\Java\jre-1.8\bin;C:\Program Files\dotnet\;C:\Program Files
(x86)\Windows Kits\10\Windows Performance Toolkit\;C:\Program
Files\Amazon\AWSCLIV2\;C:\Program Files (x86)\Bitvise SSH Client;C:\Program
Files\MySQL\MySQL Shell
8.0\bin\;C:\Users\charlie\AppData\Local\Microsoft\WindowsApps;C:\Users\charl
ie\.dotnet\tools

 

 

Output from Maven verify is below

Not sure what to do about it

 

Scanning for projects...

[INFO] 

[INFO] [1m---< [0;36morg.apache.tomcat:jakartaee-migration[0;1m
>[m

[INFO] [1mBuilding Apache Tomcat Migration Tool for Jakarta EE
1.0.9-SNAPSHOT[m

[INFO]   from pom.xml

[INFO] [1m[ jar
]-[m

[INFO]
[1m[
m

[INFO] [1;31mBUILD FAILURE[m

[INFO]
[1m[
m

[INFO] Total time:  0.647 s

[INFO] Finished at: 2024-09-03T19:27:17-04:00

[INFO]
[1m[
m

[ERROR] Failed to execute goal on project [36mjakartaee-migration[m:
[1;31mCould not resolve dependencies for project
org.apache.tomcat:jakartaee-migration:jar:1.0.9-SNAPSHOT: The following
artifacts could not be resolved: com.sun:tools:jar:1.8.0: Could not find
artifact com.sun:tools:jar:1.8.0 at specified path C:\Program
Files\Java\jre-1.8/../lib/tools.jar[m -> [1m[Help 1][m

[ERROR] 

[ERROR] To see the full stack trace of the errors, re-run Maven with the
[1m-e[m switch.

[ERROR] Re-run Maven using the [1m-X[m switch to enable full debug logging.

[ERROR] 

[ERROR] For more information about the errors and possible solutions, please
read the following articles:

[ERROR] [1m[Help 1][m
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionExcepti
on

 

 

Re: Migration of Spring MVC 4 app to Spring MVC 6

[Mark Thomas]

On 04/09/2024 00:33, charliedidon...@gmail.com wrote:

I am migrating a Spring MVC app from 4.x to 6.x so I am going from Tomcat
9.1 Java 8 to Tomcat 10.1 Java 17.

I noticed that in the migration steps on the Tomcat site that there is a
tool to help with the javax to Jakarta package conversions

  


I have downloaded the migration tool from Github
https://github.com/apache/tomcat-jakartaee-migration

I currently have 2 versions of Java on my machine.  Java 8 (Oracle) and Java
17 (Open JDK)

  


And am trying to build it and am getting the following error in Eclipse when
running maven verify.


Possibly an issue with the Eclipse environment?

mvn clean verify

works for me with both Java 8 and Java 17 with the current HEAD of the 
main branch.


I'd suggest building on the command line as a first step towards 
debugging what is going on.


Mark




It appears to be using my Java 8 JRE to run the maven build even though I
have JRE_HOME set to below

JRE_HOME=C:\Program Files\OpenLogic\jdk-17.0.12.7-hotspot

  


And my PATH has the Open JDK first in the PATH variable

Path=C:\Program Files\OpenLogic\jdk-17.0.12.7-hotspot\bin;C:\Program
Files\Microsoft\jdk-11.0.16.101-hotspot\bin;C:\Program
Files\Java\jre-1.8;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C
:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\P
rogram Files\Java\jre-1.8\bin;C:\Program Files\dotnet\;C:\Program Files
(x86)\Windows Kits\10\Windows Performance Toolkit\;C:\Program
Files\Amazon\AWSCLIV2\;C:\Program Files (x86)\Bitvise SSH Client;C:\Program
Files\MySQL\MySQL Shell
8.0\bin\;C:\Users\charlie\AppData\Local\Microsoft\WindowsApps;C:\Users\charl
ie\.dotnet\tools

  

  


Output from Maven verify is below

Not sure what to do about it

  


Scanning for projects...

[INFO]

[INFO] [1m---< [0;36morg.apache.tomcat:jakartaee-migration[0;1m

[m


[INFO] [1mBuilding Apache Tomcat Migration Tool for Jakarta EE
1.0.9-SNAPSHOT[m

[INFO]   from pom.xml

[INFO] [1m[ jar
]-[m

[INFO]
[1m[
m

[INFO] [1;31mBUILD FAILURE[m

[INFO]
[1m[
m

[INFO] Total time:  0.647 s

[INFO] Finished at: 2024-09-03T19:27:17-04:00

[INFO]
[1m[
m

[ERROR] Failed to execute goal on project [36mjakartaee-migration[m:
[1;31mCould not resolve dependencies for project
org.apache.tomcat:jakartaee-migration:jar:1.0.9-SNAPSHOT: The following
artifacts could not be resolved: com.sun:tools:jar:1.8.0: Could not find
artifact com.sun:tools:jar:1.8.0 at specified path C:\Program
Files\Java\jre-1.8/../lib/tools.jar[m -> [1m[Help 1][m

[ERROR]

[ERROR] To see the full stack trace of the errors, re-run Maven with the
[1m-e[m switch.

[ERROR] Re-run Maven using the [1m-X[m switch to enable full debug logging.

[ERROR]

[ERROR] For more information about the errors and possible solutions, please
read the following articles:

[ERROR] [1m[Help 1][m
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionExcepti
on

  

  





-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org