Eclipse Community Forums: ServerTools (WTP) » Why does Jetty server restart an application?

Help

Home

Home » Language IDEs » ServerTools (WTP) » Why does Jetty server restart an application?

Show: Today's Messages :: Show Polls :: Message Navigator

Why does Jetty server restart an application? [message #1804805]

Mon, 01 April 2019 13:58

Alexey Trofimov

Messages: 1
Registered: April 2019

Junior Member

Greetings.

I have encountered some strange Jetty server's behavior that I can't explain. My application is running, then in the middle of long and somehow resource-consuming operation, it seems to interrupt (without any special messages in the log), and after a while I can see it's being redeployed.

Here comes the log fragment:

2019-02-21 09:00:07.365 [import-xml-1] DEBUG ru.it.p321.service.ImportRegistryManagerImpl - Skip updating BO 976224=f13cb37be80085ad44e240dd8ebf9d05
2019-02-21 09:00:07.378 [import-xml-4] DEBUG ru.it.p321.service.ImportRegistryServiceImpl - [XML Data Import] file VO_RRMSPSV_0000_9965_20181113_c121856e-2753-4535-85de-49a629b28242.xml has UTF-8 encoding
2019-02-21 09:00:07.404 [import-xml-1] DEBUG ru.it.p321.service.ImportRegistryManagerImpl - Skip updating BO 976226=676e77c4e2293e2cd0168e7cbf7d2123
2019-02-21 09:00:36.095 [main] INFO com.jcabi.manifests.Manifests - #load(): 128 attribs loaded from 396 URL(s) in 489ms: ["Agent-Class", "Ant-Version", "Application-Library-Allowable-Codebase", "Application-Name", "Archiver-Version", "Automatic-Module-Name", "Bnd-LastModified", "Build-Commit", "Build-Id", "Build-Jdk", "Build-Tag", "Build-Time", "Build-TimeStamp", "Build-Timestamp", "Build-Version", "BuildInfo-Host", "BuildInfo-Revision", "BuildInfo-Timestamp", "BuildInfo-URL", "BuildInfo-User", "Built-At", "Built-By", "Built-On", "Bundle-ActivationPolicy", "Bundle-Activator", "Bundle-Category", "Bundle-ClassPath", "Bundle-Classpath", "Bundle-Copyright", "Bundle-Description", "Bundle-DocURL", "Bundle-License", "Bundle-Localization", "Bundle-ManifestVersion", "Bundle-Name", "Bundle-RequiredExecutionEnvironment", "Bundle-SymbolicName", "Bundle-Vendor", "Bundle-Version", "Caller-Allowable-Codebase", "Can-Redefine-Classes", "Can-Retransform-Classes", "Class-Path", "Codebase", "Copyright-Notice", "Created-By", "DynamicImport-Package", "Eclipse-BuddyPolicy", "Eclipse-SourceReferences", "Embed-Dependency", "Export-Package", "Export-Service", "Extension-Name", "Extension-name", "Git-Revision", "Git-Url", "HK2-Class-Path-Id", "Ignore-Package", "Implementation-Build", "Implementation-Build-Date", "Implementation-Build-Id", "Implementation-Title", "Implementation-URL", "Implementation-Url", "Implementation-Vendor", "Implementation-Vendor-Id", "Implementation-Version", "Import-Package", "Include-Resource", "JCabi-Build", "JCabi-Version", "Java-Vendor", "Java-Version", "Karaf-Info", "License", "Liquibase-Package", "Main-Class", "Main-class", "Major-Version", "Manifest-Version", "Maven-Version", "Multi-Release", "Name", "Originally-Created-By", "Os-Arch", "Os-Name", "Os-Version", "Package", "Permissions", "Premain-Class", "Private-Package", "Probe-Provider-XML-File-Names", "Project-Name", "Provide-Capability", "Release-Designation", "Release-Version", "Require-Capability", "SCM-Revision", "SVN-Revision", "SVN-URL", "Scm-Connection", "Scm-Revision", "Scm-Url", "Sealed", "Solar-Version", "Specification-Title", "Specification-Vendor", "Specification-Version", "Terracotta-Description", "Terracotta-Name", "Terracotta-ProjectStatus", "Time-Zone-Database-Version", "Tool", "Trusted-Library", "UNO-Type-Path", "URL", "X-Compile-Source-JDK", "X-Compile-Target-JDK", "artifactId", "groupId", "mode", "p321-Container-Profile", "p321-Implementation-Build", "p321-Implementation-Build-Time", "p321-Implementation-Version", "probe-provider-class-names", "url", "version"]
2019-02-21 09:00:36.915 [main] INFO com.jcabi.aspects.aj.MethodValidator - JSR-303 validator

The last message from the application is at 09:00:07.404, then no logging at all untill at 09:00:36.095 we can see redeploy beginning. Usually Jetty would restart the application if any of its' artifacts were changed, but this is not the case.
Can anyone suggest what would be the reasons for such behavior? Any help would be appreciated.

We're using embedded Jetty 9.2.10, jdk 8 update 191.

Report message to a moderator