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.

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

spring-boot: tomcat: if management port is different from the app port, the app's access.log goes to /tmp/tomcat.xxxxx.port [SPR-12220] #16834

Closed
spring-projects-issues opened this issue Sep 18, 2014 · 1 comment
Labels
status: invalid

Comments

@spring-projects-issues
Copy link
Collaborator

spring-projects-issues commented Sep 18, 2014

Simon So opened SPR-12220 and commented

spring-boot 1.1.6

http://stackoverflow.com/questions/23596157/spring-boot-tomcat-access-logs

The issue exists since 1.1

Steps to reproduce

  1. in application.properties, define management port = 7081
  2. in application.properties, define the app port to be anything but 7081
  3. in application.properties, set the server.tomcat.base=/home/mydir
  4. Start the spring-boot project with tomcat as the web server

expected: access log goes to /home/mydir
actual: after a few days, the access.log will suddenly appears in /tmp/tomcat.xxxx.port_number

I have cloud deployment that needs to do log rotation. Prefer to centralize everything to one single directory.


Affects: 4.0.6

@spring-projects-issues
Copy link
Collaborator Author

spring-projects-issues commented Sep 18, 2014

Juergen Hoeller commented

Note that this JIRA is the Spring Framework issue tracker. We do not deal with Spring Boot issues here.

The Spring Boot project uses GitHub issues instead: https://github.com/spring-projects/spring-boot/issues. Please report your issue there.

@spring-projects-issues spring-projects-issues added type: bug status: invalid and removed type: bug labels Jan 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: invalid
Projects
None yet
Development

No branches or pull requests

1 participant