[JBoss JIRA] (JBIDE-24981) Server adapter: fails to start if app has no dc but only a rc
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24981?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-24981:
-------------------------------------
Attachment: starte-even-though-failed-starting.png
> Server adapter: fails to start if app has no dc but only a rc
> -------------------------------------------------------------
>
> Key: JBIDE-24981
> URL: https://issues.jboss.org/browse/JBIDE-24981
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.5.1.AM1
> Reporter: Andre Dietisheim
> Labels: openhift_v3, server_adapter
> Fix For: 4.5.x
>
> Attachments: eap-without-service-nor-deploymentconfig.json, image-2017-09-04-22-15-46-383.png, image-2017-09-04-22-17-26-655.png, starte-even-though-failed-starting.png
>
>
> # ASSERT: make sure that you have an app that has NO deployment config, just a replication controller
> (EXEC: if you dont, create it via the attached custom template [^eap-without-service-nor-deploymentconfig.json])
> # EXEC: in explorer: once your app is created, create a server adapter for it, binding the imported source to the replication controller that's available
> # ASSERT: the server adapter is starting up
> !image-2017-09-04-22-15-46-383.png!
> Result:
> The server adapter keeps starting up without reaching "[Started]", waiting at 7%. Finally -
> after a few minutes, it fails with the following error:
> !image-2017-09-04-22-17-26-655.png!
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24981) Server adapter: fails to start if app has no dc but only a rc
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24981?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-24981:
-------------------------------------
Description:
# ASSERT: make sure that you have an app that has NO deployment config, just a replication controller
(EXEC: if you dont, create it via the attached custom template [^eap-without-service-nor-deploymentconfig.json])
# EXEC: in explorer: once your app is created, create a server adapter for it, binding the imported source to the replication controller that's available
# ASSERT: the server adapter is starting up
!image-2017-09-04-22-15-46-383.png!
Result:
The server adapter keeps starting up without reaching "[Started]", waiting at 7%. Finally -
after a few minutes, it fails with the following error:
!image-2017-09-04-22-17-26-655.png!
Furthermore, once you close the error dialog the server is in state "[Started]" even though it errored while starting up
!starte-even-though-failed-starting.png!
was:
# ASSERT: make sure that you have an app that has NO deployment config, just a replication controller
(EXEC: if you dont, create it via the attached custom template [^eap-without-service-nor-deploymentconfig.json])
# EXEC: in explorer: once your app is created, create a server adapter for it, binding the imported source to the replication controller that's available
# ASSERT: the server adapter is starting up
!image-2017-09-04-22-15-46-383.png!
Result:
The server adapter keeps starting up without reaching "[Started]", waiting at 7%. Finally -
after a few minutes, it fails with the following error:
!image-2017-09-04-22-17-26-655.png!
> Server adapter: fails to start if app has no dc but only a rc
> -------------------------------------------------------------
>
> Key: JBIDE-24981
> URL: https://issues.jboss.org/browse/JBIDE-24981
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.5.1.AM1
> Reporter: Andre Dietisheim
> Labels: openhift_v3, server_adapter
> Fix For: 4.5.x
>
> Attachments: eap-without-service-nor-deploymentconfig.json, image-2017-09-04-22-15-46-383.png, image-2017-09-04-22-17-26-655.png, starte-even-though-failed-starting.png
>
>
> # ASSERT: make sure that you have an app that has NO deployment config, just a replication controller
> (EXEC: if you dont, create it via the attached custom template [^eap-without-service-nor-deploymentconfig.json])
> # EXEC: in explorer: once your app is created, create a server adapter for it, binding the imported source to the replication controller that's available
> # ASSERT: the server adapter is starting up
> !image-2017-09-04-22-15-46-383.png!
> Result:
> The server adapter keeps starting up without reaching "[Started]", waiting at 7%. Finally -
> after a few minutes, it fails with the following error:
> !image-2017-09-04-22-17-26-655.png!
>
> Furthermore, once you close the error dialog the server is in state "[Started]" even though it errored while starting up
> !starte-even-though-failed-starting.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24981) Server adapter: fails to start if app has no dc but only a rc
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24981?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-24981:
-------------------------------------
Labels: openhift_v3 server_adapter (was: )
> Server adapter: fails to start if app has no dc but only a rc
> -------------------------------------------------------------
>
> Key: JBIDE-24981
> URL: https://issues.jboss.org/browse/JBIDE-24981
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.5.1.AM1
> Reporter: Andre Dietisheim
> Labels: openhift_v3, server_adapter
> Fix For: 4.5.x
>
> Attachments: eap-without-service-nor-deploymentconfig.json, image-2017-09-04-22-15-46-383.png, image-2017-09-04-22-17-26-655.png
>
>
> # ASSERT: make sure that you have an app that has NO deployment config, just a replication controller
> (EXEC: if you dont, create it via the attached custom [^template eap-without-service-nor-deploymentconfig.json])
> # EXEC: in explorer: once your app is created, create a server adapter for it, binding the imported source to the replication controller that's available
> # ASSERT: the server adapter is starting up
> !image-2017-09-04-22-15-46-383.png!
> Result:
> The server adapter keeps starting up without reaching "[Started]", waiting at 7%. Finally -
> after a few minutes, it fails with the following error:
> !image-2017-09-04-22-17-26-655.png!
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24981) Server adapter: fails to start if app has no dc but only a rc
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24981?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-24981:
-------------------------------------
Attachment: eap-without-service-nor-deploymentconfig.json
> Server adapter: fails to start if app has no dc but only a rc
> -------------------------------------------------------------
>
> Key: JBIDE-24981
> URL: https://issues.jboss.org/browse/JBIDE-24981
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.5.1.AM1
> Reporter: Andre Dietisheim
> Labels: openhift_v3, server_adapter
> Fix For: 4.5.x
>
> Attachments: eap-without-service-nor-deploymentconfig.json, image-2017-09-04-22-15-46-383.png, image-2017-09-04-22-17-26-655.png
>
>
> # ASSERT: make sure that you have an app that has NO deployment config, just a replication controller
> (EXEC: if you dont, create it via the attached custom [^template eap-without-service-nor-deploymentconfig.json])
> # EXEC: in explorer: once your app is created, create a server adapter for it, binding the imported source to the replication controller that's available
> # ASSERT: the server adapter is starting up
> !image-2017-09-04-22-15-46-383.png!
> Result:
> The server adapter keeps starting up without reaching "[Started]", waiting at 7%. Finally -
> after a few minutes, it fails with the following error:
> !image-2017-09-04-22-17-26-655.png!
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24981) Server adapter: fails to start if app has no dc but only a rc
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24981?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-24981:
-------------------------------------
Description:
# ASSERT: make sure that you have an app that has NO deployment config, just a replication controller
(EXEC: if you dont, create it via the attached custom template [^eap-without-service-nor-deploymentconfig.json])
# EXEC: in explorer: once your app is created, create a server adapter for it, binding the imported source to the replication controller that's available
# ASSERT: the server adapter is starting up
!image-2017-09-04-22-15-46-383.png!
Result:
The server adapter keeps starting up without reaching "[Started]", waiting at 7%. Finally -
after a few minutes, it fails with the following error:
!image-2017-09-04-22-17-26-655.png!
was:
# ASSERT: make sure that you have an app that has NO deployment config, just a replication controller
(EXEC: if you dont, create it via the attached custom [^template eap-without-service-nor-deploymentconfig.json])
# EXEC: in explorer: once your app is created, create a server adapter for it, binding the imported source to the replication controller that's available
# ASSERT: the server adapter is starting up
!image-2017-09-04-22-15-46-383.png!
Result:
The server adapter keeps starting up without reaching "[Started]", waiting at 7%. Finally -
after a few minutes, it fails with the following error:
!image-2017-09-04-22-17-26-655.png!
> Server adapter: fails to start if app has no dc but only a rc
> -------------------------------------------------------------
>
> Key: JBIDE-24981
> URL: https://issues.jboss.org/browse/JBIDE-24981
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.5.1.AM1
> Reporter: Andre Dietisheim
> Labels: openhift_v3, server_adapter
> Fix For: 4.5.x
>
> Attachments: eap-without-service-nor-deploymentconfig.json, image-2017-09-04-22-15-46-383.png, image-2017-09-04-22-17-26-655.png
>
>
> # ASSERT: make sure that you have an app that has NO deployment config, just a replication controller
> (EXEC: if you dont, create it via the attached custom template [^eap-without-service-nor-deploymentconfig.json])
> # EXEC: in explorer: once your app is created, create a server adapter for it, binding the imported source to the replication controller that's available
> # ASSERT: the server adapter is starting up
> !image-2017-09-04-22-15-46-383.png!
> Result:
> The server adapter keeps starting up without reaching "[Started]", waiting at 7%. Finally -
> after a few minutes, it fails with the following error:
> !image-2017-09-04-22-17-26-655.png!
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24981) Server adapter: fails to start if app has no dc but only a rc
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-24981:
----------------------------------------
Summary: Server adapter: fails to start if app has no dc but only a rc
Key: JBIDE-24981
URL: https://issues.jboss.org/browse/JBIDE-24981
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 4.5.1.AM1
Reporter: Andre Dietisheim
Fix For: 4.5.x
Attachments: image-2017-09-04-22-15-46-383.png, image-2017-09-04-22-17-26-655.png
# ASSERT: make sure that you have an app that has NO deployment config, just a replication controller
(EXEC: if you dont, create it via the attached custom [^template eap-without-service-nor-deploymentconfig.json])
# EXEC: in explorer: once your app is created, create a server adapter for it, binding the imported source to the replication controller that's available
# ASSERT: the server adapter is starting up
!image-2017-09-04-22-15-46-383.png!
Result:
The server adapter keeps starting up without reaching "[Started]", waiting at 7%. Finally -
after a few minutes, it fails with the following error:
!image-2017-09-04-22-17-26-655.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24980) Explorer: add Scale Up/Down/To to context menu to replication controller
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24980?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-24980:
-------------------------------------
Attachment: eap-without-service-nor-deploymentconfig.json
> Explorer: add Scale Up/Down/To to context menu to replication controller
> ------------------------------------------------------------------------
>
> Key: JBIDE-24980
> URL: https://issues.jboss.org/browse/JBIDE-24980
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.5.1.AM1
> Reporter: Andre Dietisheim
> Labels: explorer, openshift_v3, scale
> Fix For: 4.5.x
>
> Attachments: eap-without-service-nor-deploymentconfig.json, scale-replication-controller.png, scale-service.png
>
>
> # ASSERT: make sure that you have an app that has NO deployment config, just a replication controller
> (EXEC: if you dont, create it via the attached custom template eap-without-service-nor-deploymentconfig.json)
> # ASSERT: in explorer: once your app is created, select your replication controller and open up the context menu, look for a "*Scale*" Item.
> Result:
> There's no such item. There's only "Scale" available if you select the pod for the replication controller. Furthermore it also exists in the properties view for "*Deployments*".
> !scale-replication-controller.png!
> While it exists for services
> !scale-service.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24980) Explorer: add Scale Up/Down/To to context menu to replication controller
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24980?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-24980:
-------------------------------------
Attachment: (was: eap-without-service-nor-deploymentconfig.json)
> Explorer: add Scale Up/Down/To to context menu to replication controller
> ------------------------------------------------------------------------
>
> Key: JBIDE-24980
> URL: https://issues.jboss.org/browse/JBIDE-24980
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.5.1.AM1
> Reporter: Andre Dietisheim
> Labels: explorer, openshift_v3, scale
> Fix For: 4.5.x
>
> Attachments: eap-without-service-nor-deploymentconfig.json, scale-replication-controller.png, scale-service.png
>
>
> # ASSERT: make sure that you have an app that has NO deployment config, just a replication controller
> (EXEC: if you dont, create it via the attached custom template eap-without-service-nor-deploymentconfig.json)
> # ASSERT: in explorer: once your app is created, select your replication controller and open up the context menu, look for a "*Scale*" Item.
> Result:
> There's no such item. There's only "Scale" available if you select the pod for the replication controller. Furthermore it also exists in the properties view for "*Deployments*".
> !scale-replication-controller.png!
> While it exists for services
> !scale-service.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24980) Explorer: add Scale Up/Down/To to context menu to replication controller
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24980?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-24980:
-------------------------------------
Description:
# ASSERT: make sure that you have an app that has NO deployment config, just a replication controller
(EXEC: if you dont, create it via the attached custom template [^eap-without-service-nor-deploymentconfig.json])
# ASSERT: in explorer: once your app is created, select your replication controller and open up the context menu, look for a "*Scale*" Item.
Result:
There's no such item. There's only "Scale" available if you select the pod for the replication controller. Furthermore it also exists in the properties view for "*Deployments*".
!scale-replication-controller.png!
While it exists for services
!scale-service.png!
was:
# ASSERT: make sure that you have an app that has NO deployment config, just a replication controller
(EXEC: if you dont, create it via the attached custom template eap-without-service-nor-deploymentconfig.json)
# ASSERT: in explorer: once your app is created, select your replication controller and open up the context menu, look for a "*Scale*" Item.
Result:
There's no such item. There's only "Scale" available if you select the pod for the replication controller. Furthermore it also exists in the properties view for "*Deployments*".
!scale-replication-controller.png!
While it exists for services
!scale-service.png!
> Explorer: add Scale Up/Down/To to context menu to replication controller
> ------------------------------------------------------------------------
>
> Key: JBIDE-24980
> URL: https://issues.jboss.org/browse/JBIDE-24980
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.5.1.AM1
> Reporter: Andre Dietisheim
> Labels: explorer, openshift_v3, scale
> Fix For: 4.5.x
>
> Attachments: eap-without-service-nor-deploymentconfig.json, scale-replication-controller.png, scale-service.png
>
>
> # ASSERT: make sure that you have an app that has NO deployment config, just a replication controller
> (EXEC: if you dont, create it via the attached custom template [^eap-without-service-nor-deploymentconfig.json])
> # ASSERT: in explorer: once your app is created, select your replication controller and open up the context menu, look for a "*Scale*" Item.
> Result:
> There's no such item. There's only "Scale" available if you select the pod for the replication controller. Furthermore it also exists in the properties view for "*Deployments*".
> !scale-replication-controller.png!
> While it exists for services
> !scale-service.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24979) Scale up/down/to: NPE if you have only a rc, no dc for your app
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24979?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-24979:
-------------------------------------
Labels: openshift_v3 scale (was: explorer openshift_v3 properties scale)
> Scale up/down/to: NPE if you have only a rc, no dc for your app
> ---------------------------------------------------------------
>
> Key: JBIDE-24979
> URL: https://issues.jboss.org/browse/JBIDE-24979
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.x
> Reporter: Andre Dietisheim
> Labels: openshift_v3, scale
> Fix For: 4.5.x
>
> Attachments: eap-without-service-nor-deploymentconfig.json, image-2017-09-04-21-24-57-027.png
>
>
> # ASSERT: make sure that you have an app that has *NO* deployment config, just a replication controller
> (EXEC: if you dont, create it via the attached custom template [^eap-without-service-nor-deploymentconfig.json])
> # EXEC: in OpenShift explorer: select the pod for your rc, pick "Scale > Up" or "Scale > Down" or "Scale > To"
> !image-2017-09-04-21-24-57-027.png!
> The very same is true if you do the same via the properties view "Deployments". There's a "Scale" item for the deployment context menu, but it does nothing.
> Result:
> Nothing happens and in the log you discover the following:
> {code}
> org.eclipse.e4.core.di.InjectionException: java.lang.NullPointerException
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:65)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:305)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:239)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:494)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:487)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:431)
> at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.handleWidgetSelection(AbstractContributionItem.java:446)
> at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.lambda$2(AbstractContributionItem.java:472)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4257)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1502)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1525)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1510)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1314)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4081)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3698)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1155)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1044)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153)
> at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:680)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:594)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:151)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:653)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1499)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1472)
> Caused by: java.lang.NullPointerException
> at org.jboss.tools.openshift.internal.ui.handler.ScaleDeploymentHandler.getDeploymentConfig(ScaleDeploymentHandler.java:143)
> at org.jboss.tools.openshift.internal.ui.handler.ScaleDeploymentHandler.getDeploymentConfig(ScaleDeploymentHandler.java:136)
> at org.jboss.tools.openshift.internal.ui.handler.ScaleDeploymentHandler.getDeploymentConfig(ScaleDeploymentHandler.java:106)
> at org.jboss.tools.openshift.internal.ui.handler.ScaleDeploymentHandler.execute(ScaleDeploymentHandler.java:78)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:291)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:92)
> at sun.reflect.GeneratedMethodAccessor104.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months