Forum Discussion

Huib's avatar
Huib
New Contributor
5 years ago
Solved

ReadyAPI 2.8.0 doesn't start it's get an null in the splash window: ERROR [SwingInvokeInterceptor]

Hello all, 

 

I'm new here but I work 6 years with SoapUI and ReadyAPI :). It worked untill we decided to upgrade ReadyAPI 2.4.0. to 2.8.0.

The versions 2.7.0 and 2.8.0 gives me the same error. I could not find it here.  So that's why I started a new topic. 

When we start ReadyAPI 2.8.0 it looks fine untill we see a Null in the splash window see picutere: 

 

And I found the following in log file: 

ERROR [SwingInvokeInterceptor] null

java.lang.NullPointerException: null
at com.eviware.soapui.support.UISupport.getModuleLogo(UISupport.java:2910) ~[ready-api-soapui-2.8.0.jar:?]

 

See the whole file:

.
2019-08-12 14:40:57,569 INFO  [DefaultSoapUICore] Adding listeners from [C:\Program Files\ReadyAPI-2.8.0\bin\listeners\demo-listeners.xml]
2019-08-12 14:40:59,356 INFO  [DefaultSoapUICore] Adding actions from [C:\Program Files\ReadyAPI-2.8.0\bin\actions\demo-actions.xml]
2019-08-12 14:41:00,307 INFO  [Reflections] Reflections took 564 ms to scan 42 urls, producing 2440 keys and 9712 values 
2019-08-12 14:41:00,399 INFO  [Reflections] Reflections took 17 ms to scan 2 urls, producing 82 keys and 179 values 
2019-08-12 14:41:00,421 INFO  [Reflections] Reflections took 19 ms to scan 1 urls, producing 44 keys and 339 values 
2019-08-12 14:41:00,436 INFO  [PluginManager] Adding plugin from [C:\Users\atfprl\.soapui\plugins\ready-mqtt-plugin-dist.jar]
2019-08-12 14:41:00,440 INFO  [PluginManager] Adding plugin from [C:\Users\atfprl\.soapui\plugins\ready-jira-plugin-1.3.jar]
2019-08-12 14:41:03,334 INFO  [jetty] Logging initialized @19382ms to com.eviware.soapui.support.log.JettyLogger
2019-08-12 14:41:04,022 INFO  [ReadyApiInitializer] Initializing modules
2019-08-12 14:41:05,415 INFO  [Reflections] Reflections took 15677 ms to scan 365 urls, producing 22502 keys and 118580 values 
2019-08-12 14:41:05,550 INFO  [Reflections] Reflections collected metadata from input stream using serializer org.reflections.serializers.XmlSerializer
2019-08-12 14:41:05,672 INFO  [PluginManager] Adding plugin from [C:\Users\atfprl\.soapui\plugins\ready-uxm-plugin-1.1.0.jar]
2019-08-12 14:41:05,786 INFO  [PluginManager] 3 plugins loaded in 5359 ms
2019-08-12 14:41:05,787 INFO  [DefaultSoapUICore] All plugins loaded
2019-08-12 14:41:05,807 INFO  [ModuleLoader] Module [LoadUI] added 0 actionGroups, 4 actions, 0 factories, 0 listeners, 0 toolbar components.
2019-08-12 14:41:05,868 INFO  [ModuleLoader] Module [Dashboard] added 0 actionGroups, 0 actions, 0 factories, 0 listeners, 0 toolbar components.
2019-08-12 14:41:06,754 INFO  [ModuleLoader] Module [ServiceV] added 19 actionGroups, 36 actions, 19 factories, 0 listeners, 0 toolbar components.
2019-08-12 14:41:06,775 INFO  [ModuleLoader] Module [Integrations] added 0 actionGroups, 0 actions, 0 factories, 0 listeners, 0 toolbar components.
2019-08-12 14:41:06,878 INFO  [ModuleLoader] Module [Secure] added 5 actionGroups, 13 actions, 2 factories, 0 listeners, 0 toolbar components.
2019-08-12 14:41:07,071 INFO  [ModuleLoader] Module [SoapUIProUserInterfaceModule] added 5 actionGroups, 208 actions, 3 factories, 0 listeners, 0 toolbar components.
2019-08-12 14:41:07,086 INFO  [ModuleLoader] Module [SoapUI] added 6 actionGroups, 6 actions, 1 factories, 0 listeners, 0 toolbar components.
2019-08-12 14:41:07,143 INFO  [ModuleLoader] Module [Projects] added 12 actionGroups, 2 actions, 1 factories, 0 listeners, 0 toolbar components.
2019-08-12 14:41:07,146 INFO  [ReadyApiInitializer] All modules loaded
2019-08-12 14:41:07,391 INFO  [ModuleLoader] Module [ReadyApiUI] added 6 actionGroups, 4 actions, 0 factories, 0 listeners, 0 toolbar components.
2019-08-12 14:41:07,392 INFO  [ReadyApiInitializer] Loading took 3368 ms
2019-08-12 14:41:07,403 INFO  [DiscoveryBroadcaster] No valid license for DiscoveryBroadcaster found. Not started.
2019-08-12 14:41:07,441 INFO  [LifecycleManager] Started 'LifecycleManager@1706505865'
2019-08-12 14:41:07,451 INFO  [CommonSwingReadyApiUi] Starting ReadyAPI 2.8.0 (build 3384)
2019-08-12 14:41:07,545 ERROR [SwingInvokeInterceptor] null
java.lang.NullPointerException: null
	at com.eviware.soapui.support.UISupport.getModuleLogo(UISupport.java:2910) ~[ready-api-soapui-2.8.0.jar:?]
	at com.smartbear.ready.ui.swing.CommonUiBuilder$ModuleLink.build(CommonUiBuilder.java:1048) ~[common-ui-2.8.0.jar:?]
	at com.smartbear.ready.ui.swing.CommonUiBuilder$ModuleLink.lambda$0(CommonUiBuilder.java:1032) ~[common-ui-2.8.0.jar:?]
	at com.eviware.soapui.support.swing.SwingUtils.invokeAndWaitIfNotInEDT(SwingUtils.java:42) ~[ready-api-soapui-2.8.0.jar:2.8.0]
	at com.eviware.soapui.support.UISupport.invokeAndWaitIfNotInEDT(UISupport.java:1640) ~[ready-api-soapui-2.8.0.jar:?]
	at com.smartbear.ready.ui.swing.CommonUiBuilder$ModuleLink.<init>(CommonUiBuilder.java:1031) ~[common-ui-2.8.0.jar:?]
	at com.smartbear.ready.ui.swing.CommonUiBuilder$TopBar.<init>(CommonUiBuilder.java:820) ~[common-ui-2.8.0.jar:?]
	at com.smartbear.ready.ui.swing.CommonUiBuilder.buildMainWindow(CommonUiBuilder.java:226) ~[common-ui-2.8.0.jar:?]
	at com.smartbear.ready.ui.swing.CommonSwingReadyApiUi.buildMainWindow(CommonSwingReadyApiUi.java:118) ~[common-ui-2.8.0.jar:?]
	at com.smartbear.ready.ui.swing.CommonSwingReadyApiUi.getMainWindow(CommonSwingReadyApiUi.java:110) ~[common-ui-2.8.0.jar:?]
	at com.smartbear.ready.ui.swing.CommonSwingReadyApiUi.runReadyApi(CommonSwingReadyApiUi.java:102) ~[common-ui-2.8.0.jar:?]
	at com.smartbear.ready.ui.swinginvoke.SwingInvokeInterceptor$InvocationRunner.run(SwingInvokeInterceptor.java:59) [ready-api-core-2.8.0.jar:?]
	at java.awt.event.InvocationEvent.dispatch(Unknown Source) [?:1.8.0_181]
	at java.awt.EventQueue.dispatchEventImpl(Unknown Source) [?:1.8.0_181]
	at java.awt.EventQueue.access$500(Unknown Source) [?:1.8.0_181]
	at java.awt.EventQueue$3.run(Unknown Source) [?:1.8.0_181]
	at java.awt.EventQueue$3.run(Unknown Source) [?:1.8.0_181]
	at java.security.AccessController.doPrivileged(Native Method) [?:1.8.0_181]
	at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source) [?:1.8.0_181]
	at java.awt.EventQueue.dispatchEvent(Unknown Source) [?:1.8.0_181]
	at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source) [?:1.8.0_181]
	at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source) [?:1.8.0_181]
	at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source) [?:1.8.0_181]
	at java.awt.EventDispatchThread.pumpEvents(Unknown Source) [?:1.8.0_181]
	at java.awt.EventDispatchThread.pumpEvents(Unknown Source) [?:1.8.0_181]
	at java.awt.EventDispatchThread.run(Unknown Source) [?:1.8.0_181]

 

