[JBoss JIRA] Created: (JBDS-1509) JBDS thread looping after call to OS - Seen in DTP connection profile-setting
1:45 p.m.
JBDS thread looping after call to OS - Seen in DTP connection profile-setting
-----------------------------------------------------------------------------
Key: JBDS-1509
URL: https://issues.jboss.org/browse/JBDS-1509
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: integration
Affects Versions: 4.0.0.CR1
Environment: JBDS 4.0 H65 CR1, Fedora 12, Java SE Runtime Environment (build
1.6.0_21-b06)
Reporter: Paul Nittel
While testing Teiid Designer, I found the software wold go into a loop when I was
interacting with the new connection profile process. The point at which the looping
started was sonewhat variable, but seemed repeatable within the new CP set of dialogs. To
simplify things, I started JBDS and went to the Database Development perspective (rather
than Teiid Designer) and stepped through the new CP process. While completing the database
connection information, the looping began. Here's part of the stack trace from running
it in debug:
Thread [main] (Suspended)
OS.Call(int, int, int, int) line: not available [native method]
Display.sleep() line: 4021
WizardDialog(Window).runEventLoop(Shell) line: 826
WizardDialog(Window).open() line: 801
NewProfileAction(AddProfileViewAction).run() line: 246
NewProfileAction(Action).runWithEvent(Event) line: 498
ActionContributionItem.handleWidgetSelection(Event, boolean) line: 584
ActionContributionItem.access$2(ActionContributionItem, Event, boolean) line: 501
ActionContributionItem$5.handleEvent(Event) line: 411
EventTable.sendEvent(Event) line: 84
MenuItem(Widget).sendEvent(Event) line: 1258
Display.runDeferredEvents() line: 3540
Display.readAndDispatch() line: 3161
Workbench.runEventLoop(Window$IExceptionHandler, Display) line: 2640
Workbench.runUI() line: 2604
Workbench.access$4(Workbench) line: 2438
Workbench$7.run() line: 671
Realm.runWithDefault(Realm, Runnable) line: 332
Workbench.createAndRunWorkbench(Display, WorkbenchAdvisor) line: 664
PlatformUI.createAndRunWorkbench(Display, WorkbenchAdvisor) line: 149
IDEApplication.start(IApplicationContext) line: 115
EclipseAppHandle.run(Object) line: 196
EclipseAppLauncher.runApplication(Object) line: 110
EclipseAppLauncher.start(Object) line: 79
EclipseStarter.run(Object) line: 369
EclipseStarter.run(String[], Runnable) line: 179
NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native
method]
NativeMethodAccessorImpl.invoke(Object, Object[]) line: 39
DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 25
Method.invoke(Object, Object...) line: 597
Main.invokeFramework(String[], URL[]) line: 619
Main.basicRun(String[]) line: 574
Main.run(String[]) line: 1407
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:22 p.m.
New subject: [JBoss JIRA] Commented: (JBDS-1509) JBDS thread looping after call to OS - Seen in DTP connection profile-setting
[
https://issues.jboss.org/browse/JBDS-1509?page=com.atlassian.jira.plugin....
]
Brian Fitzpatrick commented on JBDS-1509:
-----------------------------------------
I've tried this on RHEL 5 with the latest builds and can't reproduce. Anybody have
a Fedora 12 system to try debugging this on?
JBDS thread looping after call to OS - Seen in DTP connection
profile-setting
-----------------------------------------------------------------------------
Key: JBDS-1509
URL: https://issues.jboss.org/browse/JBDS-1509
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: integration
Affects Versions: 4.0.0.CR1
Environment: JBDS 4.0 H65 CR1, Fedora 12, Java SE Runtime Environment (build
1.6.0_21-b06)
Reporter: Paul Nittel
While testing Teiid Designer, I found the software wold go into a loop when I was
interacting with the new connection profile process. The point at which the looping
started was sonewhat variable, but seemed repeatable within the new CP set of dialogs. To
simplify things, I started JBDS and went to the Database Development perspective (rather
than Teiid Designer) and stepped through the new CP process. While completing the database
connection information, the looping began. Here's part of the stack trace from running
it in debug:
Thread [main] (Suspended)
OS.Call(int, int, int, int) line: not available [native method]
Display.sleep() line: 4021
WizardDialog(Window).runEventLoop(Shell) line: 826
WizardDialog(Window).open() line: 801
NewProfileAction(AddProfileViewAction).run() line: 246
NewProfileAction(Action).runWithEvent(Event) line: 498
ActionContributionItem.handleWidgetSelection(Event, boolean) line: 584
ActionContributionItem.access$2(ActionContributionItem, Event, boolean) line: 501
ActionContributionItem$5.handleEvent(Event) line: 411
EventTable.sendEvent(Event) line: 84
MenuItem(Widget).sendEvent(Event) line: 1258
Display.runDeferredEvents() line: 3540
Display.readAndDispatch() line: 3161
Workbench.runEventLoop(Window$IExceptionHandler, Display) line: 2640
Workbench.runUI() line: 2604
Workbench.access$4(Workbench) line: 2438
Workbench$7.run() line: 671
Realm.runWithDefault(Realm, Runnable) line: 332
Workbench.createAndRunWorkbench(Display, WorkbenchAdvisor) line: 664
PlatformUI.createAndRunWorkbench(Display, WorkbenchAdvisor) line: 149
IDEApplication.start(IApplicationContext) line: 115
EclipseAppHandle.run(Object) line: 196
EclipseAppLauncher.runApplication(Object) line: 110
EclipseAppLauncher.start(Object) line: 79
EclipseStarter.run(Object) line: 369
EclipseStarter.run(String[], Runnable) line: 179
NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native
method]
NativeMethodAccessorImpl.invoke(Object, Object[]) line: 39
DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 25
Method.invoke(Object, Object...) line: 597
Main.invokeFramework(String[], URL[]) line: 619
Main.basicRun(String[]) line: 574
Main.run(String[]) line: 1407
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:06 p.m.
New subject: [JBoss JIRA] Updated: (JBDS-1509) JBDS thread looping after call to OS - Seen in DTP connection profile-setting
[
https://issues.jboss.org/browse/JBDS-1509?page=com.atlassian.jira.plugin....
]
Brian Fitzpatrick updated JBDS-1509:
------------------------------------
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Assignee: Brian Fitzpatrick
Fix Version/s: 4.0.x
JBDS thread looping after call to OS - Seen in DTP connection
profile-setting
-----------------------------------------------------------------------------
Key: JBDS-1509
URL: https://issues.jboss.org/browse/JBDS-1509
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: integration
Affects Versions: 4.0.0.CR1
Environment: JBDS 4.0 H65 CR1, Fedora 12, Java SE Runtime Environment (build
1.6.0_21-b06)
Reporter: Paul Nittel
Assignee: Brian Fitzpatrick
Fix For: 4.0.x
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
While testing Teiid Designer, I found the software wold go into a loop when I was
interacting with the new connection profile process. The point at which the looping
started was sonewhat variable, but seemed repeatable within the new CP set of dialogs. To
simplify things, I started JBDS and went to the Database Development perspective (rather
than Teiid Designer) and stepped through the new CP process. While completing the database
connection information, the looping began. Here's part of the stack trace from running
it in debug:
Thread [main] (Suspended)
OS.Call(int, int, int, int) line: not available [native method]
Display.sleep() line: 4021
WizardDialog(Window).runEventLoop(Shell) line: 826
WizardDialog(Window).open() line: 801
NewProfileAction(AddProfileViewAction).run() line: 246
NewProfileAction(Action).runWithEvent(Event) line: 498
ActionContributionItem.handleWidgetSelection(Event, boolean) line: 584
ActionContributionItem.access$2(ActionContributionItem, Event, boolean) line: 501
ActionContributionItem$5.handleEvent(Event) line: 411
EventTable.sendEvent(Event) line: 84
MenuItem(Widget).sendEvent(Event) line: 1258
Display.runDeferredEvents() line: 3540
Display.readAndDispatch() line: 3161
Workbench.runEventLoop(Window$IExceptionHandler, Display) line: 2640
Workbench.runUI() line: 2604
Workbench.access$4(Workbench) line: 2438
Workbench$7.run() line: 671
Realm.runWithDefault(Realm, Runnable) line: 332
Workbench.createAndRunWorkbench(Display, WorkbenchAdvisor) line: 664
PlatformUI.createAndRunWorkbench(Display, WorkbenchAdvisor) line: 149
IDEApplication.start(IApplicationContext) line: 115
EclipseAppHandle.run(Object) line: 196
EclipseAppLauncher.runApplication(Object) line: 110
EclipseAppLauncher.start(Object) line: 79
EclipseStarter.run(Object) line: 369
EclipseStarter.run(String[], Runnable) line: 179
NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native
method]
NativeMethodAccessorImpl.invoke(Object, Object[]) line: 39
DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 25
Method.invoke(Object, Object...) line: 597
Main.invokeFramework(String[], URL[]) line: 619
Main.basicRun(String[]) line: 574
Main.run(String[]) line: 1407
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:06 p.m.
New subject: [JBoss JIRA] Commented: (JBDS-1509) JBDS thread looping after call to OS - Seen in DTP connection profile-setting
[
https://issues.jboss.org/browse/JBDS-1509?page=com.atlassian.jira.plugin....
]
Brian Fitzpatrick commented on JBDS-1509:
-----------------------------------------
Until I have a reliable way to reproduce it, I can't go far. It *should* work fine on
Fedora 12 all things considered. What all did you have installed tooling-wise? (i.e. what
Features are enabled? you can see by going to Help->About and getting a list of the
installed Features from the Installation Details button).
JBDS thread looping after call to OS - Seen in DTP connection
profile-setting
-----------------------------------------------------------------------------
Key: JBDS-1509
URL: https://issues.jboss.org/browse/JBDS-1509
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: integration
Affects Versions: 4.0.0.CR1
Environment: JBDS 4.0 H65 CR1, Fedora 12, Java SE Runtime Environment (build
1.6.0_21-b06)
Reporter: Paul Nittel
Assignee: Brian Fitzpatrick
Fix For: 4.0.x
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
While testing Teiid Designer, I found the software wold go into a loop when I was
interacting with the new connection profile process. The point at which the looping
started was sonewhat variable, but seemed repeatable within the new CP set of dialogs. To
simplify things, I started JBDS and went to the Database Development perspective (rather
than Teiid Designer) and stepped through the new CP process. While completing the database
connection information, the looping began. Here's part of the stack trace from running
it in debug:
Thread [main] (Suspended)
OS.Call(int, int, int, int) line: not available [native method]
Display.sleep() line: 4021
WizardDialog(Window).runEventLoop(Shell) line: 826
WizardDialog(Window).open() line: 801
NewProfileAction(AddProfileViewAction).run() line: 246
NewProfileAction(Action).runWithEvent(Event) line: 498
ActionContributionItem.handleWidgetSelection(Event, boolean) line: 584
ActionContributionItem.access$2(ActionContributionItem, Event, boolean) line: 501
ActionContributionItem$5.handleEvent(Event) line: 411
EventTable.sendEvent(Event) line: 84
MenuItem(Widget).sendEvent(Event) line: 1258
Display.runDeferredEvents() line: 3540
Display.readAndDispatch() line: 3161
Workbench.runEventLoop(Window$IExceptionHandler, Display) line: 2640
Workbench.runUI() line: 2604
Workbench.access$4(Workbench) line: 2438
Workbench$7.run() line: 671
Realm.runWithDefault(Realm, Runnable) line: 332
Workbench.createAndRunWorkbench(Display, WorkbenchAdvisor) line: 664
PlatformUI.createAndRunWorkbench(Display, WorkbenchAdvisor) line: 149
IDEApplication.start(IApplicationContext) line: 115
EclipseAppHandle.run(Object) line: 196
EclipseAppLauncher.runApplication(Object) line: 110
EclipseAppLauncher.start(Object) line: 79
EclipseStarter.run(Object) line: 369
EclipseStarter.run(String[], Runnable) line: 179
NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native
method]
NativeMethodAccessorImpl.invoke(Object, Object[]) line: 39
DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 25
Method.invoke(Object, Object...) line: 597
Main.invokeFramework(String[], URL[]) line: 619
Main.basicRun(String[]) line: 574
Main.run(String[]) line: 1407
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:49 p.m.
New subject: [JBoss JIRA] (JBDS-1509) JBDS thread looping after call to OS - Seen in DTP connection profile-setting
[
https://issues.jboss.org/browse/JBDS-1509?page=com.atlassian.jira.plugin....
]
Brian Fitzpatrick updated JBDS-1509:
------------------------------------
Fix Version/s: LATER
(was: 4.x)
JBDS thread looping after call to OS - Seen in DTP connection
profile-setting
-----------------------------------------------------------------------------
Key: JBDS-1509
URL: https://issues.jboss.org/browse/JBDS-1509
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: integration
Affects Versions: 4.0.0.CR1
Environment: JBDS 4.0 H65 CR1, Fedora 12, Java SE Runtime Environment (build
1.6.0_21-b06)
Reporter: Paul Nittel
Assignee: Brian Fitzpatrick
Fix For: LATER
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
While testing Teiid Designer, I found the software wold go into a loop when I was
interacting with the new connection profile process. The point at which the looping
started was sonewhat variable, but seemed repeatable within the new CP set of dialogs. To
simplify things, I started JBDS and went to the Database Development perspective (rather
than Teiid Designer) and stepped through the new CP process. While completing the database
connection information, the looping began. Here's part of the stack trace from running
it in debug:
Thread [main] (Suspended)
OS.Call(int, int, int, int) line: not available [native method]
Display.sleep() line: 4021
WizardDialog(Window).runEventLoop(Shell) line: 826
WizardDialog(Window).open() line: 801
NewProfileAction(AddProfileViewAction).run() line: 246
NewProfileAction(Action).runWithEvent(Event) line: 498
ActionContributionItem.handleWidgetSelection(Event, boolean) line: 584
ActionContributionItem.access$2(ActionContributionItem, Event, boolean) line: 501
ActionContributionItem$5.handleEvent(Event) line: 411
EventTable.sendEvent(Event) line: 84
MenuItem(Widget).sendEvent(Event) line: 1258
Display.runDeferredEvents() line: 3540
Display.readAndDispatch() line: 3161
Workbench.runEventLoop(Window$IExceptionHandler, Display) line: 2640
Workbench.runUI() line: 2604
Workbench.access$4(Workbench) line: 2438
Workbench$7.run() line: 671
Realm.runWithDefault(Realm, Runnable) line: 332
Workbench.createAndRunWorkbench(Display, WorkbenchAdvisor) line: 664
PlatformUI.createAndRunWorkbench(Display, WorkbenchAdvisor) line: 149
IDEApplication.start(IApplicationContext) line: 115
EclipseAppHandle.run(Object) line: 196
EclipseAppLauncher.runApplication(Object) line: 110
EclipseAppLauncher.start(Object) line: 79
EclipseStarter.run(Object) line: 369
EclipseStarter.run(String[], Runnable) line: 179
NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native
method]
NativeMethodAccessorImpl.invoke(Object, Object[]) line: 39
DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 25
Method.invoke(Object, Object...) line: 597
Main.invokeFramework(String[], URL[]) line: 619
Main.basicRun(String[]) line: 574
Main.run(String[]) line: 1407
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5232
days inactive
5555
days old
jbosstools-issues@lists.jboss.org
4 comments
3 participants
participants (3)
-
Brian Fitzpatrick (JIRA) -
Brian Fitzpatrick (Updated) (JIRA)
-
Paul Nittel (JIRA)