[JBoss JIRA] (TEIID-2407) Support temporary table on commit behavior
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2407?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-2407:
----------------------------------
Fix Version/s: 8.6
(was: 8.5)
Bumping to 8.6. Given our local scoping behavior on commit drop is largely not needed (and not yet applicable to our global temporary tables). On commit delete rows is still worthwhile to pursue.
> Support temporary table on commit behavior
> ------------------------------------------
>
> Key: TEIID-2407
> URL: https://issues.jboss.org/browse/TEIID-2407
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.6
>
>
> Now that our temporary tables are transactionally aware we should support the on commit clause.
> Our current default for on commit is effectively "preserve rows", which is contrary to the sql specification. We should also offer delete rows and possible drop (similar to pg sql).
--
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
12 years, 8 months
[JBoss JIRA] (TEIID-2602) Add clearer message that a VDB cannot be deployed without a JNDI name specified in the .vdb
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2602?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2602:
---------------------------------------
Can you clarify -
> but the server doesn't like it that there's no JNDI specified
That's not expected. If a connection is not needed you should deploy just fine. We even have an integration test (no connection-jndi-name attribute) of that scenario with loopback.
> Can Teiid preempt this and produce a clearer message that its because there's no JNDI specified?
If no JNDI is specified, then you should not get this message. Do you mean that you get this error if you use something invalid like an empty string?
> Add clearer message that a VDB cannot be deployed without a JNDI name specified in the .vdb
> -------------------------------------------------------------------------------------------
>
> Key: TEIID-2602
> URL: https://issues.jboss.org/browse/TEIID-2602
> Project: Teiid
> Issue Type: Enhancement
> Components: Server
> Affects Versions: 8.4.1
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Priority: Minor
>
> Created a sample VDB in designer, for which the model is to use the loopback connector. Did not specify a JNDI reference, because it doesn't need one. However, the VDB can't be deployed from Designer because there's no connection info for this model. So I hand deployed, but the server doesn't like it that there's no JNDI specified (if I add the JNDI reference, it deploys fine). You get this error:
> 08:10:17,265 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.deployment.unit."Sample.vdb".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."Sample.vdb".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment "Sample.vdb"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:127) [jboss-as-server-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_13]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_13]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_13]
> Caused by: java.lang.IllegalArgumentException: Empty name segment is not allowed for java
> at org.jboss.msc.service.ServiceName.of(ServiceName.java:85) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
> at org.jboss.msc.service.ServiceName.append(ServiceName.java:112) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
> at org.jboss.as.naming.deployment.ContextNames.buildServiceName(ContextNames.java:183)
> at org.jboss.as.naming.deployment.ContextNames$BindInfo.<init>(ContextNames.java:195)
> at org.jboss.as.naming.deployment.ContextNames$BindInfo.<init>(ContextNames.java:186)
> at org.jboss.as.naming.deployment.ContextNames.bindInfoFor(ContextNames.java:300)
> at org.teiid.jboss.VDBDeployer.addDataSourceListener(VDBDeployer.java:245)
> at org.teiid.jboss.VDBDeployer.dataSourceDependencies(VDBDeployer.java:267)
> at org.teiid.jboss.VDBDeployer.deploy(VDBDeployer.java:153)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:120) [jboss-as-server-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> ... 5 more
> Can Teiid preempt this and produce a clearer message that its because there's no JNDI specified?
--
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
12 years, 8 months
[JBoss JIRA] (TEIID-2597) Allow Salesforce COnnection timeouts to be easily adjusted
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2597?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2597:
---------------------------------------
No, you aren't missing anything you are just a little ahead. We have typically been doing a forward merge from 8.4.1 to master every week or before committing other large feature work. So this hasn't been forward merged yet, but will be shortly to be in 8.5 Beta1.
> Allow Salesforce COnnection timeouts to be easily adjusted
> ----------------------------------------------------------
>
> Key: TEIID-2597
> URL: https://issues.jboss.org/browse/TEIID-2597
> Project: Teiid
> Issue Type: Enhancement
> Affects Versions: 8.4
> Reporter: Graeme Gillies
> Assignee: Steven Hawkins
> Fix For: 8.4.1, 8.5
>
>
> Currently it is possible via an easy configuration option to set the http and other time-outs of ws connections. Can a similar option be made available to salesforce connections, so timeouts can be changed easily without a custom cxf setup
> Thanks,
> Graeme
--
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
12 years, 8 months
[JBoss JIRA] (TEIID-2597) Allow Salesforce COnnection timeouts to be easily adjusted
by Graeme Gillies (JIRA)
[ https://issues.jboss.org/browse/TEIID-2597?page=com.atlassian.jira.plugin... ]
Graeme Gillies commented on TEIID-2597:
---------------------------------------
Hi,
I see this has made it to the 8.4 branch, but can't see it on master (and thus the 8.5 branch) yet. Or am I missing something? I tired to build from head and use the settings but they don't work.
Regards,
Graeme
> Allow Salesforce COnnection timeouts to be easily adjusted
> ----------------------------------------------------------
>
> Key: TEIID-2597
> URL: https://issues.jboss.org/browse/TEIID-2597
> Project: Teiid
> Issue Type: Enhancement
> Affects Versions: 8.4
> Reporter: Graeme Gillies
> Assignee: Steven Hawkins
> Fix For: 8.4.1, 8.5
>
>
> Currently it is possible via an easy configuration option to set the http and other time-outs of ws connections. Can a similar option be made available to salesforce connections, so timeouts can be changed easily without a custom cxf setup
> Thanks,
> Graeme
--
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
12 years, 8 months
[JBoss JIRA] (TEIID-2601) Better handling for streamed lobs
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2601?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-2601.
-----------------------------------
Fix Version/s: 8.4.1
8.5
Resolution: Done
Added logic to the logmanger/serialization of lobs to prevent operations that would render a streaming lob invalid. Also improved the design of connectormanager.
> Better handling for streamed lobs
> ---------------------------------
>
> Key: TEIID-2601
> URL: https://issues.jboss.org/browse/TEIID-2601
> Project: Teiid
> Issue Type: Quality Risk
> Components: Query Engine
> Affects Versions: 8.2
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.4.1, 8.5
>
>
> When the ws translator returns a streamed result internal operations, such as adding to a tuple buffer may attempt to obtain the length, etc. that render the lob unusable and result in opaque errors, such as
> "TEIID30035 Wrong type of data found or no data found; expecting streamable object from the buffer manager"
> We should make streaming best effort (such as resorting to the copy on read logic), more fool-proof with internal operations, or at least improve the error 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
12 years, 8 months
[JBoss JIRA] (TEIID-2602) Add clearer message that a VDB cannot be deployed without a JNDI name specified in the .vdb
by Van Halbert (JIRA)
Van Halbert created TEIID-2602:
----------------------------------
Summary: Add clearer message that a VDB cannot be deployed without a JNDI name specified in the .vdb
Key: TEIID-2602
URL: https://issues.jboss.org/browse/TEIID-2602
Project: Teiid
Issue Type: Enhancement
Components: Server
Affects Versions: 8.4.1
Reporter: Van Halbert
Assignee: Steven Hawkins
Priority: Minor
Created a sample VDB in designer, for which the model is to use the loopback connector. Did not specify a JNDI reference, because it doesn't need one. However, the VDB can't be deployed from Designer because there's no connection info for this model. So I hand deployed, but the server doesn't like it that there's no JNDI specified (if I add the JNDI reference, it deploys fine). You get this error:
08:10:17,265 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.deployment.unit."Sample.vdb".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."Sample.vdb".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment "Sample.vdb"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:127) [jboss-as-server-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_13]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_13]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_13]
Caused by: java.lang.IllegalArgumentException: Empty name segment is not allowed for java
at org.jboss.msc.service.ServiceName.of(ServiceName.java:85) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
at org.jboss.msc.service.ServiceName.append(ServiceName.java:112) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
at org.jboss.as.naming.deployment.ContextNames.buildServiceName(ContextNames.java:183)
at org.jboss.as.naming.deployment.ContextNames$BindInfo.<init>(ContextNames.java:195)
at org.jboss.as.naming.deployment.ContextNames$BindInfo.<init>(ContextNames.java:186)
at org.jboss.as.naming.deployment.ContextNames.bindInfoFor(ContextNames.java:300)
at org.teiid.jboss.VDBDeployer.addDataSourceListener(VDBDeployer.java:245)
at org.teiid.jboss.VDBDeployer.dataSourceDependencies(VDBDeployer.java:267)
at org.teiid.jboss.VDBDeployer.deploy(VDBDeployer.java:153)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:120) [jboss-as-server-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
... 5 more
Can Teiid preempt this and produce a clearer message that its because there's no JNDI specified?
--
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
12 years, 8 months
[JBoss JIRA] (TEIID-2600) IllegalArgumentException when creating datasource from an imported Webservice source model
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2600?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-2600.
-----------------------------------
Fix Version/s: 8.4.1
8.5
Resolution: Done
added validation of the property values with a message indicating the name to make the exception message clearer.
> IllegalArgumentException when creating datasource from an imported Webservice source model
> ------------------------------------------------------------------------------------------
>
> Key: TEIID-2600
> URL: https://issues.jboss.org/browse/TEIID-2600
> Project: Teiid
> Issue Type: Quality Risk
> Components: AdminApi
> Affects Versions: 8.0
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Fix For: 8.4.1, 8.5
>
>
> After importing from a remote web service and creating the source and view models, tried to (right click on source model) create data source on teiid server (EAP 6.1 / Teiid 8.4.1) and had this issue:
> !ENTRY org.teiid.designer.dqp.ui 4 0 2013-07-25 16:59:24.847
> !MESSAGE Error creating data source for model CustomerRESTWebSvcSource.xmi
> !STACK 0
> java.lang.IllegalArgumentException: The argument value is not specified for value: ''
> at org.jboss.as.cli.operation.impl.DefaultOperationRequestBuilder.addProperty(DefaultOperationRequestBuilder.java:113)
> at org.teiid.adminapi.AdminFactory$AdminImpl.cliCall(AdminFactory.java:1397)
> at org.teiid.adminapi.AdminFactory$AdminImpl.addConfigProperty(AdminFactory.java:308)
> at org.teiid.adminapi.AdminFactory$AdminImpl.createConnectionFactory(AdminFactory.java:297)
> at org.teiid.adminapi.AdminFactory$AdminImpl.createDataSource(AdminFactory.java:412)
> at org.teiid84.runtime.ExecutionAdmin.getOrCreateDataSource(ExecutionAdmin.java:324)
> at org.teiid.designer.runtime.TeiidServer.getOrCreateDataSource(TeiidServer.java:551)
> at org.teiid.designer.runtime.ui.connection.CreateDataSourceAction.run(CreateDataSourceAction.java:156)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:499)
> 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$5.handleEvent(ActionContributionItem.java:411)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4166)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1489)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1474)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4012)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3651)
> 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)
--
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
12 years, 8 months
[JBoss JIRA] (TEIID-2597) Allow Salesforce COnnection timeouts to be easily adjusted
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2597?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-2597.
-----------------------------------
Resolution: Done
Update the httpdispatch logic to also use timeouts, added the connect timeout, and added timeout handling to salesforce.
> Allow Salesforce COnnection timeouts to be easily adjusted
> ----------------------------------------------------------
>
> Key: TEIID-2597
> URL: https://issues.jboss.org/browse/TEIID-2597
> Project: Teiid
> Issue Type: Enhancement
> Affects Versions: 8.4
> Reporter: Graeme Gillies
> Assignee: Steven Hawkins
> Fix For: 8.4.1, 8.5
>
>
> Currently it is possible via an easy configuration option to set the http and other time-outs of ws connections. Can a similar option be made available to salesforce connections, so timeouts can be changed easily without a custom cxf setup
> Thanks,
> Graeme
--
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
12 years, 8 months
[JBoss JIRA] (TEIID-2601) Better handling for streamed lobs
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2601:
-------------------------------------
Summary: Better handling for streamed lobs
Key: TEIID-2601
URL: https://issues.jboss.org/browse/TEIID-2601
Project: Teiid
Issue Type: Quality Risk
Components: Query Engine
Affects Versions: 8.2
Reporter: Steven Hawkins
Assignee: Steven Hawkins
When the ws translator returns a streamed result internal operations, such as adding to a tuple buffer may attempt to obtain the length, etc. that render the lob unusable and result in opaque errors, such as
"TEIID30035 Wrong type of data found or no data found; expecting streamable object from the buffer manager"
We should make streaming best effort (such as resorting to the copy on read logic), more fool-proof with internal operations, or at least improve the error 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
12 years, 8 months
[JBoss JIRA] (TEIID-2600) IllegalArgumentException when creating datasource from an imported Webservice source model
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2600?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-2600:
----------------------------------
Issue Type: Quality Risk (was: Bug)
Assignee: Steven Hawkins (was: Barry LaFond)
It would make sense based upon this to validate property values in the AdminImpl prior to the cliCall to produce a better error message.
> IllegalArgumentException when creating datasource from an imported Webservice source model
> ------------------------------------------------------------------------------------------
>
> Key: TEIID-2600
> URL: https://issues.jboss.org/browse/TEIID-2600
> Project: Teiid
> Issue Type: Quality Risk
> Components: AdminApi
> Affects Versions: 8.0
> Reporter: Van Halbert
> Assignee: Steven Hawkins
>
> After importing from a remote web service and creating the source and view models, tried to (right click on source model) create data source on teiid server (EAP 6.1 / Teiid 8.4.1) and had this issue:
> !ENTRY org.teiid.designer.dqp.ui 4 0 2013-07-25 16:59:24.847
> !MESSAGE Error creating data source for model CustomerRESTWebSvcSource.xmi
> !STACK 0
> java.lang.IllegalArgumentException: The argument value is not specified for value: ''
> at org.jboss.as.cli.operation.impl.DefaultOperationRequestBuilder.addProperty(DefaultOperationRequestBuilder.java:113)
> at org.teiid.adminapi.AdminFactory$AdminImpl.cliCall(AdminFactory.java:1397)
> at org.teiid.adminapi.AdminFactory$AdminImpl.addConfigProperty(AdminFactory.java:308)
> at org.teiid.adminapi.AdminFactory$AdminImpl.createConnectionFactory(AdminFactory.java:297)
> at org.teiid.adminapi.AdminFactory$AdminImpl.createDataSource(AdminFactory.java:412)
> at org.teiid84.runtime.ExecutionAdmin.getOrCreateDataSource(ExecutionAdmin.java:324)
> at org.teiid.designer.runtime.TeiidServer.getOrCreateDataSource(TeiidServer.java:551)
> at org.teiid.designer.runtime.ui.connection.CreateDataSourceAction.run(CreateDataSourceAction.java:156)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:499)
> 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$5.handleEvent(ActionContributionItem.java:411)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4166)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1489)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1474)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4012)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3651)
> 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)
--
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
12 years, 8 months