I already contaced support.. I got one message: 

Thank you for creating the case.  Try adding the following line - "Dsoapui.browser.disabled=true" into vmoptions file(C:\Program Files\SmartBear\ReadyAPI-x.x.x\bin) and restart ReadyAPI.

 

I tried this but it didn't help. Maybe someone knows what the problem is and can help me to fix this? 

Thank you for your time. 

  • Huib's avatar
    Huib
    5 years ago

    Hi Olga_T,

     

    Thank yo for asking! I got the solution. It was very easy: 

    The disabled-tools.txt is causing the issue. Please check {your user profile directory}\.readyapi i.e C:\Users\yourusername\.readyapi directory on Windows for a disabled-tools.txt file. If it is there, delete the file and proceed to start ReadyAPI again.

     

    I had that file on my systems. It starts now :) 

3 Replies

  • Olga_T's avatar
    Olga_T
    SmartBear Alumni (Retired)

    Hi Huib,

     

    I have contacted our Support team regarding your question, and they said that you are working with them in a support case. It would be great if you could share the results with the Community when you have any.

    Thank you so much in advance!

     

    • Huib's avatar
      Huib
      New Contributor

      Hi Olga_T,

       

      Thank yo for asking! I got the solution. It was very easy: 

      The disabled-tools.txt is causing the issue. Please check {your user profile directory}\.readyapi i.e C:\Users\yourusername\.readyapi directory on Windows for a disabled-tools.txt file. If it is there, delete the file and proceed to start ReadyAPI again.

       

      I had that file on my systems. It starts now :) 

      • Olga_T's avatar
        Olga_T
        SmartBear Alumni (Retired)

        Thank you for the update, Huib! Good to hear this was solved! 

        Have a great day :smileyhappy: