How can I fix an error occurred while initializing modules

0
After I have merged/imported 2 modules into my master model and I have deleted some attributes in an entity and walk through the consistency errors and fix it. After all consistency errors have been fixed and no error in the model. I start to deploy the system as usual, but during deployment and starting the Mendix server, I found an error while deploy like this An error occurred while initializing modules java.lang.NullPointerException at w.a(SourceFile:242) at w.a(SourceFile:137) at dg.a(SourceFile:183) at dg.a(SourceFile:121) at w.a(SourceFile:267) at w.a(SourceFile:142) at gt.<init>(SourceFile:52) at com.mendix.core.MxRuntime.H(SourceFile:600) at com.mendix.core.MxRuntime.A(SourceFile:274) at com.mendix.core.MxRuntime.z(SourceFile:254) at com.mendix.core.MxRuntime.a(SourceFile:236) at lF.execute(SourceFile:54) at com.mendix.m2ee.server.handler.AdminHandler.handle(AdminHandler.java:84) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:113) at org.eclipse.jetty.server.Server.handle(Server.java:334) at org.eclipse.jetty.server.HttpConnection.handleRequest(HttpConnection.java:559) at org.eclipse.jetty.server.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:992) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:550) at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:203) at org.eclipse.jetty.server.HttpConnection.handle(HttpConnection.java:406) at org.eclipse.jetty.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:462) at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:436) at java.lang.Thread.run(Thread.java:619) Is this a bug in Mendix or there is some corruption in my model? Any ideas are welcome. Thank you very much in advance Somrak
asked
2 answers
0

If your project contains java then clean your deployment directory to get rid of old code that still uses attribute or entities.

answered
0

During the deployment I got another error about web service in the Mendix Modeler console. this occurred after previous error in the earlier post.

REMARK: we do not have any web service in this model. For the full trace-log please download HERE

Stack trace:

Request action: start
Message: Starting MxRuntime failed.
Cause: Webservice must not be null
Stack trace: com.mendix.m2ee.api.AdminException: Starting MxRuntime failed.
    at com.mendix.core.MxRuntime.z(SourceFile:259)
Caused by: java.lang.IllegalArgumentException: Webservice must not be null
    at dL.<init>(SourceFile:20)
    at com.mendix.core.MxRuntime.J(SourceFile:706)
    at com.mendix.core.MxRuntime.A(SourceFile:311)
    at com.mendix.core.MxRuntime.z(SourceFile:254)
    at com.mendix.core.MxRuntime.a(SourceFile:236)
    at lF.execute(SourceFile:54)
    at com.mendix.m2ee.server.handler.AdminHandler.handle(AdminHandler.java:84)
    at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:113)
    at org.eclipse.jetty.server.Server.handle(Server.java:334)
    at org.eclipse.jetty.server.HttpConnection.handleRequest(HttpConnection.java:559)
    at org.eclipse.jetty.server.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:992)
    at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:550)
    at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:203)
    at org.eclipse.jetty.server.HttpConnection.handle(HttpConnection.java:406)
    at org.eclipse.jetty.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:462)
    at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:436)
    at java.lang.Thread.run(Thread.java:619)
answered