[JBoss JIRA] (TEIIDDES-1939) Preview VDB operation should validate first if there is existing Data Source
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1939?page=com.atlassian.jira.plu... ]
RH Bugzilla Integration commented on TEIIDDES-1939:
---------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1035020|https://bugzilla.redhat.com/show_bug.cgi?id=1035020] from ASSIGNED to NEW
> Preview VDB operation should validate first if there is existing Data Source
> ----------------------------------------------------------------------------
>
> Key: TEIIDDES-1939
> URL: https://issues.jboss.org/browse/TEIIDDES-1939
> Project: Teiid Designer
> Issue Type: Bug
> Components: Data Preview, VDB & Execution
> Affects Versions: 8.3
> Reporter: Ramesh Reddy
> Assignee: Mark Drilling
> Fix For: 8.3
>
>
> I am trying to create a file based source model using the "Flat File Importer". In the step one, I created a file connection factory and tried to create a source and view model based on TEXTTABLE creation wizard. This failed (this will be another defect once I figure out why). I tried to redo the wizard steps all over once I deleted empty source model it created in the last step. Every thing went OK, but after generating the source and view models I see a dialog pop-up with following exception
> {code}
> An error synchronizing and saving the Preview VDB for model "/RecursiveXMLTest/EmployeeData.xmi" occurred.
> TEIID70006 JBAS014749: Operation handler failed: Service jboss.resourceadapters.ra.file.PREVIEW_052e68a6-b711-4e7d-903f-1957fd7e9ff1_RecursiveXMLTest_EmployeeData is already registered
> {code}
> and Exception from Server log
> {code}
> 10:55:05,063 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 23) JBAS014612: Operation ("add") failed - address: ([
> ("subsystem" => "resource-adapters"),
> ("resource-adapter" => "file"),
> ("connection-definitions" => "PREVIEW_052e68a6-b711-4e7d-903f-1957fd7e9ff1_RecursiveXMLTest_EmployeeData")
> ]): org.jboss.msc.service.DuplicateServiceException: Service jboss.resourceadapters.ra.file.PREVIEW_052e68a6-b711-4e7d-903f-1957fd7e9ff1_RecursiveXMLTest_EmployeeData is already registered
> at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:154) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:227) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
> at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:561) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
> at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:201) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2228) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
> at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:307) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
> at org.jboss.as.controller.OperationContextImpl$ContextServiceBuilder.install(OperationContextImpl.java:989) [jboss-as-controller-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> at org.jboss.as.connector.subsystems.resourceadapters.ConnectionDefinitionAdd.performRuntime(ConnectionDefinitionAdd.java:84)
> at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:50) [jboss-as-controller-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:440) [jboss-as-controller-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:322) [jboss-as-controller-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:229) [jboss-as-controller-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:224) [jboss-as-controller-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:194) [jboss-as-controller-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:115) [jboss-as-controller-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:139) [jboss-as-controller-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:108) [jboss-as-controller-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:296) [jboss-as-protocol-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:518) [jboss-as-protocol-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_35]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_35]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_35]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.0.Final-redhat-1.jar:2.1.0.Final-redhat-1]
> {code}
> Looks like we are trying to create the data source again, or did not cleanup the data source from before.
--
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
10 years, 7 months
[JBoss JIRA] (TEIIDDES-1945) Creating a VDB with XML document model results in error
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1945?page=com.atlassian.jira.plu... ]
RH Bugzilla Integration commented on TEIIDDES-1945:
---------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1035019|https://bugzilla.redhat.com/show_bug.cgi?id=1035019] from ASSIGNED to NEW
> Creating a VDB with XML document model results in error
> -------------------------------------------------------
>
> Key: TEIIDDES-1945
> URL: https://issues.jboss.org/browse/TEIIDDES-1945
> Project: Teiid Designer
> Issue Type: Bug
> Components: Validation, VDB & Execution
> Affects Versions: 8.3
> Reporter: Ramesh Reddy
> Fix For: 8.4
>
> Attachments: RecursiveXMLTest.tar.gz
>
>
> Followed the E2eRecursiveXmlTextSourceTestScript_Teiid7.odt test and created various models. When it came to creating the VDB on step 5.23 the vdb creation failed with below exception.
> There is no way to further proceed with the test without a VDB. I will also attach the MPS.
> {code}
> java.lang.RuntimeException: javax.xml.bind.MarshalException
> - with linked exception:
> [org.xml.sax.SAXParseException: Duplicate unique value [Employees] declared for identity constraint of element "vdb".]
> at org.teiid.core.designer.CoreModelerPlugin.toRuntimeException(CoreModelerPlugin.java:76)
> at org.teiid.core.designer.util.OperationUtil.perform(OperationUtil.java:50)
> at org.teiid.designer.vdb.Vdb.save(Vdb.java:919)
> at org.teiid.designer.vdb.ui.editor.VdbEditor.doSave(VdbEditor.java:1768)
> at org.eclipse.ui.internal.SaveableHelper$2.run(SaveableHelper.java:150)
> at org.eclipse.ui.internal.SaveableHelper$5.run(SaveableHelper.java:276)
> at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464)
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372)
> at org.eclipse.ui.internal.WorkbenchWindow$13.run(WorkbenchWindow.java:1818)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.ui.internal.WorkbenchWindow.run(WorkbenchWindow.java:1815)
> at org.eclipse.ui.internal.SaveableHelper.runProgressMonitorOperation(SaveableHelper.java:284)
> at org.eclipse.ui.internal.SaveableHelper.runProgressMonitorOperation(SaveableHelper.java:263)
> at org.eclipse.ui.internal.SaveableHelper.savePart(SaveableHelper.java:155)
> at org.eclipse.ui.internal.WorkbenchPage.saveSaveable(WorkbenchPage.java:3769)
> at org.eclipse.ui.internal.WorkbenchPage.saveEditor(WorkbenchPage.java:3782)
> at org.eclipse.ui.internal.handlers.SaveHandler.execute(SaveHandler.java:53)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:243)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:224)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:167)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:213)
> at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:420)
> at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
> at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:452)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> Caused by: javax.xml.bind.MarshalException
> - with linked exception:
> [org.xml.sax.SAXParseException: Duplicate unique value [Employees] declared for identity constraint of element "vdb".]
> at com.sun.xml.internal.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:317)
> at com.sun.xml.internal.bind.v2.runtime.MarshallerImpl.marshal(MarshallerImpl.java:243)
> at javax.xml.bind.helpers.AbstractMarshallerImpl.marshal(AbstractMarshallerImpl.java:75)
> at org.teiid.designer.vdb.Vdb$4.tryToDo(Vdb.java:948)
> at org.teiid.core.designer.util.OperationUtil.perform(OperationUtil.java:40)
> ... 60 more
> Caused by: org.xml.sax.SAXParseException: Duplicate unique value [Employees] declared for identity constraint of element "vdb".
> at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195)
> at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:131)
> at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:384)
> at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:318)
> at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(XMLSchemaValidator.java:423)
> at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.reportSchemaError(XMLSchemaValidator.java:3188)
> at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator$UniqueValueStore.checkDuplicateValues(XMLSchemaValidator.java:3823)
> at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator$ValueStoreBase.addValue(XMLSchemaValidator.java:3549)
> at com.sun.org.apache.xerces.internal.impl.xs.identity.Field$Matcher.matched(Field.java:178)
> at com.sun.org.apache.xerces.internal.impl.xs.identity.XPathMatcher.startElement(XPathMatcher.java:331)
> at com.sun.org.apache.xerces.internal.impl.xs.identity.Selector$Matcher.startElement(Selector.java:225)
> at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.handleStartElement(XMLSchemaValidator.java:2083)
> at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.startElement(XMLSchemaValidator.java:711)
> at com.sun.org.apache.xerces.internal.jaxp.validation.ValidatorHandlerImpl.startElement(ValidatorHandlerImpl.java:551)
> at org.xml.sax.helpers.XMLFilterImpl.startElement(XMLFilterImpl.java:527)
> at com.sun.xml.internal.bind.v2.runtime.output.SAXOutput.endStartTag(SAXOutput.java:113)
> at com.sun.xml.internal.bind.v2.runtime.output.ForkXmlOutput.endStartTag(ForkXmlOutput.java:91)
> at com.sun.xml.internal.bind.v2.runtime.XMLSerializer.endAttributes(XMLSerializer.java:274)
> at com.sun.xml.internal.bind.v2.runtime.XMLSerializer.childAsXsiType(XMLSerializer.java:663)
> at com.sun.xml.internal.bind.v2.runtime.property.ArrayElementNodeProperty.serializeItem(ArrayElementNodeProperty.java:54)
> at com.sun.xml.internal.bind.v2.runtime.property.ArrayElementProperty.serializeListBody(ArrayElementProperty.java:157)
> at com.sun.xml.internal.bind.v2.runtime.property.ArrayERProperty.serializeBody(ArrayERProperty.java:141)
> at com.sun.xml.internal.bind.v2.runtime.ClassBeanInfoImpl.serializeBody(ClassBeanInfoImpl.java:306)
> at com.sun.xml.internal.bind.v2.runtime.XMLSerializer.childAsSoleContent(XMLSerializer.java:561)
> at com.sun.xml.internal.bind.v2.runtime.ClassBeanInfoImpl.serializeRoot(ClassBeanInfoImpl.java:290)
> at com.sun.xml.internal.bind.v2.runtime.XMLSerializer.childAsRoot(XMLSerializer.java:462)
> at com.sun.xml.internal.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:314)
> ... 64 more
> {code}
--
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
10 years, 7 months
[JBoss JIRA] (TEIIDDES-1943) Exception produced from deployed war
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1943?page=com.atlassian.jira.plu... ]
RH Bugzilla Integration commented on TEIIDDES-1943:
---------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1035005|https://bugzilla.redhat.com/show_bug.cgi?id=1035005] from ASSIGNED to CLOSED
> Exception produced from deployed war
> ------------------------------------
>
> Key: TEIIDDES-1943
> URL: https://issues.jboss.org/browse/TEIIDDES-1943
> Project: Teiid Designer
> Issue Type: Bug
> Components: Web Services Support
> Affects Versions: 8.3
> Reporter: Paul Richardson
> Assignee: Ted Jones
> Fix For: 8.3
>
> Attachments: E2eRESTEasyWarTestScript.odt, server.log
>
>
> Following the script 'E2eRESTEasyWarTestScript.odt', all steps check out until the final deployment of the war archive in the final section.
> Deployment of the war then trying to query it using a browser produces the following exception in the jboss log:
> {code}
> 19:35:57,191 SEVERE [org.teiid.rest] (http-/0.0.0.0:8080-1) Exception in execute: {0}: java.lang.Throwable: java.sql.SQLException: javax.resource.ResourceException: IJ000453: Unable to get managed connection for java:/BooksRestTest
> at org.teiid.rest.services.TeiidRSProviderPre.execute(TeiidRSProviderPre.java:109) [classes:]
> at org.teiid.rest.services.BooksInfo.getBook(BooksInfo.java:89) [classes:]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_25]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImp7l.java:57) [rt.jar:1.7.0_25]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_25]
> at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_25]
> at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:167) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:269) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:227) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:216) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:542) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:524) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:126) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:208) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:55) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]
> Caused by: java.sql.SQLException: javax.resource.ResourceException: IJ000453: Unable to get managed connection for java:/BooksRestTest
> at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:147)
> at org.teiid.rest.services.TeiidRSProviderPre.execute(TeiidRSProviderPre.java:63) [classes:]
> ... 29 more
> Caused by: javax.resource.ResourceException: IJ000453: Unable to get managed connection for java:/BooksRestTest
> at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.getManagedConnection(AbstractConnectionManager.java:390)
> at org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl.getManagedConnection(TxConnectionManagerImpl.java:368)
> at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:464)
> at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:139)
> ... 30 more
> Caused by: javax.resource.ResourceException: IJ000658: Unexpected throwable while trying to create a connection: null
> at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.getConnection(SemaphoreArrayListManagedConnectionPool.java:377)
> at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getSimpleConnection(AbstractPool.java:397)
> at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getConnection(AbstractPool.java:365)
> at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.getManagedConnection(AbstractConnectionManager.java:329)
> ... 33 more
> Caused by: javax.resource.ResourceException: Could not create connection
> at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.getLocalManagedConnection(LocalManagedConnectionFactory.java:282)
> at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:240)
> at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.createConnectionEventListener(SemaphoreArrayListManagedConnectionPool.java:781)
> at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.getConnection(SemaphoreArrayListManagedConnectionPool.java:344)
> ... 36 more
> Caused by: org.teiid.jdbc.TeiidSQLException: TEIID20020 Error establishing socket to host and port: localhost:9999. Reason: Unsupported version: 0
> at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:135)
> at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:71)
> at org.teiid.jdbc.SocketProfile.connect(SocketProfile.java:56)
> at org.teiid.jdbc.TeiidDriver.connect(TeiidDriver.java:107)
> at org.teiid.jdbc.TeiidDriver.connect(TeiidDriver.java:55)
> at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.getLocalManagedConnection(LocalManagedConnectionFactory.java:254)
> ... 39 more
> Caused by: org.teiid.net.socket.SingleInstanceCommunicationException: TEIID20020 Error establishing socket to host and port: localhost:9999. Reason: Unsupported version: 0
> at org.teiid.net.socket.SocketServerConnection.selectServerInstance(SocketServerConnection.java:158)
> at org.teiid.net.socket.SocketServerConnection.<init>(SocketServerConnection.java:92)
> at org.teiid.net.socket.SocketServerConnectionFactory.getConnection(SocketServerConnectionFactory.java:312)
> at org.teiid.jdbc.SocketProfile.connect(SocketProfile.java:54)
> ... 42 more
> Caused by: java.io.StreamCorruptedException: Unsupported version: 0
> at org.teiid.netty.handler.codec.serialization.CompactObjectInputStream.readStreamHeader(CompactObjectInputStream.java:57)
> at java.io.ObjectInputStream.<init>(ObjectInputStream.java:299) [rt.jar:1.7.0_25]
> at org.teiid.netty.handler.codec.serialization.CompactObjectInputStream.<init>(CompactObjectInputStream.java:48)
> at org.teiid.netty.handler.codec.serialization.ObjectDecoderInputStream.readObjectOverride(ObjectDecoderInputStream.java:107)
> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:364) [rt.jar:1.7.0_25]
> at org.teiid.net.socket.OioOjbectChannelFactory$OioObjectChannel.read(OioOjbectChannelFactory.java:109)
> at org.teiid.net.socket.SocketServerInstanceImpl.doHandshake(SocketServerInstanceImpl.java:115)
> at org.teiid.net.socket.SocketServerInstanceImpl.connect(SocketServerInstanceImpl.java:96)
> at org.teiid.net.socket.SocketServerConnectionFactory.getServerInstance(SocketServerConnectionFactory.java:271)
> at org.teiid.net.socket.SocketServerConnection.connect(SocketServerConnection.java:196)
> at org.teiid.net.socket.SocketServerConnection.selectServerInstance(SocketServerConnection.java:122)
> ... 45 more
> 19:35:57,196 WARN [org.jboss.resteasy.core.SynchronousDispatcher] (http-/0.0.0.0:8080-1) failed to execute: javax.ws.rs.WebApplicationException
> at org.teiid.rest.services.TeiidRSProviderPre.createWebApplicationException(TeiidRSProviderPre.java:153) [classes:]
> at org.teiid.rest.services.TeiidRSProviderPre.execute(TeiidRSProviderPre.java:110) [classes:]
> at org.teiid.rest.services.BooksInfo.getBook(BooksInfo.java:89) [classes:]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_25]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_25]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_25]
> at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_25]
> at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:167) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:269) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:227) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:216) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:542) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:524) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:126) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:208) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:55) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]
> {code}
> The full log is attached.
--
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
10 years, 7 months
[JBoss JIRA] (TEIIDDES-1970) VDB Containing UDF Source Model Cannot Be Deployed
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1970?page=com.atlassian.jira.plu... ]
RH Bugzilla Integration updated TEIIDDES-1970:
----------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1036675
> VDB Containing UDF Source Model Cannot Be Deployed
> --------------------------------------------------
>
> Key: TEIIDDES-1970
> URL: https://issues.jboss.org/browse/TEIIDDES-1970
> Project: Teiid Designer
> Issue Type: Bug
> Components: VDB & Execution
> Affects Versions: 8.3
> Reporter: Van Halbert
> Fix For: 8.4
>
> Attachments: YahooMps.zip
>
>
> Description of problem:
> When I try to deploy a VDB containing a relational source model that contains a user-defined function (UDF), I get an error saying "One or more models in VDB are either missing a translator name or have a translator name that is not found on the current Teiid instance." The translator name for the source model containing the UDF is empty; but the translator names for the other source models contained in the VDB are non-empty and do exist on the server.
> Version-Release number of selected component (if applicable):
> DV 6.0.0 ER4
> JBDS 7.1.0 CR1
> JBIS 4.1.3 Beta5
> Teiid Designer 8.3.0 CR1
> OS X 10.9
> How reproducible:
> Always
> Steps to Reproduce (executing E2EYahooUdfTestScript):
> Using Teiid Designer:
> 1. Select VDB containing UDF source model
> 2. Right-click > Modeling > Deploy
> Actual results:
> "VDB Not Deployed" error dialog is displayed.
> Expected results:
> VDB is deployed
> Additional info:
> None
--
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
10 years, 7 months
[JBoss JIRA] (TEIIDDES-1970) VDB Containing UDF Source Model Cannot Be Deployed
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1970?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1970:
-----------------------------------
Fix Version/s: 8.4
Teiid 8.4.x does not include an available Yahoo connector, so this use-case or E2E is not relevant to 8.3 Designer release.
Note that the MarketData.xmi source model does not include translator nor connection profile info, so no data source (JNDI) can be deployed/created.
> VDB Containing UDF Source Model Cannot Be Deployed
> --------------------------------------------------
>
> Key: TEIIDDES-1970
> URL: https://issues.jboss.org/browse/TEIIDDES-1970
> Project: Teiid Designer
> Issue Type: Bug
> Components: VDB & Execution
> Affects Versions: 8.3
> Reporter: Van Halbert
> Fix For: 8.4
>
> Attachments: YahooMps.zip
>
>
> Description of problem:
> When I try to deploy a VDB containing a relational source model that contains a user-defined function (UDF), I get an error saying "One or more models in VDB are either missing a translator name or have a translator name that is not found on the current Teiid instance." The translator name for the source model containing the UDF is empty; but the translator names for the other source models contained in the VDB are non-empty and do exist on the server.
> Version-Release number of selected component (if applicable):
> DV 6.0.0 ER4
> JBDS 7.1.0 CR1
> JBIS 4.1.3 Beta5
> Teiid Designer 8.3.0 CR1
> OS X 10.9
> How reproducible:
> Always
> Steps to Reproduce (executing E2EYahooUdfTestScript):
> Using Teiid Designer:
> 1. Select VDB containing UDF source model
> 2. Right-click > Modeling > Deploy
> Actual results:
> "VDB Not Deployed" error dialog is displayed.
> Expected results:
> VDB is deployed
> Additional info:
> None
--
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
10 years, 7 months
[JBoss JIRA] (TEIIDDES-1969) Newly Created VDB Editor Does Not Show UDF JAR
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1969?page=com.atlassian.jira.plu... ]
RH Bugzilla Integration commented on TEIIDDES-1969:
---------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1036644|https://bugzilla.redhat.com/show_bug.cgi?id=1036644] from NEW to ASSIGNED
> Newly Created VDB Editor Does Not Show UDF JAR
> ----------------------------------------------
>
> Key: TEIIDDES-1969
> URL: https://issues.jboss.org/browse/TEIIDDES-1969
> Project: Teiid Designer
> Issue Type: Bug
> Components: Editors
> Affects Versions: 8.3
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Fix For: 8.3
>
>
> Using Teiid Designer:
> Description of problem:
> I created a VDB and added models from the workspace. One of these models, was a relational function model that had a UDF JAR associated with it. When the VDB is created and the VDB editor is shown for the first time, selecting the "UDF Jars" tab does not show the UDF JAR that was added to the VDB when the VDB was created.
> Version-Release number of selected component (if applicable):
> DV 6.0.0 ER4
> JBDS 7.1.0 CR1
> JBIS 4.1.3 Beta5
> Teiid Designer 8.3.0 CR1
> OS X 10.9
> How reproducible:
> Always.
> Steps to Reproduce (using the E2EYahooUdfTestScript):
> 1. New > Teiid VDB
> 2. Select models from workspace. One of which is relational function with UDF JAR.
> 3. Click on "UDF Jars" tab of the VDB editor.
> Actual results:
> The "UDF Jars" tab of VDB editor does not show the UDF JAR file associated with the relational function model.
> Expected results:
> The UDF JAR file should be displayed when the VDB is first created.
> Additional info:
> If the VDB editor is closed and reopened, the UDF JAR is shown in the editor. So it is obviously being added to the VDB.
--
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
10 years, 7 months
[JBoss JIRA] (TEIIDDES-1971) No indication that management authentication fails
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1971?page=com.atlassian.jira.plu... ]
Max Rydahl Andersen commented on TEIIDDES-1971:
-----------------------------------------------
I moved this back to teiid designer since the issue is found to not be because of jbt core server behavior but be lack of handling bad username/password on teiid side.
If you find out how to reproduce the server side connection reset error then let us know ;)
> No indication that management authentication fails
> --------------------------------------------------
>
> Key: TEIIDDES-1971
> URL: https://issues.jboss.org/browse/TEIIDDES-1971
> Project: Teiid Designer
> Issue Type: Bug
> Reporter: Steven Hawkins
> Assignee: Rob Stryker
> Priority: Critical
>
> Running Developer Studio 7.1.0.CR1 and using either the server auto-detection or manually defining a server and using an incorrect management password results in a console log entry:
> 14:00:54,966 ERROR [org.jboss.remoting.remote.connection] (Remoting "..." read-1) JBREM000200: Remote connection failed: java.io.IOException: Connection reset by peer
> On server startup without any indication of what it means.
--
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
10 years, 7 months
[JBoss JIRA] (TEIIDDES-1971) No indication that management authentication fails
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1971?page=com.atlassian.jira.plu... ]
Max Rydahl Andersen moved JBIDE-16133 to TEIIDDES-1971:
-------------------------------------------------------
Project: Teiid Designer (was: Tools (JBoss Tools))
Key: TEIIDDES-1971 (was: JBIDE-16133)
Issue Type: Bug (was: Quality Risk)
Component/s: (was: server)
Fix Version/s: (was: 4.1.1.CR1)
> No indication that management authentication fails
> --------------------------------------------------
>
> Key: TEIIDDES-1971
> URL: https://issues.jboss.org/browse/TEIIDDES-1971
> Project: Teiid Designer
> Issue Type: Bug
> Reporter: Steven Hawkins
> Assignee: Rob Stryker
> Priority: Critical
>
> Running Developer Studio 7.1.0.CR1 and using either the server auto-detection or manually defining a server and using an incorrect management password results in a console log entry:
> 14:00:54,966 ERROR [org.jboss.remoting.remote.connection] (Remoting "..." read-1) JBREM000200: Remote connection failed: java.io.IOException: Connection reset by peer
> On server startup without any indication of what it means.
--
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
10 years, 7 months
[JBoss JIRA] (TEIIDDES-1969) Newly Created VDB Editor Does Not Show UDF JAR
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1969?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-1969.
------------------------------------
Resolution: Done
Done. Added udf file table refresh() after Vdb.addModels() call
> Newly Created VDB Editor Does Not Show UDF JAR
> ----------------------------------------------
>
> Key: TEIIDDES-1969
> URL: https://issues.jboss.org/browse/TEIIDDES-1969
> Project: Teiid Designer
> Issue Type: Bug
> Components: Editors
> Affects Versions: 8.3
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Fix For: 8.3
>
>
> Using Teiid Designer:
> Description of problem:
> I created a VDB and added models from the workspace. One of these models, was a relational function model that had a UDF JAR associated with it. When the VDB is created and the VDB editor is shown for the first time, selecting the "UDF Jars" tab does not show the UDF JAR that was added to the VDB when the VDB was created.
> Version-Release number of selected component (if applicable):
> DV 6.0.0 ER4
> JBDS 7.1.0 CR1
> JBIS 4.1.3 Beta5
> Teiid Designer 8.3.0 CR1
> OS X 10.9
> How reproducible:
> Always.
> Steps to Reproduce (using the E2EYahooUdfTestScript):
> 1. New > Teiid VDB
> 2. Select models from workspace. One of which is relational function with UDF JAR.
> 3. Click on "UDF Jars" tab of the VDB editor.
> Actual results:
> The "UDF Jars" tab of VDB editor does not show the UDF JAR file associated with the relational function model.
> Expected results:
> The UDF JAR file should be displayed when the VDB is first created.
> Additional info:
> If the VDB editor is closed and reopened, the UDF JAR is shown in the editor. So it is obviously being added to the VDB.
--
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
10 years, 7 months