-
Bug
-
Resolution: Cannot Reproduce
-
High
-
3.5.3
-
Fogbugz: Win2003R2, SQLExpress
Atlassian JIRA(v4.4.4#664-r167664) Win2k8R2, SQL2008
Error from JIRA: Unexpected failure occurred. Importer will stop immediately. Data maybe in an unstable state
----------------------------------------------------------------------------------------------
Logfile:
----------------------------------------------------------------------------------------------
2012-02-16 10:21:12,736 INFO - Import started by admin using com.atlassian.jira.plugins.importer.imports.fogbugz.FogBugzDataBean
2012-02-16 10:21:12,751 INFO - ------------------------------
2012-02-16 10:21:12,751 INFO - Importing: Users
2012-02-16 10:21:12,751 INFO - ------------------------------
2012-02-16 10:21:12,751 INFO - Only new items will be imported
2012-02-16 10:21:12,892 INFO - 32 users associated with import.
2012-02-16 10:21:13,095 INFO - Imported user Alf Burghardt (aburghardt)
2012-02-16 10:21:13,189 INFO - Imported user Erwin Sauter (esauter)
2012-02-16 10:21:13,267 INFO - Imported user Exxcellent (exxcellent)
2012-02-16 10:21:13,377 INFO - Imported user G�nther Hafner (ghafner)
2012-02-16 10:21:13,502 INFO - Imported user Martin Wimmer (mwimmer)
2012-02-16 10:21:13,595 INFO - Imported user Roland Fr�wis (rfr�wis)
2012-02-16 10:21:13,674 INFO - Imported user Sourish Halder (shalder)
2012-02-16 10:21:13,799 INFO - Imported user Thomas Hassler (thassler)
2012-02-16 10:21:13,877 INFO - Imported user Volker Manusch (vmanusch)
2012-02-16 10:21:13,877 INFO - ------------------------------
2012-02-16 10:21:13,877 INFO - Finished Importing : Users
2012-02-16 10:21:13,877 INFO - ------------------------------
2012-02-16 10:21:13,877 INFO - 9 users successfully created.
2012-02-16 10:21:13,877 INFO - Retrieving custom fields...
2012-02-16 10:21:13,877 INFO - Retrieving projects...
2012-02-16 10:21:13,877 INFO - ------------------------------
2012-02-16 10:21:13,877 INFO - Importing: Issues
2012-02-16 10:21:13,877 INFO - ------------------------------
2012-02-16 10:21:13,877 INFO - Only new items will be imported
2012-02-16 10:21:13,955 INFO - ------------------------------
2012-02-16 10:21:13,955 INFO - Finished Importing : Issues
2012-02-16 10:21:13,955 INFO - ------------------------------
2012-02-16 10:21:13,955 ERROR - Unexpected failure occurred. Importer will stop immediately. Data maybe in an unstable state
com.atlassian.jira.plugins.importer.SQLRuntimeException: Incorrect syntax near ')'.
at com.atlassian.jira.plugins.importer.web.JdbcConnection.queryDb(JdbcConnection.java:177)
at com.atlassian.jira.plugins.importer.web.JdbcConnection.queryDb(JdbcConnection.java:146)
at com.atlassian.jira.plugins.importer.imports.fogbugz.FogBugzDataBean.getTotalIssues(FogBugzDataBean.java:96)
at com.atlassian.jira.plugins.importer.imports.importer.impl.DefaultJiraDataImporter.doImport(DefaultJiraDataImporter.java:295)
at com.atlassian.jira.plugins.importer.imports.importer.impl.ImporterCallable.call(ImporterCallable.java:25)
at com.atlassian.jira.plugins.importer.imports.importer.impl.ImporterCallable.call(ImporterCallable.java:14)
at com.atlassian.jira.task.TaskManagerImpl$TaskCallableDecorator.call(TaskManagerImpl.java:359)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at com.atlassian.multitenant.impl.DefaultMultiTenantManager.runForTenant(DefaultMultiTenantManager.java:61)
at com.atlassian.multitenant.juc.MultiTenantExecutors$WrappedRunnable.run(MultiTenantExecutors.java:160)
at com.atlassian.jira.task.ForkedThreadExecutor$ForkedRunnableDecorator.run(ForkedThreadExecutor.java:249)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.sql.SQLException: Incorrect syntax near ')'.
at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:368)
at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2820)
at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2258)
at net.sourceforge.jtds.jdbc.TdsCore.getMoreResults(TdsCore.java:632)
at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQLQuery(JtdsStatement.java:477)
at net.sourceforge.jtds.jdbc.JtdsPreparedStatement.executeQuery(JtdsPreparedStatement.java:778)
at com.atlassian.jira.plugins.importer.web.JdbcConnection.queryDb(JdbcConnection.java:162)
... 15 more
2012-02-16 10:21:13,955 INFO - No issues need to be reindexed.
----------------------------------------------------------------------------------------------
Configuration:
----------------------------------------------------------------------------------------------
{
"field" :
,
"link" :
,
"value" : {
"sStatus" :
,
"workflowScheme" : "IZfM",
"sStatus (Resolution)" :
},
"projectLead" : {
},
"projectName" : {
},
"projectKey" : {
},
"projectSelection" :
}
[JIM-680] Fogbugz Import from Version 8.6.50 failed
| Resolution | New: Cannot Reproduce [ 5 ] | |
| Status | Original: Closed [ 6 ] | New: Closed [ 6 ] |
| Workflow | Original: JIM Project Workflow (Software Simplified) [ 1606809 ] | New: JIM - workflow v2 [ 1611283 ] |
Hi Gary,
I'm looking at the issue again. I wasn't able to reproduce the original problem when using FogBugz 8.7.60 with a database access.
Looking at the logs and comparing it with the code I see a strange thing - there's "Retrieving projects..." in the log but actually no projects were imported (there should be message in the log). That's really strange and that would be a cause for the error you got. If no projects were selected the import should end up exactly with the error you got.
So I wonder how is it possible no projects were selected? What browser did you use? Can you try importing again with FogBugz importer and see if it happens again when you use Firefox or Chrome?
Cheers,
Pawel
Sorry so late on reply.
I've been using 4.1.4 all along. Someone recommended importing using the Fogbugz on demand import. This is working for all our tables except our three largest resulting in the same error as posted before.
Gary
I have installed the newest FogBugz 8.7.60 for tests and I don't get any errors importing using JIM 4.1.4. Gary can you try out JIM 4.1.4?
Unfortunately when the exception happens JIM doesn't have the idea which issue is broken so we can't report it.
I guess in your case the easiest option would be to search the database (you're looking for <?xml). You can also try running the same search query importer use (FogBugz API is documented here http://fogbugz.stackexchange.com/fogbugz-xml-api), after you log in you want to issue search command, here's snippet from our code that we use to build the query:
final UriBuilder uri = UriBuilder.fromUri(apiUri) .queryParam("cmd", "search") .queryParam("q", String.format("project:=%s", projectId)) .queryParam("cols", "ixBug,tags,fOpen,sTitle,sArea,sComputer," + "ixPersonAssignedTo,ixPersonOpenedBy,sStatus,ixPriority,sPriority,sFixFor,sVersion,sCustomerEmail," + "dtOpened,dtClosed,dtResolved,hrsOrigEst,hrsElapsed,hrsCurrEst,sCategory,events");
We have thousands of issues. How can we know which one is offending? I don't see it in the exception output.
@Gary, that's a problem with FogBugz XML output - when you have an issue that includes XML inside of the description (or comments) it will be incorrectly presented in the remote API. They do not escape or encode content served by the remote endpoint so you end up with XML content inside another XML content which breaks the parser.
The only thing you can do is to modify offending issue and change XML so it will not break the parser.
Going to close it. I'm not able to reproduce the problem. If you have any updates please re-open it.