topic Re: MDM - "Unable to parse the document" error in web client in Talend Data Catalog

MDM - "Unable to parse the document" error in web client

Anonymous — Sat, 16 Nov 2024 13:30:23 GMT

I am trying to evaluate the full MDM product. I used the windows .jar to unzip on a Win2008Server 64bit server and it starts up fine. Web client comes up as well.
I next use TDQTE client in MDM view to create a data container and a data model, give them descriptions and save them.
I bounce the MDM server. When it has come back up I log in with the web client, pick my container and model and get the following error:
Unable to parse the document: java.lang.NullPointerException null null
This is a clean install where I only did the preceding steps!
Can someone please tell me what's happening here??? I'm trying to put together a proof-of-concept to show how Talend MDM works.
Thanks!
- Dan

Re: MDM - "Unable to parse the document" error in web client

_AnonymousUser — Tue, 16 Mar 2010 14:39:46 GMT

hey dan,
this is very odd. i think i would need more information in order to debug as i cannot recreate. would you be able to paste a bit more of the exception stack here?
also note, there is no need to bounce the server whenever changes are made to the model., the services are automatically updated and deployed upon any save.
-jim

Re: MDM - "Unable to parse the document" error in web client

Anonymous — Tue, 16 Mar 2010 18:50:40 GMT

Did create views. I'm not seeing an exception stack; that message is on the popup from the web client.
What log would you like me to check?
- Dan

Re: MDM - "Unable to parse the document" error in web client

Anonymous — Thu, 18 Mar 2010 01:21:43 GMT

I checked when I start the server and I see:
21:20:09,130 ERROR (main Error starting endpoint
java.net.SocketException: Unrecognized Windows Sockets error: 0: JVM_Bind
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.PlainSocketImpl.bind(Unknown Source)
at java.net.ServerSocket.bind(Unknown Source)
at java.net.ServerSocket.<init>(Unknown Source)
at org.apache.tomcat.util.net.DefaultServerSocketFactory.createSocket(De
faultServerSocketFactory.java:56)
at org.apache.tomcat.util.net.JIoEndpoint.init(JIoEndpoint.java:497)
at org.apache.tomcat.util.net.JIoEndpoint.start(JIoEndpoint.java:514)
at org.apache.coyote.ajp.AjpProtocol.start(AjpProtocol.java:187)
at org.apache.catalina.connector.Connector.start(Connector.java:1146)
at org.jboss.web.tomcat.service.JBossWeb.startConnectors(JBossWeb.java:5
84)
at org.jboss.web.tomcat.service.JBossWeb.handleNotification(JBossWeb.jav
a:621)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.mx.notification.NotificationListenerProxy.invoke(Notificati
onListenerProxy.java:153)
at $Proxy46.handleNotification(Unknown Source)
at org.jboss.mx.util.JBossNotificationBroadcasterSupport.handleNotificat
ion(JBossNotificationBroadcasterSupport.java:127)
at org.jboss.mx.util.JBossNotificationBroadcasterSupport.sendNotificatio
n(JBossNotificationBroadcasterSupport.java:108)
at org.jboss.system.server.ServerImpl.sendNotification(ServerImpl.java:9
16)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:497)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
at org.jboss.Main.boot(Main.java:200)
at org.jboss.Main$1.run(Main.java:508)
at java.lang.Thread.run(Unknown Source)
21:20:09,145 WARN (main Failed to startConnectors
LifecycleException: service.getName(): "jboss.web"; Protocol handler start fai
led: java.net.SocketException: Unrecognized Windows Sockets error: 0: JVM_Bind
at org.apache.catalina.connector.Connector.start(Connector.java:1153)
at org.jboss.web.tomcat.service.JBossWeb.startConnectors(JBossWeb.java:5
84)
at org.jboss.web.tomcat.service.JBossWeb.handleNotification(JBossWeb.jav
a:621)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.mx.notification.NotificationListenerProxy.invoke(Notificati
onListenerProxy.java:153)
at $Proxy46.handleNotification(Unknown Source)
at org.jboss.mx.util.JBossNotificationBroadcasterSupport.handleNotificat
ion(JBossNotificationBroadcasterSupport.java:127)
at org.jboss.mx.util.JBossNotificationBroadcasterSupport.sendNotificatio
n(JBossNotificationBroadcasterSupport.java:108)
at org.jboss.system.server.ServerImpl.sendNotification(ServerImpl.java:9
16)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:497)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
at org.jboss.Main.boot(Main.java:200)
at org.jboss.Main$1.run(Main.java:508)
Any help?
- Dan

