Always sometimes empty screen with DS 1.6 SP01

[former_member210496]

Hi,

If I remember right in Design Studio 1.6 SP0 was a known bug. The bug was that if you using Design Studio in combination with BIP Plugin it could happen that the application screen is empty after opening an new or existing application.

Meanwhile I installed Design Studio 1.6 SP01 (client and BIP Plugin on server side) released at 29^th of March. If I open now an existing application I got time by time a blank application screen and the error messages "Internal Webserver is not able to start ..." and "Message: org.osgi.service.cm.ConfigurationException: org.eclipse.equinox.http.jetty.JettyConfigurator.aad : Address already in use: ... ". As I said this error occurs not every time only time by time. Any ideas or advices regarding this problem?

Thank you and best regards,

Eric

[TammyPowlas]

Have you tried to restart your system, as described in this SAP Note? https://launchpad.support.sap.com/#/notes/2230238/E

[former_member210496]

Hi Tammy,

thank you for your fast repl. To avoid misunderstandings. My problem is on client side. I do the following steps:

1. Start the Design Studio
2. Logon to BOE platform
3. Open an existing application
4. Time by time I got a blank screen in the application window

For example. Yesterday I tried to open the application and I got a blank screen and the error messages in the error log. This morning after a reboot of the Laptop I was able to open the application without any error. So I have this situation from time to time. 

Here are event details out of the error log:

First error:

1. eclipse.buildId=@qualifier@
2. java.version=1.7.0_76
3. java.vendor=SAP AG

BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=de_DE

Framework arguments:  BusinessObjects Design Studio

Command-line arguments:  -os win32 -ws win32 -arch x86_64 BusinessObjects Design Studio

1. com.sap.ip.bi.zen.webserver

Error

Tue Apr 19 16:59:52 CEST 2016

Interner Webserver konnte nicht gestartet werden*

(*Translation into english „Internal Webserver couldn’t be started“)

Second error:

1. eclipse.buildId=@qualifier@
2. java.version=1.7.0_76
3. java.vendor=SAP AG

BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=de_DE

Framework arguments: BusinessObjects Design Studio

Command-line arguments:  -os win32 -ws win32 -arch x86_64 BusinessObjects Design Studio

1. com.sap.ip.bi.zen.webserver

Error

Tue Apr 19 16:59:52 CEST 2016

Message: org.osgi.service.cm.ConfigurationException: org.eclipse.equinox.http.jetty.JettyConfigurator.aad : Address already in use: bind

Stack trace: com.sap.ip.bi.zen.webserver.WebServerException: org.osgi.service.cm.ConfigurationException: org.eclipse.equinox.http.jetty.JettyConfigurator.aad : Address already in use: bind

                at com.sap.ip.bi.zen.webserver.jetty.JettyWebServer.startServer(JettyWebServer.java:93)

                at com.sap.ip.bi.zen.webserver.designer.DesignTimeWebServer.startServer(DesignTimeWebServer.java:95)

                at com.sap.ip.bi.zen.webserver.WebServerPlugin.getInitializedDesignTimeWebServer(WebServerPlugin.java:83)

                at com.sap.ip.bi.zen.ui.internal.editor.EmbeddedWebBrowser.getUrl(EmbeddedWebBrowser.java:202)

                at com.sap.ip.bi.zen.ui.internal.editor.EmbeddedWebBrowser.navigateToHomeUrl(EmbeddedWebBrowser.java:357)

                at com.sap.ip.bi.zen.ui.internal.editor.FullLoadUpdateTask.execute(FullLoadUpdateTask.java:11)

                at com.sap.ip.bi.zen.ui.internal.editor.BrowserUpdater$2.run(BrowserUpdater.java:111)

                at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)

                at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)

                at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4155)

                at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3772)

                at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)

                at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)

                at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)

                at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)

                at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)

                at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)

                at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)

                at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)

                at com.sap.ip.bi.zen.ui.internal.application.ZenApplication.start(ZenApplication.java:36)

                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:380)

                at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)

                at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

                at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

                at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

                at java.lang.reflect.Method.invoke(Method.java:606)

                at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)

                at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)

                at org.eclipse.equinox.launcher.Main.run(Main.java:1515)

                at org.eclipse.equinox.launcher.Main.main(Main.java:1488)

Caused by: org.osgi.service.cm.ConfigurationException: org.eclipse.equinox.http.jetty.JettyConfigurator.aad : Address already in use: bind

                at org.eclipse.equinox.http.jetty.internal.HttpServerManager.updated(HttpServerManager.java:91)

                at org.eclipse.equinox.http.jetty.internal.Activator.startServer(Activator.java:225)

                at org.eclipse.equinox.http.jetty.JettyConfigurator.startServer(JettyConfigurator.java:45)

                at com.sap.ip.bi.zen.webserver.jetty.JettyWebServer.startServer(JettyWebServer.java:86)

                ... 32 more

