Not supported on Tomcat 8.5.3 ? #42
Comments
|
@zsustar did you find any workarounds? |
|
@yateam not yet, so have to use tomcat 7 for the time being... |
|
I apologize for the silence on this. Turns on this method was removed from Tomcat 8.5 but it's value has been ignored since Tomcat 6. I've removed this method call and am trying to get a release out that should be compatible with new versions of Tomcat, having issues with GPG signing. |
|
Okay the fix has been released under 2.0.3. Can you give it a try? |
|
I still see this issue. Can u provide a Jar which you think works. |
|
Is the error message the same? |
|
Please see the output of catalina.out 18-Aug-2016 18:40:20.904 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server version: Apache Tomcat/8.5.4 18-Aug-2016 18:40:22.263 SEVERE [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployWAR Error deploying web application archive C:\Tomcat\apache-tomcat-8.5.4\webapps\vshome.war 18-Aug-2016 18:40:22.263 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployWAR Deployment of web application archive C:\Tomcat\apache-tomcat-8.5.4\webapps\vshome.war has finished in 47 ms 18-Aug-2016 18:40:22.279 SEVERE [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Error deploying web application directory C:\Tomcat\apache-tomcat-8.5.4\webapps\docs 18-Aug-2016 18:40:22.279 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory C:\Tomcat\apache-tomcat-8.5.4\webapps\docs has finished in 0 ms 18-Aug-2016 18:40:22.279 SEVERE [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Error deploying web application directory C:\Tomcat\apache-tomcat-8.5.4\webapps\examples 18-Aug-2016 18:40:22.279 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory C:\Tomcat\apache-tomcat-8.5.4\webapps\examples has finished in 0 ms 18-Aug-2016 18:40:22.295 SEVERE [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Error deploying web application directory C:\Tomcat\apache-tomcat-8.5.4\webapps\host-manager 18-Aug-2016 18:40:22.295 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory C:\Tomcat\apache-tomcat-8.5.4\webapps\host-manager has finished in 16 ms 18-Aug-2016 18:40:22.310 SEVERE [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Error deploying web application directory C:\Tomcat\apache-tomcat-8.5.4\webapps\manager 18-Aug-2016 18:40:22.310 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory C:\Tomcat\apache-tomcat-8.5.4\webapps\manager has finished in 15 ms 18-Aug-2016 18:40:22.310 SEVERE [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Error deploying web application directory C:\Tomcat\apache-tomcat-8.5.4\webapps\ROOT 18-Aug-2016 18:40:22.310 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory C:\Tomcat\apache-tomcat-8.5.4\webapps\ROOT has finished in 0 ms |
|
Looking back through the source history it appears you are using this revision https://github.com/aws/aws-dynamodb-session-tomcat/blob/2de64e49d64cc21b71d7aac1d341f67b20656d7a/src/main/java/com/amazonaws/services/dynamodb/sessionmanager/DynamoDBSessionManager.java#L74 Can you make sure you are using 2.0.3? Note that the session manager must be present in the lib directory of the tomcat installation and not the context. |
|
On running the Application using mvn package I see the folliowing error. Any chance you could upload Jar on github with your fix? ReflectionUtils.java:189) com.amazonaws.services.dynamodb.sessionmanager.ExpiredSessionReaperIntegrationTe Running com.amazonaws.services.dynamodb.sessionmanager.ExpiredSessionReaperTest com.amazonaws.services.dynamodb.sessionmanager.SessionStorageIntegrationTest Ti Results : Tests in error: Tests run: 28, Failures: 0, Errors: 16, Skipped: 0 [INFO] ------------------------------------------------------------------------ |
|
Hi I was able to build 2.0.3.It is unable to find the setDistributable method. Please see log below. 20-Aug-2016 17:37:45.003 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server version: Apache Tomcat/8.5.4 20-Aug-2016 17:38:11.768 SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.startInternal Context [/vshome] startup failed due to previous errors 20-Aug-2016 17:38:12.221 SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.startInternal Context [/docs] startup failed due to previous errors 20-Aug-2016 17:38:14.065 SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.startInternal Context [/examples] startup failed due to previous errors 20-Aug-2016 17:38:14.502 SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.startInternal Context [/host-manager] startup failed due to previous errors 20-Aug-2016 17:38:14.986 SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.startInternal Context [/manager] startup failed due to previous errors 20-Aug-2016 17:38:15.705 SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.startInternal Context [] startup failed due to previous errors |
|
I have the same problem with 2.0.3 version (the @akmukherjee problem) |
|
I believe this is because it has been removed in Tomcat 8.5. Please see this link for details about that. Also, @shorea , if you can please take a look at https://tomcat.apache.org/tomcat-8.0-doc/api/deprecated-list.html for the other deprecated fields as they apply for Tomcat 8.5, that would be most appreciated. |
|
Sorry for the delay, I distracted with another project. I just published v2.0.4 that should resolve the compatibility issues. Can you give it another try? (It may be a few minutes before it's accessible in Maven). |
|
Yeah it works. Thanks Andrew. I was wondering if there are any mechanisms exposed to control the duration after which the session is deleted from the Session Table. |
|
I believe you want maxInactiveInterval, https://tomcat.apache.org/tomcat-7.0-doc/config/manager.html. We won't consider deleting a session until it's inactive. |
|
Nice. The Jar being developed here did not seem to be taking maxInactiveInterval as an input from the user via Context.xml file or provide any mechanism to do so. Currently, it is defaulted to 30 min and I was looking to change it to 20 min and was looking to see if this App would allow me control that somehow. |
Hi
I am running Tomcat 8.5.3 and JDK 1.8u92 on RedHat 7.
I just downloaded the jar file and deployed according to the guide from AWS.
However, I got following issue while starting the tomcat.
BTW, the Tomcat 7 with JDK 1.7 on same machine looks running good.
Thanks
catalina_log.txt
13-Jul-2016 10:35:57.243 SEVERE [localhost-startStop-1] org.apache.tomcat.util.digester.Digester.startElement Begin event threw error
java.lang.NoSuchMethodError: com.amazonaws.services.dynamodb.sessionmanager.DynamoDBSessionManager.setMaxInactiveInterval(I)V
at com.amazonaws.services.dynamodb.sessionmanager.DynamoDBSessionManager.(DynamoDBSessionManager.java:71)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at java.lang.Class.newInstance(Class.java:442)
at org.apache.tomcat.util.digester.ObjectCreateRule.begin(ObjectCreateRule.java:117)
at org.apache.tomcat.util.digester.Digester.startElement(Digester.java:1188)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:509)
at com.sun.org.apache.xerces.internal.parsers.AbstractXMLDocumentParser.emptyElement(AbstractXMLDocumentParser.java:182)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:1344)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2787)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:606)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:510)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:848)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:777)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1213)
at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:643)
at org.apache.tomcat.util.digester.Digester.parse(Digester.java:1461)
at org.apache.catalina.startup.ContextConfig.processContextConfig(ContextConfig.java:536)
at org.apache.catalina.startup.ContextConfig.contextConfig(ContextConfig.java:474)
at org.apache.catalina.startup.ContextConfig.init(ContextConfig.java:734)
at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:309)
at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:94)
at org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:401)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:115)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:141)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:726)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:702)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:734)
at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1107)
at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1841)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
The text was updated successfully, but these errors were encountered: