Joget DX 8 Stable Released
The stable release for Joget DX 8 is now available, with a focus on UX and Governance.
I have a user that I set up exactly as I am supposed to if not than I would have had problems with my other users
The problem is that everytime I try logging in the app or console with that bastard, I get an error 404.
Has anybody ever faced something similar that could give me hint as to how to fix this up??
Thanks in advance to have taken the time to read this, I am clueless here.
MO
2 Comments
Hugo
Hi Marc,
Are you getting any error details? Those will be very helpful for us to help you troubleshoot. You may try to check the server log as well.
Which URL are you attempting to access at that time? Does it happen to all pages or to all users?
You can also try to create another user and try again to isolate the problem.
Thanks.
Marc-O. D. Rompre
There is no stack trace errors I would have sent you one if there had been.
Now I have the same problem with 2 more users.
Can synchronizing MSSQL DBs cause this kind of behavior??
Thank for your help
Ill send you a video by mail since it's over 10mb.
INFO 06 mars 2014 14:54:03 org.joget.apps.workflow.security.WorkflowHttpAuthProcessingFilter - Authentication for user admin: true
INFO 06 mars 2014 14:54:32 org.joget.apps.workflow.security.WorkflowHttpAuthProcessingFilter - Authentication for user chiefeng_007: true
INFO 06 mars 2014 14:54:43 org.joget.apps.workflow.security.WorkflowHttpAuthProcessingFilter - Authentication for user Master_005: true
INFO 06 mars 2014 14:54:54 org.joget.workflow.shark.WorkflowAssignmentManager - [processId=7_safetyManagementApp_defectreport, processDefId=safetyManagementApp#2#defectreport, participantId=participant1, next user=[Master_005]]
INFO 06 mars 2014 15:05:14 org.joget.apps.workflow.security.WorkflowHttpAuthProcessingFilter - Authentication for user admin: true
INFO 06 mars 2014 15:08:04 org.joget.apps.workflow.security.WorkflowHttpAuthProcessingFilter - Authentication for user 1OFF_005: true
INFO 06 mars 2014 15:08:35 org.joget.apps.workflow.security.WorkflowHttpAuthProcessingFilter - Authentication for user 1OFF_005: true
WARN 06 mars 2014 15:10:49 com.atomikos.icatch.config.UserTransactionServiceImp - No properties path set - looking for transactions.properties in classpath...
WARN 06 mars 2014 15:10:49 com.atomikos.icatch.config.UserTransactionServiceImp - transactions.properties not found - looking for jta.properties in classpath...
WARN 06 mars 2014 15:10:49 com.atomikos.icatch.config.UserTransactionServiceImp - Using init file: /C:/Joget-v3/apache-tomcat-6.0.18/webapps/jw/WEB-INF/classes/jta.properties
INFO 06 mars 2014 15:10:50 org.joget.commons.util.SetupManager - Using base directory: ./wflow/
INFO 06 mars 2014 15:10:50 org.joget.commons.util.DynamicDataSource - datasourceName=workflow, url=jdbc:sqlserver://localhost:1433;DatabaseName=jwdbTDI;SelectMethod=cursor, user=sa
INFO 06 mars 2014 15:10:51 org.joget.plugin.base.PluginManager - PluginManager initialized
INFO 06 mars 2014 15:10:53 org.joget.workflow.model.service.WorkflowManagerImpl - Datasource bound to jwdb
INFO 06 mars 2014 15:10:56 org.displaytag.filter.ResponseOverrideFilter - Filter initialized. Response buffering is enabled
INFO 06 mars 2014 15:11:48 org.joget.apps.workflow.security.WorkflowHttpAuthProcessingFilter - Authentication for user 1OFF_005: true (This is the message we get when everything's fine right??)