Bug 753715 - Build 16 - error pushing edited spec
Summary: Build 16 - error pushing edited spec
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: PressGang CCMS
Classification: Community
Component: CSProcessor
Version: 1.x
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Lee Newson
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-14 09:35 UTC by Joshua Wulf
Modified: 2014-10-19 22:59 UTC (History)
2 users (show)

Fixed In Version: 0.16.1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-25 00:04:39 UTC


Attachments (Terms of Use)

Description Joshua Wulf 2011-11-14 09:35:37 UTC
[jwulf@gaura scratch]$ skynet push -cn ~/Work/Zanata/Skynet\ integration\ POC/Zanata-all-topics.spec 
Skynet client version: 0.13.1
Loading configuration from /home/jwulf/.config/skynet.ini
Web Service at http://localhost:8080/ version: 0.16.0

ERROR: Look-behind group does not have an obvious maximum length near index 29
.*(?<!\\)\[(?<Brackets>(.|
)*?)(?<!\\)\][ ]*$
                             ^
ERROR: Look-behind group does not have an obvious maximum length near index 29
.*(?<!\\)\[(?<Brackets>(.|
)*?)(?<!\\)\][ ]*$
                             ^

Comment 1 Lee Newson 2011-11-14 22:34:14 UTC
Do you have Java 7 installed and running for the server?

I missed it in the original email but added it to the notes on the 0.16.0 Release Tracker.

If required I can use a Library instead of the Java 7 API however that shouldn't be required because going by http://sourceforge.net/p/topicindex/blog/2011/10/this-week-in-skynet-921/ Skynet requires Java 7 to run now as well.

Comment 2 Joshua Wulf 2011-11-15 02:41:11 UTC
With Java 7:


