[GUMP@vmgump]: Project xml-xmlbeans-v1 (in module xml-xmlbeans) failed

2012-12-07 Thread Robert Burrell Donkin
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 xml-xmlbeans-v1 has an issue affecting its community integration.
This issue affects 4 projects,
 and has been outstanding for 235 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- jmeter-svn :  Pure Java load testing and performance measurement tool.
   ...
- jmeter-test :  Pure Java load testing and performance measurement tool.
   ...
- rhino :  JavaScript for Java
- xml-xmlbeans-v1 :  XML Beans Object <-> Java Binding Tool


Full details are available at:
http://vmgump.apache.org/gump/public/xml-xmlbeans/xml-xmlbeans-v1/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -INFO- Failed with reason build failed
 -INFO- Failed to extract fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/xml-xmlbeans/xml-xmlbeans-v1/gump_work/build_xml-xmlbeans_xml-xmlbeans-v1.html
Work Name: build_xml-xmlbeans_xml-xmlbeans-v1 (Type: Build)
Work ended in a state of : Failed
Elapsed: 1 min 34 secs
Command Line: /usr/lib/jvm/java-7-oracle/bin/java -Djava.awt.headless=true 
-Dbuild.sysclasspath=only 
-Xbootclasspath/p:/srv/gump/public/workspace/xml-xerces2/build/xercesImpl.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar
 org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml -f 
build.xml bootstrap 
[Working Directory: /srv/gump/public/workspace/xml-xmlbeans]
CLASSPATH: 
/usr/lib/jvm/java-7-oracle/lib/tools.jar:/srv/gump/public/workspace/xml-xmlbeans/build/classes/common:/srv/gump/public/workspace/xml-xmlbeans/build/classes/xmlinputstream:/srv/gump/public/workspace/xml-xmlbeans/build/classes/xmlpublic:/srv/gump/public/workspace/xml-xmlbeans/external/lib/oldxbean.jar:/srv/gump/public/workspace/xml-xmlbeans/build/private/classes/zipcompare:/srv/gump/public/workspace/xml-xmlbeans/build/private/lib/easypo.jar:/srv/gump/public/workspace/xml-xmlbeans/build/private/lib/schemas.jar:/srv/gump/public/workspace/xml-xmlbeans/build/private/lib/enumtest.jar:/srv/gump/public/workspace/xml-xmlbeans/build/private/lib/drt.jar:/srv/gump/public/workspace/xml-xmlbeans/build/private/lib/xstypes.jar:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swin
 
g.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/xml-commons/java/build/resolver.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar:/srv/gump/packages/jaxen-1.1-beta-6/jaxen-1.1-beta-6.jar:/srv/gump/public/workspace/junit/dist/junit-08122012.jar:/srv/gump/public/workspace/junit/dist/junit-dep-08122012.jar
-
 [java] Comparing build/ar/xbean.jar with build/private/lib/oldxbean.jar:
 [java] schema/system/sXMLCONFIG/extensionconfig2ac2type.xsb does not match
 [java] schema/system/sXMLCONFIG/nsconfigaebatype.xsb does not match
 [java] schema/system/sXMLTOOLS/definitions05ddelemtype.xsb does not match
 [java] schema/system/sXMLTOOLS/downloadedschemaentry5f6ftype.xsb does not 
match
 [java] schema/system/sXMLTOOLS/testcase9599type.xsb does not match
 [java] schema/system/sXMLSCHEMA/all3c04type.xsb does not match
 [java] schema/system/sXMLSCHEMA/all82daelemtype.xsb does not match
 [java] schema/system/sXMLSCHEMA/annotation5abfelemtype.xsb does not match
 [java] schema/system/sXMLSCHEMA/attribute83a9type.xsb does not match
 [java] schema/system/sXMLSCHEMA/attributegroupe530type.xsb does not match
 [java] schema/system/sXMLSCHEMA/complexcontentaa7felemtype.xsb does not 
match
 [java] schema/system/sXMLSCHEMA/complexrestrictiontype1b7dtype.xsb does 
