cancel
Showing results for 
Search instead for 
Did you mean: 

can't login in activiti explorer

johnrd
Champ in-the-making
Champ in-the-making

Hi,

I am having a problem with login ( kermit/kermit)  I have redeployed the  activiti war file in case of any corruption, created my database but problem persisting.

Please help

John.

a stack trace is given below


Apr 20, 2013 9:47:04 PM org.apache.catalina.core.StandardWrapperValve invoke
SEVERE: Servlet.service() for servlet [Vaadin Application Servlet] in context with path [/activiti-explorer] threw exception [com.vaadin.event.ListenerMethod$MethodException: Invocation of method onLogin in org.activiti.explorer.ui.login.LoginPage$ActivitiLoginListener failed.] with root cause
java.lang.NullPointerException
   at org.activiti.explorer.ui.login.DefaultLoginHandler.authenticate(DefaultLoginHandler.java:40)
   at org.activiti.explorer.ui.login.DefaultLoginHandler.authenticate(DefaultLoginHandler.java:34)
   at org.activiti.explorer.ui.login.LoginPage$ActivitiLoginListener.onLogin(LoginPage.java:98)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
   at java.lang.reflect.Method.invoke(Method.java:601)
   at com.vaadin.event.ListenerMethod.receiveEvent(ListenerMethod.java:510)
   at com.vaadin.event.EventRouter.fireEvent(EventRouter.java:164)
   at com.vaadin.ui.AbstractComponent.fireEvent(AbstractComponent.java:1219)
   at com.vaadin.ui.LoginForm$2.handleParameters(LoginForm.java:103)
   at com.vaadin.ui.Window.handleParameters(Window.java:515)
16 REPLIES 16

I downloaded activiti 5.13  today, first time user and had the same problem. I am a newbie to activiti so if the suggestion below is incorrect please let me know alternative solution. The class public class DefaultLoginHandler implements LoginHandler had
definitionSmiley Tonguerivate transient IdentityService identityService;
previous version of the same module were defined as: private IdentityService identityService;
removed transient, recompiled and it seems to be working ok. Hope this helps.

reinaud
Champ in-the-making
Champ in-the-making
Same Error.

I'm using 5.13 as well along with mysql

reinaud
Champ in-the-making
Champ in-the-making
I looks like this is happening randomly. Last week it worked fine today i started up the same application, but without success!

Please supply a working solution!

glazachev
Champ in-the-making
Champ in-the-making
Workaround - turn off tomcat session serialization.
Add <Manager pathname="" /> in activiti-explorer/META-INF/context.xml file.

It should looks like this:
&lt;Context antiJARLocking="true" path="/activiti-explorer2"&gt;
&lt;Manager pathname="" /&gt;
&lt;/Context&gt;

houstoniasian
Champ in-the-making
Champ in-the-making
It definitely happens randomly.  I have Activiti 5.13 working with Tomcat 7.0.33 all day long and all of a sudden I have the same error.  I shut down, restart a few times and it still does not work.  I went to the log folder, delete all the logs, restart tomcat, look at the logs to see if there is any error, no error.  And then all of a sudden I'm able to log in as kermit/kermit again.  This worries me as I'm in the beginning of the project.  And if Activiti acts randomly like this, we may not want to rely on Activiti.

frederikherema1
Star Contributor
Star Contributor
Please keep in mind that activiti-explorer is a demo-app, demonstrating the API of activiti in a UI. The engine itself is QA'ed intensively (check out our unit-tests) and is reliable. The Explorer-app is NOT qa'ed as extensively, rather it shows people how to leverage the API's…

houstoniasian
Champ in-the-making
Champ in-the-making
Today I have the same problem again.  I decided to run activiti-explorer in different port.  It worked.  I went back and run it on port 8080.  It worked too.  So for whatever reason, changing port would fix this problem.  This does not answer why it happened in the first place.  But at least we have a way to get around this issue.  Hopefully somebody would know why changing port would fix this and can fix the root cause.