Caused by: java.net.BindException: Address already in use: bind

                at sun.nio.ch.Net.bind0(Native Method)

                at sun.nio.ch.Net.bind(Net.java:444)

                at sun.nio.ch.Net.bind(Net.java:436)

                at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:214)

                at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)

                at org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:321)

                at org.eclipse.equinox.http.jetty.internal.HttpServerManager.updated(HttpServerManager.java:89)

                ... 35 more

1. com.sap.ip.bi.zen.webserver.WebServerException: org.osgi.service.cm.ConfigurationException: org.eclipse.equinox.http.jetty.JettyConfigurator.aad : Address already in use: bind

                at com.sap.ip.bi.zen.webserver.jetty.JettyWebServer.startServer(JettyWebServer.java:93)

                at com.sap.ip.bi.zen.webserver.designer.DesignTimeWebServer.startServer(DesignTimeWebServer.java:95)

                at com.sap.ip.bi.zen.webserver.WebServerPlugin.getInitializedDesignTimeWebServer(WebServerPlugin.java:83)

                at com.sap.ip.bi.zen.ui.internal.editor.EmbeddedWebBrowser.getUrl(EmbeddedWebBrowser.java:202)

                at com.sap.ip.bi.zen.ui.internal.editor.EmbeddedWebBrowser.navigateToHomeUrl(EmbeddedWebBrowser.java:357)

                at com.sap.ip.bi.zen.ui.internal.editor.FullLoadUpdateTask.execute(FullLoadUpdateTask.java:11)

                at com.sap.ip.bi.zen.ui.internal.editor.BrowserUpdater$2.run(BrowserUpdater.java:111)

                at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)

                at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)

                at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4155)

                at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3772)

                at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)

                at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)

                at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)

                at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)

                at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)

                at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)

                at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)

                at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)

                at com.sap.ip.bi.zen.ui.internal.application.ZenApplication.start(ZenApplication.java:36)

                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:380)

                at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)

                at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

                at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

                at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

                at java.lang.reflect.Method.invoke(Method.java:606)

                at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)

                at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)

                at org.eclipse.equinox.launcher.Main.run(Main.java:1515)

                at org.eclipse.equinox.launcher.Main.main(Main.java:1488)

Caused by: org.osgi.service.cm.ConfigurationException: org.eclipse.equinox.http.jetty.JettyConfigurator.aad : Address already in use: bind

                at org.eclipse.equinox.http.jetty.internal.HttpServerManager.updated(HttpServerManager.java:91)

                at org.eclipse.equinox.http.jetty.internal.Activator.startServer(Activator.java:225)

                at org.eclipse.equinox.http.jetty.JettyConfigurator.startServer(JettyConfigurator.java:45)

                at com.sap.ip.bi.zen.webserver.jetty.JettyWebServer.startServer(JettyWebServer.java:86)

                ... 32 more

Caused by: java.net.BindException: Address already in use: bind

                at sun.nio.ch.Net.bind0(Native Method)

                at sun.nio.ch.Net.bind(Net.java:444)

                at sun.nio.ch.Net.bind(Net.java:436)

                at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:214)

                at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)

                at org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:321)

                at org.eclipse.equinox.http.jetty.internal.HttpServerManager.updated(HttpServerManager.java:89)

                ... 35 more

Best regards,

Eric

[TammyPowlas]

Eric:

Does it work locally, or show a blank page when you connect locally?

Also have you see this page for Design Studio client troubleshooting? Design Studio - Support Page For Client - Business Intelligence (BusinessObjects) - SCN Wiki

[former_member210496]

Dear Tammy,

thank you for response. Especially your link to the „Design Studio client troubleshooting” is very interesting. Menwhile I think my problem is related to RAM consumption. I have “only” 4 GB RAM and I think I have to increase my RAM to 8 GB.

I tried to edit the SapDesignStudio.ini parameters

From original settings:

-Dsun.net.client.defaultReadTimeout=60000

-Dsun.net.client.defaultConnectTimeout=60000-Xmx4g

-Xms512m

-XX:PermSize=64m

-XX:MaxPermSize=1g

To my settings:

-Dsun.net.client.defaultReadTimeout=240000

-Dsun.net.client.defaultConnectTimeout=240000

-Xmx512m

-Xms32m

-XX:PermSize=32m

-XX:MaxPermSize=128m

With my setting it happens not as often as before that the application windows is blank. I have to do some additional tests and add additional RAM into my Laptop and then I will come back with the results.

Thank you and best regards,

Eric

[TammyPowlas]

Hi Eric - good catch!

Yes, the amount of RAM is important...good luck

[former_member210496]

Dear all,

it takes a while till I got a new laptop so sorry for my late response. Meanwhile I am sure that the problem is due my limited system ressources. My old Laptop had an 4 GB RAM and a Core i5, the new on has 8 GB RAM also on a Core i5. On my new laptop SAP Design Studio works without any issues till now.

Best regards,

Eric