not match
 [java] schema/system/sXMLSCHEMA/complextype5dbbtype.xsb does not match
 [java] schema/system/sXMLSCHEMA/elementd189type.xsb does not match
 [java] schema/system/sXMLSCHEMA/elementinall3f33type.xsb does not match
 [java] schema/system/sXMLSCHEMA/explicitgroup4efatype.xsb does not match
 [java] schema/system/sXMLSCHEMA/extensiontypeed4ctype.xsb does not match
 [java] schema/system/sXMLSCHEMA/group7ca6type.xsb does not match
 [java] schema/system/sXMLSCHEMA/keybase3955type.xsb does not match
 [java] schema/system/sXMLSCHEMA/keyref7a1felemtype.xsb does not match
 [java] schema/system/sXMLSCHEMA/list391felemtype.xsb does not match
 [jav

[jira] [Comment Edited] (XMLBEANS-235) scomp fails with error "encoded string too long"

2012-12-07 Thread Jon Schroeder (JIRA)

[ 
https://issues.apache.org/jira/browse/XMLBEANS-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13526476#comment-13526476
 ] 

Jon Schroeder edited comment on XMLBEANS-235 at 12/7/12 4:02 PM:
-

I have the same problem with 2.6.0 version.  I am attempting to compile a 
Monster Schema.  I have attached the xsd's that are required.  The xsd to 
compile to reproduce the error is JobSeeker.xsd

I reproduced this error on Windows7 using jdk1.6.0_37 and Ubuntu using 
jdk1.6.0_27

Here is the Ubuntu output

scomp -out JobSeeker.jar JobSeeker.xsd
Time to build schema type system: 1.833 seconds
Exception in thread "main" org.apache.xmlbeans.SchemaTypeLoaderException: 
encoded string too long: 91578 bytes 
(schemaorg_apache_xmlbeans.system.s79A4106C33DD5C3CB79E9FF9B64FCECF.monsteroccupationidtier3enum7fcftype)
 - code 9
at 
org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl$StringPool.writeTo(SchemaTypeSystemImpl.java:1036)
at 
org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl$XsbReader.writeRealHeader(SchemaTypeSystemImpl.java:1617)
at 
org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl.saveType(SchemaTypeSystemImpl.java:1455)
at 
org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl.saveTypesRecursively(SchemaTypeSystemImpl.java:1331)
at 
org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl.save(SchemaTypeSystemImpl.java:1306)
at 
org.apache.xmlbeans.impl.tool.SchemaCompiler.compile(SchemaCompiler.java:1126)
at 
org.apache.xmlbeans.impl.tool.SchemaCompiler.main(SchemaCompiler.java:373)

  was (Author: jonschro):
I have the same problem with 2.6.0 version.  I am attempting to compile a 
Monster Schema.  I have attached the xsd's that are required.  The xsd to 
compile to reproduce the error is JobSeeker.xsd
  
> scomp fails with error "encoded string too long"
> 
>
> Key: XMLBEANS-235
> URL: https://issues.apache.org/jira/browse/XMLBEANS-235
> Project: XMLBeans
>  Issue Type: Bug
>Affects Versions: Version 2.1
> Environment: WIndows XP, J2SE Version 1.5.0 (build 1.5.0_06-b05)
>Reporter: Chris Isbell
>Priority: Blocker
> Attachments: Common.xsd, Document.xsd, Enumerations.xsd, 
> JobSearchAgent.xsd, JobSeeker.xsd
>
>
> scomp fails with the following output:
> Time to build schema type system: 1.492 seconds
> Exception in thread "main" org.apache.xmlbeans.SchemaTypeLoaderException: 
> encoded string too long: 80643 bytes 
> (schemaorg_apache_xmlbeans.system.sD8C47734011B153A3D6BBC3BCCA9AC04.allassetsmodelgroup)
>  - code 9
>   at 
> org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl$StringPool.writeTo(SchemaTypeSystemImpl.java:1021)
>   at 
> org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl$XsbReader.writeRealHeader(SchemaTypeSystemImpl.java:1602)
>   at 
> org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl.saveModelGroup(SchemaTypeSystemImpl.java:1406)
>   at 
> org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl.saveModelGroups(SchemaTypeSystemImpl.java:1347)
>   at 
> org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl.save(SchemaTypeSystemImpl.java:1296)
>   at 
> org.apache.xmlbeans.impl.tool.SchemaCompiler.compile(SchemaCompiler.java:1098)
>   at 
> org.apache.xmlbeans.impl.tool.SchemaCompiler.main(SchemaCompiler.java:368)
> The problem appears to be with the line "output.writeUTF(str);" in the method 
> writeTo in class org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl (line 
> 1016). java.io.DataOutputStream.writeUTF has an implicit 64K byte length 
> limit (because it stores the length in a two-byte integer) and this limit is 
> being exceeded.
> The schema I am compiling comes from a third party and it is unlikely that it 
> can be modified to work around this problem.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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



[jira] [Comment Edited] (XMLBEANS-235) scomp fails with error "encoded string too long"

2012-12-07 Thread Jon Schroeder (JIRA)

[ 
https://issues.apache.org/jira/browse/XMLBEANS-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13526476#comment-13526476
 ] 

Jon Schroeder edited comment on XMLBEANS-235 at 12/7/12 4:00 PM:
-

I have the same problem with 2.6.0 version.  I am attempting to compile a 
Monster Schema.  I have attached the xsd's that are required.  The xsd to 
compile to reproduce the error is JobSeeker.xsd

  was (Author: jonschro):
I have the same problem with 2.6.0 version.  I am attempting to compile a 
Monster Schema.  I have attached the xsd's that are required.  The xsd to 
compile is JobSeeker.xsd
  
> scomp fails with error "encoded string too long"
> 
>
> Key: XMLBEANS-235
> URL: https://issues.apache.org/jira/browse/XMLBEANS-235
> Project: XMLBeans
>  Issue Type: Bug
>Affects Versions: Version 2.1
> Environment: WIndows XP, J2SE Version 1.5.0 (build 1.5.0_06-b05)
>Reporter: Chris Isbell
>Priority: Blocker
> Attachments: Common.xsd, Document.xsd, Enumerations.xsd, 
> JobSearchAgent.xsd, JobSeeker.xsd
>
>
> scomp fails with the following output:
> Time to build schema type system: 1.492 seconds
> Exception in thread "main" org.apache.xmlbeans.SchemaTypeLoaderException: 
> encoded string too long: 80643 bytes 
> (schemaorg_apache_xmlbeans.system.sD8C47734011B153A3D6BBC3BCCA9AC04.allassetsmodelgroup)
>  - code 9
>   at 
> org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl$StringPool.writeTo(SchemaTypeSystemImpl.java:1021)
>   at 
> org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl$XsbReader.writeRealHeader(SchemaTypeSystemImpl.java:1602)
>   at 
> org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl.saveModelGroup(SchemaTypeSystemImpl.java:1406)
>   at 
> org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl.saveModelGroups(SchemaTypeSystemImpl.java:1347)
>   at 
> org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl.save(SchemaTypeSystemImpl.java:1296)
>   at 
> org.apache.xmlbeans.impl.tool.SchemaCompiler.compile(SchemaCompiler.java:1098)
>   at 
> org.apache.xmlbeans.impl.tool.SchemaCompiler.main(SchemaCompiler.java:368)
> The problem appears to be with the line "output.writeUTF(str);" in the method 
> writeTo in class org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl (line 
> 1016). java.io.DataOutputStream.writeUTF has an implicit 64K byte length 
> limit (because it stores the length in a two-byte integer) and this limit is 
> being exceeded.
> The schema I am compiling comes from a third party and it is unlikely that it 
> can be modified to work around this problem.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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



[jira] [Issue Comment Deleted] (XMLBEANS-235) scomp fails with error "encoded string too long"

2012-12-07 Thread Jon Schroeder (JIRA)

 [ 
https://issues.apache.org/jira/browse/XMLBEANS-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jon Schroeder updated XMLBEANS-235:
---

Comment: was deleted

(was: JobSeeker.xsd is the one that needs to be compiled)

> scomp fails with error "encoded string too long"
> 
>
> Key: XMLBEANS-235
> URL: https://issues.apache.org/jira/browse/XMLBEANS-235
> Project: XMLBeans
>  Issue Type: Bug
>Affects Versions: Version 2.1
> Environment: WIndows XP, J2SE Version 1.5.0 (build 1.5.0_06-b05)
>Reporter: Chris Isbell
>Priority: Blocker
> Attachments: Common.xsd, Document.xsd, Enumerations.xsd, 
> JobSearchAgent.xsd, JobSeeker.xsd
>
>
> scomp fails with the following output:
> Time to build schema type system: 1.492 seconds
> Exception in thread "main" org.apache.xmlbeans.SchemaTypeLoaderException: 
> encoded string too long: 80643 bytes 
> (schemaorg_apache_xmlbeans.system.sD8C47734011B153A3D6BBC3BCCA9AC04.allassetsmodelgroup)
>  - code 9
>   at 
> org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl$StringPool.writeTo(SchemaTypeSystemImpl.java:1021)
>   at 
> org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl$XsbReader.writeRealHeader(SchemaTypeSystemImpl.java:1602)
>   at 
> org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl.saveModelGroup(SchemaTypeSystemImpl.java:1406)
>   at 
> org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl.saveModelGroups(SchemaTypeSystemImpl.java:1347)
>   at 
> org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl.save(SchemaTypeSystemImpl.java:1296)
>   at 
> org.apache.xmlbeans.impl.tool.SchemaCompiler.compile(SchemaCompiler.java:1098)
>   at 
> org.apache.xmlbeans.impl.tool.SchemaCompiler.main(SchemaCompiler.java:368)
> The problem appears to be with the line "output.writeUTF(str);" in the method 
> writeTo in class org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl (line 
> 1016). java.io.DataOutputStream.writeUTF has an implicit 64K byte length 
> limit (because it stores the length in a two-byte integer) and this limit is 
> being exceeded.
> The schema I am compiling comes from a third party and it is unlikely that it 
> can be modified to work around this problem.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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



[jira] [Commented] (XMLBEANS-235) scomp fails with error "encoded string too long"

2012-12-07 Thread Jon Schroeder (JIRA)

[ 
https://issues.apache.org/jira/browse/XMLBEANS-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13526476#comment-13526476
 ] 

Jon Schroeder commented on XMLBEANS-235:


I have the same problem with 2.6.0 version.  I am attempting to compile a 
Monster Schema.  I have attached the xsd's that are required.  The xsd to 
compile is JobSeeker.xsd

> scomp fails with error "encoded string too long"
> 
>
> Key: XMLBEANS-235
> URL: https://issues.apache.org/jira/browse/XMLBEANS-235
> Project: XMLBeans
>  Issue Type: Bug
>Affects Versions: Version 2.1
> Environment: WIndows XP, J2SE Version 1.5.0 (build 1.5.0_06-b05)
>Reporter: Chris Isbell
>Priority: Blocker
> Attachments: Common.xsd, Document.xsd, Enumerations.xsd, 
> JobSearchAgent.xsd, JobSeeker.xsd
>
>
> scomp fails with the following output:
> Time to build schema type system: 1.492 seconds
> Exception in thread "main" org.apache.xmlbeans.SchemaTypeLoaderException: 
> encoded string too long: 80643 bytes 
> (schemaorg_apache_xmlbeans.system.sD8C47734011B153A3D6BBC3BCCA9AC04.allassetsmodelgroup)
>  - code 9
>   at 
> org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl$StringPool.writeTo(SchemaTypeSystemImpl.java:1021)
>   at 
> org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl$XsbReader.writeRealHeader(SchemaTypeSystemImpl.java:1602)
>   at 
> org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl.saveModelGroup(SchemaTypeSystemImpl.java:1406)
>   at 
> org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl.saveModelGroups(SchemaTypeSystemImpl.java:1347)
>   at 
> org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl.save(SchemaTypeSystemImpl.java:1296)
>   at 
> org.apache.xmlbeans.impl.tool.SchemaCompiler.compile(SchemaCompiler.java:1098)
>   at 
> org.apache.xmlbeans.impl.tool.SchemaCompiler.main(SchemaCompiler.java:368)
> The problem appears to be with the line "output.writeUTF(str);" in the method 
> writeTo in class org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl (line 
> 1016). java.io.DataOutputStream.writeUTF has an implicit 64K byte length 
> limit (because it stores the length in a two-byte integer) and this limit is 
> being exceeded.
> The schema I am compiling comes from a third party and it is unlikely that it 
> can be modified to work around this problem.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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



[jira] [Updated] (XMLBEANS-235) scomp fails with error "encoded string too long"

2012-12-07 Thread Jon Schroeder (JIRA)

 [ 
https://issues.apache.org/jira/browse/XMLBEANS-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jon Schroeder updated XMLBEANS-235:
---

Attachment: JobSeeker.xsd
JobSearchAgent.xsd
Enumerations.xsd
Document.xsd
Common.xsd

JobSeeker.xsd is the one that needs to be compiled

> scomp fails with error "encoded string too long"
> 
>
> Key: XMLBEANS-235
> URL: https://issues.apache.org/jira/browse/XMLBEANS-235
> Project: XMLBeans
>  Issue Type: Bug
>Affects Versions: Version 2.1
> Environment: WIndows XP, J2SE Version 1.5.0 (build 1.5.0_06-b05)
>Reporter: Chris Isbell
>Priority: Blocker
> Attachments: Common.xsd, Document.xsd, Enumerations.xsd, 
> JobSearchAgent.xsd, JobSeeker.xsd
>
>
> scomp fails with the following output:
> Time to build schema type system: 1.492 seconds
> Exception in thread "main" org.apache.xmlbeans.SchemaTypeLoaderException: 
> encoded string too long: 80643 bytes 
> (schemaorg_apache_xmlbeans.system.sD8C47734011B153A3D6BBC3BCCA9AC04.allassetsmodelgroup)
>  - code 9
>   at 
> org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl$StringPool.writeTo(SchemaTypeSystemImpl.java:1021)
>   at 
> org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl$XsbReader.writeRealHeader(SchemaTypeSystemImpl.java:1602)
>   at 
> org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl.saveModelGroup(SchemaTypeSystemImpl.java:1406)
>   at 
> org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl.saveModelGroups(SchemaTypeSystemImpl.java:1347)
>   at 
> org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl.save(SchemaTypeSystemImpl.java:1296)
>   at 
> org.apache.xmlbeans.impl.tool.SchemaCompiler.compile(SchemaCompiler.java:1098)
>   at 
> org.apache.xmlbeans.impl.tool.SchemaCompiler.main(SchemaCompiler.java:368)
> The problem appears to be with the line "output.writeUTF(str);" in the method 
> writeTo in class org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl (line 
> 1016). java.io.DataOutputStream.writeUTF has an implicit 64K byte length 
> limit (because it stores the length in a two-byte integer) and this limit is 
> being exceeded.
> The schema I am compiling comes from a third party and it is unlikely that it 
> can be modified to work around this problem.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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



[jira] [Commented] (XMLBEANS-494) ArrayIndexOutOfBoundsException on query

2012-12-07 Thread Paulo Henrique Leal (JIRA)

[ 
https://issues.apache.org/jira/browse/XMLBEANS-494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13526320#comment-13526320
 ] 

Paulo Henrique Leal commented on XMLBEANS-494:
--

Sorry, I dont know how I got to the xmlbeans forum. You are correct, this is 
meant to the openJPA. So sorry about this.

> ArrayIndexOutOfBoundsException on query
> ---
>
> Key: XMLBEANS-494
> URL: https://issues.apache.org/jira/browse/XMLBEANS-494
> Project: XMLBeans
>  Issue Type: Bug
>Affects Versions: Version 2.2
> Environment: Websphere 8.0.0.3
>Reporter: Paulo Henrique Leal
>
> Running a query I get a message: openjpa.Runtime: Warn: Supplied user 
> parameters "[1, 2, 3, 4, 5]" do not match expected parameters "[1, 1, 2, 3, 
> 4, 5]" for the prepared query 
> the query is like
> SELECT 
> test 
> FROM 
> com.phleal.persistence.model.Test test 
> WHERE 
> EXISTS (
> SELECT attr
> FROM com.phleal.persistence.model.TestAttribute attr
> WHERE attr.test = test AND attr.namespace.namespaceURI = ?1 AND attr.name = 
> ?2 AND ( ( attr.valueTypeId = ?3 AND attr.stringValue = ?4 ) )
>  )
>  AND ?5 MEMBER OF reg.testTypes
>  AND reg.testCompleted = false
>  After this Warning I get an ArrayIndexOutOfBoundsException:
> Failed to execute query SELECT 
> test 
> FROM 
> com.phleal.persistence.model.Test test 
> WHERE 
> EXISTS (
> SELECT attr
> FROM com.phleal.persistence.model.TestAttribute attr
> WHERE attr.test = test AND attr.namespace.namespaceURI = ?1 AND attr.name = 
> ?2 AND ( ( attr.valueTypeId = ?3 AND attr.stringValue = ?4 ) )
>  )
>  AND ?5 MEMBER OF reg.testTypes
>  AND reg.testCompleted = false". Check the query syntax for correctness. 
> See nested exception for details..
>   nonfatal user error> org.apache.openjpa.persistence.ArgumentException: Failed 
> to execute query "SELECT 
> test 
> FROM 
> com.phleal.persistence.model.Test test 
> WHERE 
> EXISTS (
> SELECT attr
> FROM com.phleal.persistence.model.TestAttribute attr
> WHERE attr.test = test AND attr.namespace.namespaceURI = ?1 AND attr.name = 
> ?2 AND ( ( attr.valueTypeId = ?3 AND attr.stringValue = ?4 ) )
>  )
>  AND ?5 MEMBER OF reg.testTypes
>  AND reg.testCompleted = false". Check the query syntax for correctness. 
> See nested exception for details.
>   at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:872)
>   at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:794)
>   at 
> org.apache.openjpa.kernel.DelegatingQuery.execute(DelegatingQuery.java:542)
>   at org.apache.openjpa.persistence.QueryImpl.execute(QueryImpl.java:286)
>   at 
> org.apache.openjpa.persistence.QueryImpl.getResultList(QueryImpl.java:302)
>   at 
> com.phleal.persistence.TestManager.getRelatedTest(TestManager.java:1794)
> .
> .
> .
>   at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
>   at 
> com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)
>   at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
>   at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1783)
> Caused by: java.lang.ArrayIndexOutOfBoundsException: Array index out of 
> range: 5
>   at 
> org.apache.openjpa.jdbc.kernel.PreparedSQLStoreQuery$PreparedSQLExecutor.toParameterArray(PreparedSQLStoreQuery.java:161)
>   at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:857)
>   ... 89 more
> I am sure I only pass 5 attributes to the query, I don't know what could 
> generate the "[1, 1, 2, 3, 4, 5]" from the message.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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



