• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Rob Spoor
  • Tim Cooke
  • Junilu Lacar
Sheriffs:
  • Henry Wong
  • Liutauras Vilda
  • Jeanne Boyarsky
Saloon Keepers:
  • Jesse Silverman
  • Tim Holloway
  • Stephan van Hulst
  • Tim Moores
  • Carey Brown
Bartenders:
  • Al Hobbs
  • Mikalai Zaikin
  • Piet Souris

Tomcat error after installing Activiti

 
Bartender
Posts: 1810
28
jQuery Netbeans IDE Eclipse IDE Firefox Browser MySQL Database Chrome Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I installed Activiti for an evaluation, and even after undeploying it, I'm getting this error on server startup:


PSI Probe confirms that the app is no longer installed. I searched the Tomcat directory structure for the string "activiti" and only found log entries. The server.xml file contains only the standard Catalina listeners. All other applications on the server still work. Nothing changed in the tomcat\lib folder. ServletRegistration$Dynamic is an interface in servlet-api.jar, but that file is still in the tomcat\lib folder.

This is driving me crazy. Where is this listener trying to load from?
 
Sheriff
Posts: 10445
227
IntelliJ IDE Ubuntu
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Recent versions of Java EE allow application listeners to be defined via annotations. Have you checked if there's some (stray) application which might be having some jar with that Activiti class marked as a listener?
 
J. Kevin Robbins
Bartender
Posts: 1810
28
jQuery Netbeans IDE Eclipse IDE Firefox Browser MySQL Database Chrome Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I just searched for "@WebListener" and "@EventListener" and got nothing.

Good idea, but the mystery continues...
 
Saloon Keeper
Posts: 24330
167
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
It's always a good idea when deploying or redeploying to delete all items under tomcat's work/, temp/ and logs/ directories. Do this before bringing Tomcat up with the new version of the webapp.

If you don't delete the stuff under work/, in particular, you may be afflicted by stale sessions left over from previous runs and the baggage that they pulled in.
 
J. Kevin Robbins
Bartender
Posts: 1810
28
jQuery Netbeans IDE Eclipse IDE Firefox Browser MySQL Database Chrome Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks for the tip. I deleted everything in /work/Catalina/localhost, and even though there was no "activiti-explorer" folder, I'm no longer getting that error. I can't explain it, but I'm glad it's gone. It was driving me crazy. I'm giving you a cow for that one.
 
Tim Holloway
Saloon Keeper
Posts: 24330
167
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Here's how it often goes.

HttpSession-scope objects MUST be serializable. As of Tomcat 6 (or maybe 5), Tomcat does not consider this optional. Tomcat serializes session data to ".ser" files in the work directory.

If Tomcat is shut down and then restarted, this serialization is useful because it means that the user will experience temporary inability to access the server, but when it comes back up, the session will be restored so he/she/it won't lose any work. This is probably a Tomcat config option, but that's the default.

If one of those session objects references a class that's in Tomcat's classpath (say, TOMCAT/lib) but that class has been removed from TOMCAT/lib, then the restored object won't be able to resolve it any more and the session restore will fail. A variation on that theme can also occur if there's dynamic class loading and the dynamically-referenced class has been pulled out of the classpath.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic