admin wrote:drew wrote:Thank-you, thank-you, thank-you. I never would have figured this one out. It took me several attempts but I finally got the import to go through, took about an hour. However I still can not access the project.
Yes, it can be long process - we recently import 75 MB file. By the way sman in 2.8.2 has major data import bugs, so I suggest you upgrade to 2.8.3 or simple download
http://www.trackstudio.com/tse-28/sman.jardrew wrote:
I'm not sure what you mean by full stack trace. The Java Console shows two warnings about Style Sheets, nothing else.
The error has changed to just the word 'null'.
Note: I am using the WAR distribution, used the SA distribution to get sman for the import.
Please try to start with sman and send me content of sman logging window when error occurs.
I started from within sman, it doesn't enable the 'Open window' button, but I just aimed my browser at
http://127.0.0.1:8080/TrackStudio/index.html and connected successfully. I was also able to open the project in question. That said I am not sure whether the log will help much, but I will e-mailed that file to
support@trackstudio.com right after this post (since the log is 9825 lines).
With the project loaded in the SA version, I noticed the memory footprint on my PC was about 756MB. This made me think that the Linux server that the WAR version is running on may not have sufficient memory, since it only has 256MB, I have memory on order it just hasn't arrived. I stripped another 256MB out of a different server, now I get the following error from Tomcat:
- Code: Select all
HTTP Status 500 -
type Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
javax.servlet.ServletException
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:248)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:260)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:432)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:386)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:534)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:530)
at java.lang.Thread.run(Thread.java:536)
root cause
java.lang.OutOfMemoryError
Apache Tomcat/4.1.18
As I mentioned I have ordered more memory 1GB, but I am surprised as to the amount of memory required, this is one of the reasons we selected Linux over Windows as the OS. Is this an issue with Tomcat, should I consider a different application server?
admin wrote:drew wrote:The id's seem to import fine, and all the constraints activated so in that respect I think the import is fine. However, the error persists.
Strange, but possbile. Please also try the following - left only several tasks in the XML and send it to me.
Since the problem appears to be memory related, I am wondering how things will work as the task list grows, currently I have imported only about 8800 tasks moving forward there will be several users entering tasks live, the task list is likely to grow rapidly. Not to mention that since the old system would only export summary informatio, no messages or detail descriptions, the data I have used to ignite the new tracking system is relatively small, but going forward the tasks will have far more detail.
admin wrote:Yes, you must have task with id '1', user with id '1' and filter with id '1'.
All the id 1 items remain in the DB.
Thanks in advance,