Studio UI error : java.lang.NullPointerException

When I am clicking the invoke >> button in the action designer of the table which is supposed to take me to the controller,


I am getting the following exception:

17:40	Studio UI Error: java.lang.NullPointerException

Thank you for reporting the problem.
Created issue.

1 Like

It looks like this issue is still existing!


Could you please provide more information about your problem? Which version of the Studio do you use? Have you try to reproduce this problem in Studio build 183.9.1?

This is in the latest version of the studio 9.1

Hi Natalia
I think I need to share with you more info that may help you to identify this issue.
The issue i am experiencing with is the project that has been migrated to the new platform from v6.x. This is a large project having more than 800 Entities.

When I have created a brand new project, i get no error but in this large project. The issue might be related to such a large project or a project migrated to v7. Let me know if you need any additional info to investigate it for a fix. Looking forward for your help.

Could you please share idea.log file with us or stacktrace of the exception?

Hi Can you tell me where will this file be located?

In Help menu select Show log in Explorer (if you use macOS, this will be named Show log in Finder).



Here is the extracts:

2019-05-13 10:37:15,911 [81052320]   WARN - ialog.CubaNotificationsManager - Studio UI Error 
	at org.vaadin.aceeditor.SuggestionExtension$1.suggest(
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(
	at java.lang.reflect.Method.invoke(
	at com.vaadin.server.ServerRpcManager.applyInvocation(
	at com.vaadin.server.ServerRpcManager.applyInvocation(
	at com.vaadin.server.communication.ServerRpcHandler.handleInvocation(
	at com.vaadin.server.communication.ServerRpcHandler.handleInvocations(
	at com.vaadin.server.communication.ServerRpcHandler.handleRpc(
	at com.vaadin.server.communication.UidlRequestHandler.synchronizedHandleRequest(
	at com.vaadin.server.SynchronizedRequestHandler.handleRequest(
	at com.vaadin.server.VaadinService.handleRequest(
	at com.vaadin.server.VaadinServlet.service(
	at javax.servlet.http.HttpServlet.service(
	at org.eclipse.jetty.servlet.ServletHolder.handle(
	at org.eclipse.jetty.servlet.ServletHandler.doHandle(
	at org.eclipse.jetty.server.handler.ScopedHandler.handle(
	at org.eclipse.jetty.server.session.SessionHandler.doHandle(
	at org.eclipse.jetty.server.handler.ContextHandler.doHandle(
	at org.eclipse.jetty.servlet.ServletHandler.doScope(
	at org.eclipse.jetty.server.session.SessionHandler.doScope(
	at org.eclipse.jetty.server.handler.ContextHandler.doScope(
	at org.eclipse.jetty.server.handler.ScopedHandler.handle(
	at org.eclipse.jetty.server.handler.HandlerList.handle(
	at org.eclipse.jetty.server.handler.HandlerWrapper.handle(
	at org.eclipse.jetty.server.Server.handle(
	at org.eclipse.jetty.server.HttpChannel.handle(
	at org.eclipse.jetty.server.HttpConnection.onFillable(
	at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(
	at org.eclipse.jetty.util.thread.QueuedThreadPool$
2019-05-13 10:37:15,912 [81052321]   WARN - napi.components.ServiceManager - requested as a service, but it is a component - convert it to a service or change call to project.getComponent() 
2019-05-13 10:37:15,936 [81052345]   INFO - tudio.backend.stat.StatManager - Sending usage statistics 
2019-05-13 10:37:16,908 [81053317]   INFO - .openapi.util.LowMemoryWatcher - Low memory signal received: afterGc=false 
2019-05-13 10:37:16,911 [81053320]   INFO - .openapi.util.LowMemoryWatcher - Low memory signal received: afterGc=true

Thank you for reporting the problem. We have created a YouTrack issue

1 Like

Thanks for fixing this ASAP as this is slowing down the development.

Hi Natalia
I have experienced exception in updating the database script as attached. I am sharing if you get additional inputs from here.

idea.txt (391.9 KB)

This might be a different issue, Therefore, I have posted separately here to keep things separate.