Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Wilma does not work with Java 1.8 #3

Closed
tkohegyi opened this issue Mar 9, 2015 · 4 comments
Closed

Wilma does not work with Java 1.8 #3

tkohegyi opened this issue Mar 9, 2015 · 4 comments
Assignees
@tkohegyi
Labels
enhancement

Comments

@tkohegyi
Copy link
Contributor

tkohegyi commented Mar 9, 2015

Wilma cannot start when running it with (jre) java 1.8 (while it works fine with 1.7).
Exception from the logs:
14:23:18.823 [main] ERROR c.e.w.e.bootstrap.WilmaBootstrap - Wilma cannot be started.
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'configurationInitializer': Injection of autowired dependencies failed; nested exception is org.springframework.beans.factory.BeanCreationException: Could not autowire field: private com.epam.wilma.engine.properties.PropertyLoader
....
Probably upgrading the 3rd party libs would be necessary, but right now only Java 1.7 is supported.
Also tried running Wilma 0.6 with java 1.8 . It didn't work either.
Had a similar autowire/bean creation error message.
@tkohegyi
Copy link
Contributor Author

Based on this: http://stackoverflow.com/questions/26324084/java-1-8u20-fails-to-start-with-spring-boot-and-groovy-2-3-7, seems a bug in used java jdk version - this will be checked soon.

On the other hand need to check if jetty (jasper /spring framework) and ActiveMQ has proper support for 1.8, too.

@tkohegyi
Copy link
Contributor Author

Need to check if upgrade to

  • Spring FW 4.0.3+
  • Jetty 9.2.0
    can solve this or not.

@tkohegyi tkohegyi self-assigned this Apr 25, 2015
tkohegyi added a commit that referenced this issue Apr 25, 2015
@tkohegyi
#3 upgraded to spring fw 4.1, jetty 8.1.16 (message-search to 9.2.10Ö…
6b220c6 
…, and prepared for test with java 1.8
@tkohegyi
Copy link
Contributor Author

based on this, another upgrade (for saxon) is necessary: https://saxonica.plan.io/issues/1944

tkohegyi added a commit that referenced this issue Apr 27, 2015
@tkohegyi
Merge pull request #37 from epam/java18
fa663cd 
#3 upgrading libs to make Wilma Java1.8 compatible
@tkohegyi tkohegyi mentioned this issue Apr 27, 2015
Merged
tkohegyi added a commit that referenced this issue Apr 28, 2015
@tkohegyi
- Start string enhancements for Wilma and Wilma Message Search - patc…
d6b8790 
…h for #34

- Fix last 2 func test error for #3
- Fix checkstyle problems for #3
- Enhance Gepard test log info in func test
TiborK0vacs pushed a commit that referenced this issue May 12, 2015
@tibor-kovacs-epam
addressing junit behavior difference between jdk1.7 and jdk 1.8, need…
2f0b58b 
… for #3
tkohegyi added a commit that referenced this issue May 13, 2015
@tkohegyi
- fix functional test failure that is caused by browsermob-proxy roll…
f209c5d 
…back (connected to #3)

- implement error log enhancement to address #42, message id is added to such error message
@tkohegyi
Copy link
Contributor Author

V1.1.24 works with Java 1.8 properly, issue closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tkohegyi tkohegyi

Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tkohegyi