12:39:59,838 INFO  [com.redhat.contentspec.service.WebService] (http--0.0.0.0-8080-1) Received Push Request
12:39:59,838 INFO  [com.redhat.contentspec.service.WebService] (http--0.0.0.0-8080-1) Processing Push Request
12:39:59,894 INFO  [org.hibernate.jdbc.ConnectionManager] (http--0.0.0.0-8080-1) forcing batcher resource cleanup on transaction completion; forgot to close ScrollableResults/Iterator?
12:40:00,114 INFO  [com.redhat.contentspec.processor.ContentSpecProcessor] (http--0.0.0.0-8080-1) The Content Specification is valid.
12:40:00,115 WARN  [com.redhat.contentspec.processor.ContentSpecProcessor] (http--0.0.0.0-8080-1) Note: All descriptions, tags, source urls and writers will be ignored for existing Topics.
12:40:00,133 ERROR [com.redhat.contentspec.database.utils.TransactionHandler] (http--0.0.0.0-8080-1) Hibernate Transaction rollback.
12:40:00,135 ERROR [stderr] (http--0.0.0.0-8080-1) java.lang.Exception: The TopicToTopicRelationship Tuple's were unable to be deleted!
12:40:00,135 ERROR [stderr] (http--0.0.0.0-8080-1) 	at com.redhat.contentspec.database.DBWriter.cleanExistingData(DBWriter.java:589)
12:40:00,135 ERROR [stderr] (http--0.0.0.0-8080-1) 	at com.redhat.contentspec.processor.Scope.saveScope(Scope.java:207)
12:40:00,135 ERROR [stderr] (http--0.0.0.0-8080-1) 	at com.redhat.contentspec.processor.ContentSpecProcessor.validateContentSpec(ContentSpecProcessor.java:220)
12:40:00,135 ERROR [stderr] (http--0.0.0.0-8080-1) 	at com.redhat.contentspec.processor.ContentSpecProcessor.readFileData(ContentSpecProcessor.java:153)
12:40:00,136 ERROR [stderr] (http--0.0.0.0-8080-1) 	at com.redhat.contentspec.service.WebService.push(WebService.java:120)
12:40:00,136 ERROR [stderr] (http--0.0.0.0-8080-1) 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
12:40:00,136 ERROR [stderr] (http--0.0.0.0-8080-1) 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
12:40:00,136 ERROR [stderr] (http--0.0.0.0-8080-1) 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
12:40:00,136 ERROR [stderr] (http--0.0.0.0-8080-1) 	at java.lang.reflect.Method.invoke(Method.java:601)
12:40:00,136 ERROR [stderr] (http--0.0.0.0-8080-1) 	at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:140)
12:40:00,136 ERROR [stderr] (http--0.0.0.0-8080-1) 	at org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:255)
12:40:00,136 ERROR [stderr] (http--0.0.0.0-8080-1) 	at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:220)
12:40:00,136 ERROR [stderr] (http--0.0.0.0-8080-1) 	at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:209)
12:40:00,137 ERROR [stderr] (http--0.0.0.0-8080-1) 	at org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:519)
12:40:00,137 ERROR [stderr] (http--0.0.0.0-8080-1) 	at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:496)
12:40:00,137 ERROR [stderr] (http--0.0.0.0-8080-1) 	at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:119)
12:40:00,137 ERROR [stderr] (http--0.0.0.0-8080-1) 	at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:208)
12:40:00,137 ERROR [stderr] (http--0.0.0.0-8080-1) 	at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:55)
12:40:00,137 ERROR [stderr] (http--0.0.0.0-8080-1) 	at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50)
12:40:00,137 ERROR [stderr] (http--0.0.0.0-8080-1) 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
12:40:00,137 ERROR [stderr] (http--0.0.0.0-8080-1) 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329)
12:40:00,137 ERROR [stderr] (http--0.0.0.0-8080-1) 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
12:40:00,138 ERROR [stderr] (http--0.0.0.0-8080-1) 	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)
12:40:00,138 ERROR [stderr] (http--0.0.0.0-8080-1) 	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)
12:40:00,138 ERROR [stderr] (http--0.0.0.0-8080-1) 	at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:139)
12:40:00,138 ERROR [stderr] (http--0.0.0.0-8080-1) 	at org.jboss.as.web.NamingValve.invoke(NamingValve.java:57)
12:40:00,138 ERROR [stderr] (http--0.0.0.0-8080-1) 	at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:49)
12:40:00,138 ERROR [stderr] (http--0.0.0.0-8080-1) 	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154)
12:40:00,138 ERROR [stderr] (http--0.0.0.0-8080-1) 	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
12:40:00,138 ERROR [stderr] (http--0.0.0.0-8080-1) 	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
12:40:00,138 ERROR [stderr] (http--0.0.0.0-8080-1) 	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362)
12:40:00,139 ERROR [stderr] (http--0.0.0.0-8080-1) 	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)
12:40:00,139 ERROR [stderr] (http--0.0.0.0-8080-1) 	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:667)
12:40:00,139 ERROR [stderr] (http--0.0.0.0-8080-1) 	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:952)
12:40:00,139 ERROR [stderr] (http--0.0.0.0-8080-1) 	at java.lang.Thread.run(Thread.java:722)
12:40:00,139 ERROR [com.redhat.contentspec.processor.Scope] (http--0.0.0.0-8080-1) An error occurred when inserting into the database please try again.
12:40:00,139 ERROR [com.redhat.contentspec.processor.ContentSpecProcessor] (http--0.0.0.0-8080-1) An error occurred when inserting into the database please try again.
12:40:00,140 INFO  [com.redhat.contentspec.service.WebService] (http--0.0.0.0-8080-1) Processed Push Request

Comment 3 Joshua Wulf 2011-11-15 03:11:29 UTC
Reproducible. 

I pushed this same content spec as new - worked fine. 
Pulled the post version
Added a single comment line to it
Pushed as edited spec
Got the same error

Comment 4 Lee Newson 2011-11-15 03:46:46 UTC
Found the issue. The problem was that I missed a check on that delete command and as such if you had no relationships the rollback would occur. I've now added a check to make sure that a relationship exists before attempting to delete the data.


Note You need to log in before you can comment on or make changes to this bug.