[jira] [Created] (XMLBEANS-495) StackOverflowError when parsing a large number of characters in an XML element

2012-12-07 Thread Mandy Warren (JIRA)
Mandy Warren created XMLBEANS-495:
-

 Summary: StackOverflowError when parsing a large number of 
characters in an XML element
 Key: XMLBEANS-495
 URL: https://issues.apache.org/jira/browse/XMLBEANS-495
 Project: XMLBeans
  Issue Type: Bug
  Components: Validator
Affects Versions: Version 2.6
 Environment: All
Reporter: Mandy Warren


When XMLBeans validates a very long XML String (1000 or more chars), it 
generates a StackOverFlowException as shown below. In the schema for this 
element I have defined a pattern and a min/max length but XMLBeans is applying 
the pattern first before checking the length. The solution is the fix applied 
to the class RegularExpression in xerces - see 
https://issues.apache.org/jira/browse/XERCESJ-589 which went into version 2.11. 










Exception in thread "main" java.lang.StackOverflowError
at 
org.apache.xmlbeans.impl.regex.RegularExpression.matchString(RegularExpression.java:1662)
at 
org.apache.xmlbeans.impl.regex.RegularExpression.matchString(RegularExpression.java:1872)
at 
org.apache.xmlbeans.impl.regex.RegularExpression.matchString(RegularExpression.java:1872)
at 
org.apache.xmlbeans.impl.regex.RegularExpression.matchString(RegularExpression.java:1872)
at 
org.apache.xmlbeans.impl.regex.RegularExpression.matchString(RegularExpression.java:1872)
at 
org.apache.xmlbeans.impl.regex.RegularExpression.matchString(RegularExpression.java:1872)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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