okm:trash

[prashanth]

I connected SQL Server 2005 to openkm. And all tables are created in respective databases. When i try to login openkm by using username : okmAdmin, password : admin, its showing okm:trash. In command prompt error message showing that is added below
2011-03-17 12:31:50,627 WARN [org.apache.jackrabbit.core.SessionImpl] Unclosed session detected. The session was opened here:java.lang.Exception: Stack Trace .
I not understood where we using session. Please give me an solution.

[jllort]

Put some screenshot and the server.log error ( only the error not all the log )

[prashanth]

Put some screenshot and the server.log error ( only the error not all the log )

This is the error code i getting,

Code: Select all

2011-03-17 12:30:00,626 DEBUG [org.jboss.security.plugins.JaasSecurityManagerService] Added OpenKM, org.jboss.security.plugins.SecurityDomainContext@f36a2e to map
2011-03-17 12:31:50,627 WARN  [org.apache.jackrabbit.core.SessionImpl] Unclosed session detected. The session was opened here: 
java.lang.Exception: Stack Trace
	at org.apache.jackrabbit.core.SessionImpl.<init>(SessionImpl.java:249)
	at org.apache.jackrabbit.core.XASessionImpl.<init>(XASessionImpl.java:124)
	at org.apache.jackrabbit.core.RepositoryImpl.createSessionInstance(RepositoryImpl.java:1535)
	at org.apache.jackrabbit.core.RepositoryImpl.createSession(RepositoryImpl.java:993)
	at org.apache.jackrabbit.core.RepositoryImpl.extendAuthentication(RepositoryImpl.java:1058)
	at org.apache.jackrabbit.core.RepositoryImpl.login(RepositoryImpl.java:1382)
	at org.apache.jackrabbit.commons.AbstractRepository.login(AbstractRepository.java:41)
	at com.openkm.util.JCRUtils$1.run(JCRUtils.java:309)
	at java.security.AccessController.doPrivileged(Native Method)
	at javax.security.auth.Subject.doAs(Subject.java:337)
	at com.openkm.util.JCRUtils.getSession(JCRUtils.java:304)
	at com.openkm.module.direct.DirectAuthModule.login(DirectAuthModule.java:65)
	at com.openkm.api.OKMAuth.login(OKMAuth.java:52)
	at org.apache.jsp.com_openkm_frontend_Main.index_jsp._jspService(index_jsp.java:59)
	at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
	at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:373)
	at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:336)
	at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
	at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182)
	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:524)
	at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
	at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
	at java.lang.Thread.run(Thread.java:619)
2011-03-17 13:06:14,233 INFO  [org.jboss.system.server.Server] Runtime shutdown hook called, forceHalt: true
2011-03-17 13:06:14,249 INFO  [org.jboss.system.server.Server] JBoss SHUTDOWN: Undeploying all packages
2011-03-17 13:06:14,249 DEBUG [org.jboss.deployment.MainDeployer] Undeploying file:/C:/jboss-4.2.3.GA/server/default/deploy/jmx-console.war/, isShutdown=true
2011-03-17 13:06:14,249 DEBUG [org.jboss.system.ServiceController] stopping service: jboss.web.deployment:war=jmx-console.war,id=-2088151004
2011-03-17 13:06:14,249 DEBUG [org.jboss.system.ServiceController] stopping dependent services for: jboss.web.deployment:war=jmx-console.war,id=-2088151004 dependent services are: []

[prashanth]

hello Sir
This is the screen we geting after loging the openkm

This is the screen we getting after loging the OpenKm
OpenKM.JPG (69.43 KiB) Viewed 5519 times

[pavila]

Seems a problem in the repository creation. Which OpenKM version are you using? Have you read the documentation wiki?

[prashanth]

Thankyou for reply. We getting same problem in both 5.0 and 5.0.3 version.We are installing openkm step by step by reading wiki documentation itself.

[prashanth]

We compiling openkm in windows server 2008 64bit. We installed openkm by reading step by step of documentation. Everything gone wright database is created in sqlserver 2005. All the tables are created in respective databases. Then when we login its showing screen okm:trash.Error code already send to you.
if we give wrong password or username it shows authentication error. So it recognsing the username ,password. U told might be problem in repository part. We not getting exactly what is the mistake in that. Please give me an solution

[jllort]

We compiling openkm in windows server 2008 64bit.

If I understand, you've donwloaded OpenKM from sourceforge and compiled it. Have you made any change on source code ?
Could you try replace your generated OpenKM.war file for ours to ensure the problem is not there.
You're on a clean installation ? other thinks that we must know ?