[g...@vmgump]: Project poi (in module poi) failed

2009-01-26 Thread Gump [HEAD] :-( 
To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at gene...@gump.apache.org.

Project poi has an issue affecting its community integration.
This issue affects 1 projects,
 and has been outstanding for 2 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- poi :  POI


Full details are available at:
http://vmgump.apache.org/gump/public/poi/poi/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Output [poi-ooxml-gump-26012009.jar] identifier set to output 
basename: [poi-ooxml-gump]
 -DEBUG- Output [poi-contrib-gump-26012009.jar] identifier set to output 
basename: [poi-contrib-gump]
 -DEBUG- Output [poi-scratchpad-gump-26012009.jar] identifier set to output 
basename: [poi-scratchpad-gump]
 -DEBUG- Output [poi-gump-26012009.jar] identifier set to output basename: 
[poi-gump]
 -INFO- Failed with reason build failed
 -DEBUG- Extracted fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/poi/poi/gump_work/build_poi_poi.html
Work Name: build_poi_poi (Type: Build)
Work ended in a state of : Failed
Elapsed: 3 mins 11 secs
Command Line: /usr/lib/jvm/java-6-sun/bin/java -Djava.awt.headless=true 
-Xbootclasspath/p:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/srv/gump/public/workspace/xml-xerces2/build/xercesImpl.jar:/srv/gump/public/workspace/xml-xalan/build/serializer.jar:/srv/gump/public/workspace/xml-xalan/build/xalan-unbundled.jar
 org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml 
-Dbuild.sysclasspath=only -Dversion.id=gump -DDSTAMP=26012009 -f build.xml gump 
[Working Directory: /srv/gump/public/workspace/poi]
CLASSPATH: 
/usr/lib/jvm/java-6-sun/lib/tools.jar:/srv/gump/public/workspace/poi/ooxml-lib/xmlbeans-2.3.0.jar:/srv/gump/public/workspace/poi/ooxml-lib/jsr173_1.0_api.jar:/srv/gump/public/workspace/poi/ooxml-lib/ooxml-schemas-1.0.jar:/srv/gump/public/workspace/poi/ooxml-lib/openxml4j-1.0-beta.jar:/srv/gump/public/workspace/poi/build/classes:/srv/gump/public/workspace/poi/build/contrib-classes:/srv/gump/public/workspace/poi/build/scratchpad-classes:/srv/gump/public/workspace/poi/build/ooxml-classes:/srv/gump/public/workspace/poi/build/test-classes:/srv/gump/public/workspace/poi/build/scratchpad-test-classes:/srv/gump/public/workspace/poi/build/ooxml-test-classes:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-xalan2.jar:/srv/gump/public/workspace/ant/dist/lib/ant-trax.jar:/srv/gump/public/workspace/ant/dist/l
 
ib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/logging-log4j-12/dist/lib/log4j-26012009.jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-26012009.jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-api-26012009.jar:/srv/gump/public/workspace/apache-commons/beanutils/dist/commons-beanutils-26012009.jar:/srv/gump/public/workspace/apache-commons/collections/build/commons-collections-26012009.jar:/srv/gump/public/workspace/apache-commons/lang/commons-lang-26012009.jar:/srv/gump/public/workspace/junit/dist/junit-26012009.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar:/srv/gump/public/workspace/dom4j/build/dom4j.jar
-
Buildfile: /srv/gump/public/workspace/poi/build.xml

check-jars:

fetch-jars:

testexist:

downloadfile:
  [get] Getting: 
http://www.ibiblio.org/maven/commons-logging/jars/commons-logging-1.1.jar
  [get] To: /srv/gump/public/workspace/poi/lib/commons-logging-1.1.jar
  [get] Error getting 
http://www.ibiblio.org/maven/commons-logging/jars/commons-logging-1.1.jar to 
/srv/gump/public/workspace/poi/lib/commons-logging-1.1.jar

BUILD FAILED
/srv/gump/public/workspace/poi/build.xml:335: The following error occurred 
while executing this line:
/srv/gump/public/workspace/poi/build.xml:317: java.net.ConnectException: 
Connection timed out

Total time: 3 minutes 10 seconds
-

To subscribe to this information via syndicated feeds:
- RSS: http://vmgump.apache.org/gump/public/poi/poi/rss.xml
- Atom: http://vmgump.apache.org/gump/public/poi/poi/atom.xml

== Gump Tracking Only ===
Produced by Gump version 2.3.
Gump Run 1626012009, vmgump:vmgump-public:1626012009
Gump E-mail Identifier (unique within

DO NOT REPLY [Bug 46602] New: out.of.mem exception when performing batch import of document structure

2009-01-26 Thread bugzilla 
https://issues.apache.org/bugzilla/show_bug.cgi?id=46602

   Summary: out.of.mem exception when performing batch import of
document structure
   Product: POI
   Version: 3.2-FINAL
  Platform: PC
OS/Version: Windows Server 2003
Status: NEW
  Severity: major
  Priority: P2
 Component: POI Overall
AssignedTo: dev@poi.apache.org
ReportedBy: carl.sky...@gmail.com


Hi, 

we are using the poi implementation to perform a metadatatransfer to documents
imported to our ECM solution.
When doing batch imports we notice that the memory is increasing rapidly ending
up in an out of memory exception. The memory setting for the tomcat running the
application server is 1024 mb.
It seems like the poi doesn´t release the memory after it is done with the
metadata transfer for one document and before starting with the next. This
makes the apache allocate more memory and in the end ending up with a
out.of.mem exception in the log.
java.lang.OutOfMemoryError: Java heap space

The same test has been done without the metadata transfer and this does not end
up in this error. 

We are using Apache Tomcat 5.5.25 as application server and java 1.5.0_12.
The application is Webtop 6.0 SP1 (EMC) and the import is performed to
documentum contentserver 6.0 sp1 (EMC).

br
Carl Skymne


-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org

DO NOT REPLY [Bug 46602] out.of.mem exception when performing batch import of document structure

2009-01-26 Thread bugzilla 
https://issues.apache.org/bugzilla/show_bug.cgi?id=46602


Carl Skymne carl.sky...@gmail.com changed:

   What|Removed |Added

Version|3.2-FINAL   |3.1




-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.

-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org

DO NOT REPLY [Bug 46602] out.of.mem exception when performing batch import of document structure

2009-01-26 Thread bugzilla 
https://issues.apache.org/bugzilla/show_bug.cgi?id=46602


Nick Burch n...@torchbox.com changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||WORKSFORME




--- Comment #1 from Nick Burch n...@torchbox.com  2009-01-26 05:08:23 PST ---
I'm pretty sure this is a bug in your code, and you're not putting the old
document out of scope before opening the new one.

However, without any code, we can't know

Please re-open the bug if you can provide your code, and have already checked
that you are really allowing objects to go out of scope


-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.

-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org