Re: MDM - "Unable to parse the document" error in web client

Anonymous — Fri, 19 Mar 2010 00:48:37 GMT

So I tried this on another Windows machine (XP this time) and left all of the defaults in the .jar install.
No errors on start; but after the same creates and web login:
20 10-03-18 20:40:49,234 452078 ERROR (http-0.0.0.0-8080-7
java.lang.Exception: Unable to parse the document: java.lang.NullPointerException: null
null
at com.amalto.webapp.core.util.Util.parse(Unknown Source)
at com.amalto.webapp.core.util.Util.parse(Unknown Source)
at com.amalto.webapp.core.util.Util.getLoginProvisioningFromDB(Unknown Source)
at com.amalto.webapp.core.bean.Configuration.load(Unknown Source)
at com.amalto.webapp.core.bean.Configuration.getInstance(Unknown Source)
at com.amalto.webapp.v3.xtentismdm.dwr.ActionsDWR.getModel(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.directwebremoting.impl.ExecuteAjaxFilter.doFilter(ExecuteAjaxFilter.java:34)
at org.directwebremoting.impl.DefaultRemoter$1.doFilter(DefaultRemoter.java:310)
at org.directwebremoting.impl.DefaultRemoter.execute(DefaultRemoter.java:313)
at org.directwebremoting.impl.DefaultRemoter.execute(DefaultRemoter.java:172)
at org.directwebremoting.servlet.UrlProcessor.handle(UrlProcessor.java:139)
at org.directwebremoting.servlet.DwrServlet.doPost(DwrServlet.java:227)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:524)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
at org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:420)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
at java.lang.Thread.run(Thread.java:619)
java.lang.Exception: Unable to parse the document: java.lang.NullPointerException: null
null
at com.amalto.webapp.core.util.Util.parse(Unknown Source)
at com.amalto.webapp.core.util.Util.parse(Unknown Source)
at com.amalto.webapp.core.util.Util.getLoginProvisioningFromDB(Unknown Source)
at com.amalto.webapp.core.bean.Configuration.load(Unknown Source)
at com.amalto.webapp.core.bean.Configuration.getInstance(Unknown Source)
at com.amalto.webapp.v3.xtentismdm.dwr.ActionsDWR.getCluster(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.directwebremoting.impl.ExecuteAjaxFilter.doFilter(ExecuteAjaxFilter.java:34)
at org.directwebremoting.impl.DefaultRemoter$1.doFilter(DefaultRemoter.java:310)
at org.directwebremoting.impl.DefaultRemoter.execute(DefaultRemoter.java:313)
at org.directwebremoting.impl.DefaultRemoter.execute(DefaultRemoter.java:172)
at org.directwebremoting.servlet.UrlProcessor.handle(UrlProcessor.java:139)
at org.directwebremoting.servlet.DwrServlet.doPost(DwrServlet.java:227)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:524)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
at org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:420)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
at java.lang.Thread.run(Thread.java:619)

20:40:48,843 INFO (http-0.0.0.0-8080-5 Type 'org.jd
om.Document' is not convertable due to missing converter 'jdom'. This is only an
problem if you wanted to use it.
20:40:48,843 INFO (http-0.0.0.0-8080-5 Type 'org.jd
om.Element' is not convertable due to missing converter 'jdom'. This is only an
problem if you wanted to use it.