Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Koneki » Problem Starting Koneki with DM-Server 3.6(Can't connect Koneki to Funambol DM-Server 3.6 after success install)
Problem Starting Koneki with DM-Server 3.6 [message #897575] Tue, 24 July 2012 14:59 Go to next message
Andre Tomas is currently offline Andre Tomas
Messages: 28
Registered: July 2012
Junior Member
Hello. I'm kinda new to this world, i'm trying to setup the funambol dm-server 3.6 and Koneki. I've followed this guide to install and setup both Koneki and DM-Server:

http://wiki.eclipse.org/Koneki/Simulators/OMA-DM/User_Guide

I'm on opensuse 11.4, every Ambient variable are set to the right place, i can install the jboss5 and set up the data base without any problem.

The DM-Server starts up just fine (at least i guess), after that i create a new ID to use and try to connect via Koneki and then i get the following exception:

15:51:17,058 WARN  [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container
15:51:17,086 WARN  [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container
15:51:17,183 WARN  [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container
15:51:17,183 WARN  [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container
15:51:17,619 ERROR [STDERR] org.jibx.runtime.JiBXException: No unmarshaller for element "{SYNCML:SYNCML1.2}SyncML" (line 1, col 71)
15:51:17,620 ERROR [STDERR]     at org.jibx.runtime.impl.UnmarshallingContext.unmarshalElement(UnmarshallingContext.java:2565)
15:51:17,620 ERROR [STDERR]     at org.jibx.runtime.impl.UnmarshallingContext.unmarshalDocument(UnmarshallingContext.java:2736)
15:51:17,620 ERROR [STDERR]     at com.funambol.server.engine.SyncAdapter.processMessage(SyncAdapter.java:287)
15:51:17,620 ERROR [STDERR]     at com.funambol.server.syncbean.SyncBean.processMessage(SyncBean.java:228)
15:51:17,620 ERROR [STDERR]     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
15:51:17,620 ERROR [STDERR]     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
15:51:17,620 ERROR [STDERR]     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
15:51:17,620 ERROR [STDERR]     at java.lang.reflect.Method.invoke(Method.java:597)
15:51:17,621 ERROR [STDERR]     at org.jboss.aop.joinpoint.MethodInvocation.invokeTarget(MethodInvocation.java:122)
15:51:17,621 ERROR [STDERR]     at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111)
15:51:17,621 ERROR [STDERR]     at org.jboss.ejb3.EJBContainerInvocationWrapper.invokeNext(EJBContainerInvocationWrapper.java:69)
15:51:17,621 ERROR [STDERR]     at org.jboss.ejb3.interceptors.aop.InterceptorSequencer.invoke(InterceptorSequencer.java:73)
15:51:17,621 ERROR [STDERR]     at org.jboss.ejb3.interceptors.aop.InterceptorSequencer.aroundInvoke(InterceptorSequencer.java:59)
15:51:17,621 ERROR [STDERR]     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
15:51:17,621 ERROR [STDERR]     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
15:51:17,621 ERROR [STDERR]     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
15:51:17,621 ERROR [STDERR]     at java.lang.reflect.Method.invoke(Method.java:597)
15:51:17,621 ERROR [STDERR]     at org.jboss.aop.advice.PerJoinpointAdvice.invoke(PerJoinpointAdvice.java:174)
15:51:17,621 ERROR [STDERR]     at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
15:51:17,621 ERROR [STDERR]     at org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor.fillMethod(InvocationContextInterceptor.java:72)
15:51:17,621 ERROR [STDERR]     at org.jboss.aop.advice.org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor_z_fillMethod_1852690398.invoke(InvocationContextInterceptor_z_fillMethod_1852690398.java)
15:51:17,621 ERROR [STDERR]     at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
15:51:17,621 ERROR [STDERR]     at org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor.setup(InvocationContextInterceptor.java:88)
15:51:17,622 ERROR [STDERR]     at org.jboss.aop.advice.org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor_z_setup_1852690398.invoke(InvocationContextInterceptor_z_setup_1852690398.java)
15:51:17,622 ERROR [STDERR]     at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
15:51:17,622 ERROR [STDERR]     at org.jboss.ejb3.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:62)
15:51:17,622 ERROR [STDERR]     at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
15:51:17,622 ERROR [STDERR]     at org.jboss.ejb3.entity.ExtendedPersistenceContextPropagationInterceptor.invoke(ExtendedPersistenceContextPropagationInterceptor.java:60)
15:51:17,622 ERROR [STDERR]     at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
15:51:17,622 ERROR [STDERR]     at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:56)
15:51:17,622 ERROR [STDERR]     at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
15:51:17,622 ERROR [STDERR]     at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47)
15:51:17,622 ERROR [STDERR]     at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
15:51:17,622 ERROR [STDERR]     at org.jboss.ejb3.tx.NullInterceptor.invoke(NullInterceptor.java:42)
15:51:17,622 ERROR [STDERR]     at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
15:51:17,622 ERROR [STDERR]     at org.jboss.ejb3.stateful.StatefulInstanceInterceptor.invoke(StatefulInstanceInterceptor.java:81)
15:51:17,622 ERROR [STDERR]     at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
15:51:17,622 ERROR [STDERR]     at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79)
15:51:17,622 ERROR [STDERR]     at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:190)
15:51:17,623 ERROR [STDERR]     at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
15:51:17,623 ERROR [STDERR]     at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76)
15:51:17,623 ERROR [STDERR]     at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
15:51:17,623 ERROR [STDERR]     at org.jboss.ejb3.tx.NullInterceptor.invoke(NullInterceptor.java:42)
15:51:17,623 ERROR [STDERR]     at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
15:51:17,623 ERROR [STDERR]     at org.jboss.ejb3.security.Ejb3AuthenticationInterceptorv2.invoke(Ejb3AuthenticationInterceptorv2.java:186)
15:51:17,623 ERROR [STDERR]     at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
15:51:17,623 ERROR [STDERR]     at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:41)
15:51:17,623 ERROR [STDERR]     at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
15:51:17,623 ERROR [STDERR]     at org.jboss.ejb3.BlockContainerShutdownInterceptor.invoke(BlockContainerShutdownInterceptor.java:67)
15:51:17,623 ERROR [STDERR]     at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
15:51:17,623 ERROR [STDERR]     at org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor.invoke(CurrentInvocationInterceptor.java:67)
15:51:17,623 ERROR [STDERR]     at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
15:51:17,623 ERROR [STDERR]     at org.jboss.ejb3.session.SessionSpecContainer.invoke(SessionSpecContainer.java:176)
15:51:17,623 ERROR [STDERR]     at org.jboss.ejb3.session.SessionSpecContainer.invoke(SessionSpecContainer.java:216)
15:51:17,624 ERROR [STDERR]     at org.jboss.ejb3.proxy.impl.handler.session.SessionProxyInvocationHandlerBase.invoke(SessionProxyInvocationHandlerBase.java:207)
15:51:17,624 ERROR [STDERR]     at org.jboss.ejb3.proxy.impl.handler.session.SessionProxyInvocationHandlerBase.invoke(SessionProxyInvocationHandlerBase.java:164)
15:51:17,624 ERROR [STDERR]     at $Proxy266.processMessage(Unknown Source)
15:51:17,624 ERROR [STDERR]     at com.funambol.transport.http.server.LocalEJBSyncHolder.processMessage(LocalEJBSyncHolder.java:88)
15:51:17,624 ERROR [STDERR]     at com.funambol.transport.http.server.Sync4jServlet.doPost(Sync4jServlet.java:250)
15:51:17,624 ERROR [STDERR]     at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
15:51:17,624 ERROR [STDERR]     at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
15:51:17,624 ERROR [STDERR]     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
15:51:17,624 ERROR [STDERR]     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
15:51:17,624 ERROR [STDERR]     at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
15:51:17,624 ERROR [STDERR]     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
15:51:17,624 ERROR [STDERR]     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
15:51:17,624 ERROR [STDERR]     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
15:51:17,624 ERROR [STDERR]     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
15:51:17,624 ERROR [STDERR]     at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
15:51:17,625 ERROR [STDERR]     at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
15:51:17,625 ERROR [STDERR]     at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
15:51:17,625 ERROR [STDERR]     at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
15:51:17,625 ERROR [STDERR]     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
15:51:17,625 ERROR [STDERR]     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
15:51:17,625 ERROR [STDERR]     at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
15:51:17,625 ERROR [STDERR]     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
15:51:17,625 ERROR [STDERR]     at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
15:51:17,625 ERROR [STDERR]     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
15:51:17,625 ERROR [STDERR]     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598)
15:51:17,625 ERROR [STDERR]     at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
15:51:17,625 ERROR [STDERR]     at java.lang.Thread.run(Thread.java:662)
15:51:17,625 FATAL [SyncAdapter] Error unmarshalling message: No unmarshaller for element "{SYNCML:SYNCML1.2}SyncML" (line 1, col 71)
15:51:17,647 ERROR [[SyncServerServlet]] Servlet.service() for servlet SyncServerServlet threw exception
org.jibx.runtime.JiBXException: No unmarshaller for element "{SYNCML:SYNCML1.2}SyncML" (line 1, col 71)
        at org.jibx.runtime.impl.UnmarshallingContext.unmarshalElement(UnmarshallingContext.java:2565)
        at org.jibx.runtime.impl.UnmarshallingContext.unmarshalDocument(UnmarshallingContext.java:2736)
        at com.funambol.server.engine.SyncAdapter.processMessage(SyncAdapter.java:287)
        at com.funambol.server.syncbean.SyncBean.processMessage(SyncBean.java:228)
        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.jboss.aop.joinpoint.MethodInvocation.invokeTarget(MethodInvocation.java:122)
        at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111)
        at org.jboss.ejb3.EJBContainerInvocationWrapper.invokeNext(EJBContainerInvocationWrapper.java:69)
        at org.jboss.ejb3.interceptors.aop.InterceptorSequencer.invoke(InterceptorSequencer.java:73)
        at org.jboss.ejb3.interceptors.aop.InterceptorSequencer.aroundInvoke(InterceptorSequencer.java:59)
        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.jboss.aop.advice.PerJoinpointAdvice.invoke(PerJoinpointAdvice.java:174)
        at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
        at org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor.fillMethod(InvocationContextInterceptor.java:72)
        at org.jboss.aop.advice.org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor_z_fillMethod_1852690398.invoke(InvocationContextInterceptor_z_fillMethod_1852690398.java)
        at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
        at org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor.setup(InvocationContextInterceptor.java:88)
        at org.jboss.aop.advice.org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor_z_setup_1852690398.invoke(InvocationContextInterceptor_z_setup_1852690398.java)
        at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
        at org.jboss.ejb3.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:62)
        at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
        at org.jboss.ejb3.entity.ExtendedPersistenceContextPropagationInterceptor.invoke(ExtendedPersistenceContextPropagationInterceptor.java:60)
        at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
        at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:56)
        at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
        at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47)
        at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
        at org.jboss.ejb3.tx.NullInterceptor.invoke(NullInterceptor.java:42)
        at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
        at org.jboss.ejb3.stateful.StatefulInstanceInterceptor.invoke(StatefulInstanceInterceptor.java:81)
        at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
        at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79)
        at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:190)
        at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
        at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76)
        at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
        at org.jboss.ejb3.tx.NullInterceptor.invoke(NullInterceptor.java:42)
        at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
        at org.jboss.ejb3.security.Ejb3AuthenticationInterceptorv2.invoke(Ejb3AuthenticationInterceptorv2.java:186)
        at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
        at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:41)
        at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
        at org.jboss.ejb3.BlockContainerShutdownInterceptor.invoke(BlockContainerShutdownInterceptor.java:67)
        at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
        at org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor.invoke(CurrentInvocationInterceptor.java:67)
        at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
        at org.jboss.ejb3.session.SessionSpecContainer.invoke(SessionSpecContainer.java:176)
        at org.jboss.ejb3.session.SessionSpecContainer.invoke(SessionSpecContainer.java:216)
        at org.jboss.ejb3.proxy.impl.handler.session.SessionProxyInvocationHandlerBase.invoke(SessionProxyInvocationHandlerBase.java:207)
        at org.jboss.ejb3.proxy.impl.handler.session.SessionProxyInvocationHandlerBase.invoke(SessionProxyInvocationHandlerBase.java:164)
        at $Proxy266.processMessage(Unknown Source)
        at com.funambol.transport.http.server.LocalEJBSyncHolder.processMessage(LocalEJBSyncHolder.java:88)
        at com.funambol.transport.http.server.Sync4jServlet.doPost(Sync4jServlet.java:250)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
        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:235)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
        at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
        at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
        at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
        at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
        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:158)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
        at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
        at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598)
        at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
        at java.lang.Thread.run(Thread.java:662)


I'm Doing something wrong? i've look to the guide number of times and i don't understand what i may be doing wrong...

I can see it's something related to the SyncML 1.2 unmarshal. But i have look time and time again on the web on the forum and nothing i can't find any solution to this..

[Updated on: Tue, 24 July 2012 15:02]

Report message to a moderator

Re: Problem Starting Koneki with DM-Server 3.6 [message #897590 is a reply to message #897575] Tue, 24 July 2012 16:09 Go to previous messageGo to next message
Benjamin Cabé is currently offline Benjamin Cabé
Messages: 151
Registered: July 2009
Location: Toulouse, France
Senior Member

Hi Andre,
Could you post the XML messages that the simulator is sending and that are causing trouble. You can get them from the Dashboard/Message view tab.

Thanks!
Benjamin.
Re: Problem Starting Koneki with DM-Server 3.6 [message #897603 is a reply to message #897590] Tue, 24 July 2012 16:50 Go to previous messageGo to next message
Andre Tomas is currently offline Andre Tomas
Messages: 28
Registered: July 2012
Junior Member
Benjamin Cabe wrote on Tue, 24 July 2012 12:09
Hi Andre,
Could you post the XML messages that the simulator is sending and that are causing trouble. You can get them from the Dashboard/Message view tab.

Thanks!
Benjamin.


First of all thank you for your answer, and of course. The message is the follow:

<?xml version="1.0" encoding="UTF-8"?>
<SyncML xmlns="SYNCML:SYNCML1.2">
  <SyncHdr>
    <VerDTD>1.2</VerDTD>
    <VerProto>DM/1.2</VerProto>
    <SessionID>1</SessionID>
    <MsgID>1</MsgID>
    <Target>
      <LocURI>h**p://localhost:8080/funambol/dm</LocURI>
    </Target>
    <Source>
      <LocURI>FREE:12345</LocURI>
    </Source>
    <Cred>
      <Meta>
        <Format xmlns="syncml:metinf">b64</Format>
        <Type xmlns="syncml:metinf">syncml:auth-basic</Type>
      </Meta>
      <Data>ZnVuYW1ib2w6ZnVuYW1ib2w=</Data>
    </Cred>
  </SyncHdr>
  <SyncBody>
    <Alert>
      <CmdID>1</CmdID>
      <Data>1201</Data>
    </Alert>
    <Replace>
      <CmdID>2</CmdID>
      <Meta>
        <Format xmlns="syncml:metinf">chr</Format>
        <Type xmlns="syncml:metinf">text/plain</Type>
      </Meta>
      <Item>
        <Source>
          <LocURI>./DevInfo/DevId</LocURI>
        </Source>
        <Data>FREE:12345</Data>
      </Item>
      <Item>
        <Source>
          <LocURI>./DevInfo/DwV</LocURI>
        </Source>
        <Data/>
      </Item>
      <Item>
        <Source>
          <LocURI>./DevInfo/Man</LocURI>
        </Source>
        <Data>Nokia</Data>
      </Item>
      <Item>
        <Source>
          <LocURI>./DevInfo/Mod</LocURI>
        </Source>
        <Data>S534</Data>
      </Item>
      <Item>
        <Source>
          <LocURI>./DevInfo/Lang</LocURI>
        </Source>
        <Data>PT</Data>
      </Item>
    </Replace>
    <Final/>
  </SyncBody>
</SyncML>


I haven't touch in the eclipse code so far. So i guess this is the standard message for the setup phase.
Re: Problem Starting Koneki with DM-Server 3.6 [message #899028 is a reply to message #897603] Mon, 30 July 2012 09:10 Go to previous messageGo to next message
Andre Tomas is currently offline Andre Tomas
Messages: 28
Registered: July 2012
Junior Member
Anyone have any idea why this is happen? i've tryed almost everything i could remember, clean install the DM-Server, reinstall Koneki, check the libs on server side, and i'm getting no where..
If someone could help me it would be awesome.
Re: Problem Starting Koneki with DM-Server 3.6 [message #899513 is a reply to message #899028] Wed, 01 August 2012 09:11 Go to previous messageGo to next message
Julien Vermillard is currently offline Julien Vermillard
Messages: 7
Registered: August 2012
Junior Member
The generated XML is fine for me. I suppose the problem is funambol.
Yio uare sure your funambol path is correct ? 8080:/funambol/dm is for OMADM ?

Please can you make a wireshark capture of the client/server communication ? The idea is to check in the HTTP content-type is correct.
Re: Problem Starting Koneki with DM-Server 3.6 [message #903041 is a reply to message #899513] Tue, 21 August 2012 17:45 Go to previous messageGo to next message
Andre Tomas is currently offline Andre Tomas
Messages: 28
Registered: July 2012
Junior Member
Julien Vermillard wrote on Wed, 01 August 2012 05:11
The generated XML is fine for me. I suppose the problem is funambol.
Yio uare sure your funambol path is correct ? 8080:/funambol/dm is for OMADM ?

Please can you make a wireshark capture of the client/server communication ? The idea is to check in the HTTP content-type is correct.


Hello there, and thank you for your answer. Well i think the path is corrected, (this may sound newbie, but its kinda what i fell now), when i open the path 8080:/funambol/dm the browser gives me the follow message:

HTTP Status 405 - HTTP method GET is not supported by this URL

type Status report

message HTTP method GET is not supported by this URL

description The specified HTTP method is not allowed for the requested resource (HTTP method GET is not supported by this URL).
JBoss Web/2.1.2.G

Furthermore, the message was built, if i try to connect to any other place witch don't have any OMADM server running the Koneki "message" is not even built.

The wireshark capture can be found in here: h**p://www.mediafire.com/download.php?d4njq1f06ih3ynn

[Updated on: Wed, 22 August 2012 11:08]

Report message to a moderator

Re: Problem Starting Koneki with DM-Server 3.6 [message #904135 is a reply to message #897575] Mon, 27 August 2012 21:08 Go to previous messageGo to next message
Brandon F is currently offline Brandon F
Messages: 14
Registered: August 2012
Junior Member
Hello,

I have exactly the same issue as Andre. Installation of JBoss, Koneki and Funambol worked fine, I can access the Funambol and JBoss web interface, the devices I create get stored in the database.

But when I want to connect with Koneki, the following happens:
Koneki shows an alert with "HTTP/1.1 500 Internal Server Error" and I get the same error log as Andre:

22:54:36,133 WARN  [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container
22:54:36,137 WARN  [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container
22:54:36,171 WARN  [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container
22:54:36,172 WARN  [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container
22:54:36,389 ERROR [STDERR] org.jibx.runtime.JiBXException: No unmarshaller for element "{SYNCML:SYNCML1.2}SyncML" (line 1, col 71)
22:54:36,390 ERROR [STDERR] 	at org.jibx.runtime.impl.UnmarshallingContext.unmarshalElement(UnmarshallingContext.java:2565)
22:54:36,390 ERROR [STDERR] 	at org.jibx.runtime.impl.UnmarshallingContext.unmarshalDocument(UnmarshallingContext.java:2736)
22:54:36,390 ERROR [STDERR] 	at com.funambol.server.engine.SyncAdapter.processMessage(SyncAdapter.java:287)
22:54:36,391 ERROR [STDERR] 	at com.funambol.server.syncbean.SyncBean.processMessage(SyncBean.java:228)
22:54:36,391 ERROR [STDERR] 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
22:54:36,391 ERROR [STDERR] 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
22:54:36,391 ERROR [STDERR] 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
22:54:36,391 ERROR [STDERR] 	at java.lang.reflect.Method.invoke(Method.java:616)
22:54:36,391 ERROR [STDERR] 	at org.jboss.aop.joinpoint.MethodInvocation.invokeTarget(MethodInvocation.java:122)
22:54:36,391 ERROR [STDERR] 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111)
22:54:36,391 ERROR [STDERR] 	at org.jboss.ejb3.EJBContainerInvocationWrapper.invokeNext(EJBContainerInvocationWrapper.java:69)
22:54:36,391 ERROR [STDERR] 	at org.jboss.ejb3.interceptors.aop.InterceptorSequencer.invoke(InterceptorSequencer.java:73)
22:54:36,391 ERROR [STDERR] 	at org.jboss.ejb3.interceptors.aop.InterceptorSequencer.aroundInvoke(InterceptorSequencer.java:59)
22:54:36,391 ERROR [STDERR] 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
22:54:36,391 ERROR [STDERR] 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
22:54:36,391 ERROR [STDERR] 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
22:54:36,391 ERROR [STDERR] 	at java.lang.reflect.Method.invoke(Method.java:616)
22:54:36,391 ERROR [STDERR] 	at org.jboss.aop.advice.PerJoinpointAdvice.invoke(PerJoinpointAdvice.java:174)
22:54:36,391 ERROR [STDERR] 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
22:54:36,391 ERROR [STDERR] 	at org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor.fillMethod(InvocationContextInterceptor.java:72)
22:54:36,391 ERROR [STDERR] 	at org.jboss.aop.advice.org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor_z_fillMethod_10922545.invoke(InvocationContextInterceptor_z_fillMethod_10922545.java)
22:54:36,391 ERROR [STDERR] 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
22:54:36,391 ERROR [STDERR] 	at org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor.setup(InvocationContextInterceptor.java:88)
22:54:36,398 ERROR [STDERR] 	at org.jboss.aop.advice.org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor_z_setup_10922545.invoke(InvocationContextInterceptor_z_setup_10922545.java)
22:54:36,398 ERROR [STDERR] 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
22:54:36,398 ERROR [STDERR] 	at org.jboss.ejb3.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:62)
22:54:36,398 ERROR [STDERR] 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
22:54:36,398 ERROR [STDERR] 	at org.jboss.ejb3.entity.ExtendedPersistenceContextPropagationInterceptor.invoke(ExtendedPersistenceContextPropagationInterceptor.java:60)
22:54:36,398 ERROR [STDERR] 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
22:54:36,398 ERROR [STDERR] 	at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:56)
22:54:36,398 ERROR [STDERR] 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
22:54:36,398 ERROR [STDERR] 	at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47)
22:54:36,399 ERROR [STDERR] 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
22:54:36,399 ERROR [STDERR] 	at org.jboss.ejb3.tx.NullInterceptor.invoke(NullInterceptor.java:42)
22:54:36,399 ERROR [STDERR] 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
22:54:36,399 ERROR [STDERR] 	at org.jboss.ejb3.stateful.StatefulInstanceInterceptor.invoke(StatefulInstanceInterceptor.java:81)
22:54:36,399 ERROR [STDERR] 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
22:54:36,399 ERROR [STDERR] 	at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79)
22:54:36,399 ERROR [STDERR] 	at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:190)
22:54:36,399 ERROR [STDERR] 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
22:54:36,399 ERROR [STDERR] 	at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76)
22:54:36,399 ERROR [STDERR] 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
22:54:36,399 ERROR [STDERR] 	at org.jboss.ejb3.tx.NullInterceptor.invoke(NullInterceptor.java:42)
22:54:36,399 ERROR [STDERR] 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
22:54:36,399 ERROR [STDERR] 	at org.jboss.ejb3.security.Ejb3AuthenticationInterceptorv2.invoke(Ejb3AuthenticationInterceptorv2.java:186)
22:54:36,399 ERROR [STDERR] 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
22:54:36,399 ERROR [STDERR] 	at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:41)
22:54:36,405 ERROR [STDERR] 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
22:54:36,405 ERROR [STDERR] 	at org.jboss.ejb3.BlockContainerShutdownInterceptor.invoke(BlockContainerShutdownInterceptor.java:67)
22:54:36,405 ERROR [STDERR] 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
22:54:36,406 ERROR [STDERR] 	at org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor.invoke(CurrentInvocationInterceptor.java:67)
22:54:36,406 ERROR [STDERR] 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
22:54:36,406 ERROR [STDERR] 	at org.jboss.ejb3.session.SessionSpecContainer.invoke(SessionSpecContainer.java:176)
22:54:36,406 ERROR [STDERR] 	at org.jboss.ejb3.session.SessionSpecContainer.invoke(SessionSpecContainer.java:216)
22:54:36,406 ERROR [STDERR] 	at org.jboss.ejb3.proxy.impl.handler.session.SessionProxyInvocationHandlerBase.invoke(SessionProxyInvocationHandlerBase.java:207)
22:54:36,406 ERROR [STDERR] 	at org.jboss.ejb3.proxy.impl.handler.session.SessionProxyInvocationHandlerBase.invoke(SessionProxyInvocationHandlerBase.java:164)
22:54:36,406 ERROR [STDERR] 	at $Proxy266.processMessage(Unknown Source)
22:54:36,406 ERROR [STDERR] 	at com.funambol.transport.http.server.LocalEJBSyncHolder.processMessage(LocalEJBSyncHolder.java:88)
22:54:36,406 ERROR [STDERR] 	at com.funambol.transport.http.server.Sync4jServlet.doPost(Sync4jServlet.java:250)
22:54:36,406 ERROR [STDERR] 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
22:54:36,406 ERROR [STDERR] 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
22:54:36,406 ERROR [STDERR] 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
22:54:36,406 ERROR [STDERR] 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
22:54:36,406 ERROR [STDERR] 	at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
22:54:36,407 ERROR [STDERR] 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
22:54:36,407 ERROR [STDERR] 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
22:54:36,407 ERROR [STDERR] 	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
22:54:36,407 ERROR [STDERR] 	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
22:54:36,407 ERROR [STDERR] 	at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
22:54:36,407 ERROR [STDERR] 	at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
22:54:36,407 ERROR [STDERR] 	at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
22:54:36,407 ERROR [STDERR] 	at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
22:54:36,407 ERROR [STDERR] 	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
22:54:36,407 ERROR [STDERR] 	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
22:54:36,407 ERROR [STDERR] 	at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
22:54:36,407 ERROR [STDERR] 	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
22:54:36,407 ERROR [STDERR] 	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
22:54:36,407 ERROR [STDERR] 	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
22:54:36,407 ERROR [STDERR] 	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598)
22:54:36,407 ERROR [STDERR] 	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
22:54:36,408 ERROR [STDERR] 	at java.lang.Thread.run(Thread.java:636)
22:54:36,408 FATAL [SyncAdapter] Error unmarshalling message: No unmarshaller for element "{SYNCML:SYNCML1.2}SyncML" (line 1, col 71)
22:54:36,425 ERROR [[SyncServerServlet]] Servlet.service() for servlet SyncServerServlet threw exception
org.jibx.runtime.JiBXException: No unmarshaller for element "{SYNCML:SYNCML1.2}SyncML" (line 1, col 71)
	at org.jibx.runtime.impl.UnmarshallingContext.unmarshalElement(UnmarshallingContext.java:2565)
	at org.jibx.runtime.impl.UnmarshallingContext.unmarshalDocument(UnmarshallingContext.java:2736)
	at com.funambol.server.engine.SyncAdapter.processMessage(SyncAdapter.java:287)
	at com.funambol.server.syncbean.SyncBean.processMessage(SyncBean.java:228)
	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:616)
	at org.jboss.aop.joinpoint.MethodInvocation.invokeTarget(MethodInvocation.java:122)
	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111)
	at org.jboss.ejb3.EJBContainerInvocationWrapper.invokeNext(EJBContainerInvocationWrapper.java:69)
	at org.jboss.ejb3.interceptors.aop.InterceptorSequencer.invoke(InterceptorSequencer.java:73)
	at org.jboss.ejb3.interceptors.aop.InterceptorSequencer.aroundInvoke(InterceptorSequencer.java:59)
	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:616)
	at org.jboss.aop.advice.PerJoinpointAdvice.invoke(PerJoinpointAdvice.java:174)
	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
	at org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor.fillMethod(InvocationContextInterceptor.java:72)
	at org.jboss.aop.advice.org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor_z_fillMethod_10922545.invoke(InvocationContextInterceptor_z_fillMethod_10922545.java)
	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
	at org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor.setup(InvocationContextInterceptor.java:88)
	at org.jboss.aop.advice.org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor_z_setup_10922545.invoke(InvocationContextInterceptor_z_setup_10922545.java)
	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
	at org.jboss.ejb3.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:62)
	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
	at org.jboss.ejb3.entity.ExtendedPersistenceContextPropagationInterceptor.invoke(ExtendedPersistenceContextPropagationInterceptor.java:60)
	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
	at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:56)
	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
	at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47)
	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
	at org.jboss.ejb3.tx.NullInterceptor.invoke(NullInterceptor.java:42)
	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
	at org.jboss.ejb3.stateful.StatefulInstanceInterceptor.invoke(StatefulInstanceInterceptor.java:81)
	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
	at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79)
	at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:190)
	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
	at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76)
	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
	at org.jboss.ejb3.tx.NullInterceptor.invoke(NullInterceptor.java:42)
	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
	at org.jboss.ejb3.security.Ejb3AuthenticationInterceptorv2.invoke(Ejb3AuthenticationInterceptorv2.java:186)
	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
	at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:41)
	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
	at org.jboss.ejb3.BlockContainerShutdownInterceptor.invoke(BlockContainerShutdownInterceptor.java:67)
	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
	at org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor.invoke(CurrentInvocationInterceptor.java:67)
	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
	at org.jboss.ejb3.session.SessionSpecContainer.invoke(SessionSpecContainer.java:176)
	at org.jboss.ejb3.session.SessionSpecContainer.invoke(SessionSpecContainer.java:216)
	at org.jboss.ejb3.proxy.impl.handler.session.SessionProxyInvocationHandlerBase.invoke(SessionProxyInvocationHandlerBase.java:207)
	at org.jboss.ejb3.proxy.impl.handler.session.SessionProxyInvocationHandlerBase.invoke(SessionProxyInvocationHandlerBase.java:164)
	at $Proxy266.processMessage(Unknown Source)
	at com.funambol.transport.http.server.LocalEJBSyncHolder.processMessage(LocalEJBSyncHolder.java:88)
	at com.funambol.transport.http.server.Sync4jServlet.doPost(Sync4jServlet.java:250)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
	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:235)
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
	at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
	at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
	at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
	at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
	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:158)
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598)
	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
	at java.lang.Thread.run(Thread.java:636)


Any ideas? Are there any Funambol servers out there which are open to use? This way I could at least check if my Koneki is working correctly.

Thanks in advance,

Brandon
Re: Problem Starting Koneki with DM-Server 3.6 [message #905020 is a reply to message #904135] Wed, 29 August 2012 15:05 Go to previous messageGo to next message
Benjamin Cabé is currently offline Benjamin Cabé
Messages: 151
Registered: July 2009
Location: Toulouse, France
Senior Member

Guys, any luck refering to this thread?
Re: Problem Starting Koneki with DM-Server 3.6 [message #905083 is a reply to message #905020] Wed, 29 August 2012 16:46 Go to previous messageGo to next message
Andre Tomas is currently offline Andre Tomas
Messages: 28
Registered: July 2012
Junior Member
Hello there and thank you for the quick responses Smile

I had the same problem noted in that thread, but with some search i end up finding a version of the Dm-Server 3.6, but it may be modifed i don't know. Tomorrow i will try the version you posted here and give some feedback. Thank you Smile
Re: Problem Starting Koneki with DM-Server 3.6 [message #905104 is a reply to message #905083] Wed, 29 August 2012 17:38 Go to previous messageGo to next message
Brandon F is currently offline Brandon F
Messages: 14
Registered: August 2012
Junior Member
Hey,
I changed from Debian to Ubuntu and everything works fine suddenly Smile
I used exactly the same versions as stated in the guide, on Debian I used Postgresql 8 and JDBC v4, maybe that was the reason, but I'm not sure. But I used the DM server version which was linked in the thread above.
Anyway thank you for your help!

Best regards

Brandon
Re: Problem Starting Koneki with DM-Server 3.6 [message #905111 is a reply to message #905104] Wed, 29 August 2012 17:57 Go to previous messageGo to next message
Benjamin Cabé is currently offline Benjamin Cabé
Messages: 151
Registered: July 2009
Location: Toulouse, France
Senior Member

Yeah, great news Brandon! Smile
Looking forward to helping you again if need be!

Cheers,
Benjamin
Re: Problem Starting Koneki with DM-Server 3.6 [message #907246 is a reply to message #905111] Mon, 03 September 2012 15:57 Go to previous messageGo to next message
Andre Tomas is currently offline Andre Tomas
Messages: 28
Registered: July 2012
Junior Member
No luck on me, i used the server you linked on yhe other thread, but still got the exact same error... Sad is it because i'm using an OpenSuse distribution?? I know they are different, but what differs form Ubuntu that's causing me to have this error??

Well, i'll install an Ubuntu virtual machine on one of my machines and try to connect Funambol with Koneki again and see if i got any luck.

Thanks a lot for all the suggestions.
Re: Problem Starting Koneki with DM-Server 3.6 [message #907278 is a reply to message #907246] Mon, 03 September 2012 16:40 Go to previous messageGo to next message
Benjamin Cabé is currently offline Benjamin Cabé
Messages: 151
Registered: July 2009
Location: Toulouse, France
Senior Member

Hi Andre,

What JRE version are you using? Maybe that where the difference can be between Ubuntu and the rest of the world?

Benjamin.
Re: Problem Starting Koneki with DM-Server 3.6 [message #907283 is a reply to message #897575] Mon, 03 September 2012 16:53 Go to previous messageGo to next message
Andre Tomas is currently offline Andre Tomas
Messages: 28
Registered: July 2012
Junior Member
I thought of that as well, but i kinda discard that option because i'm using a regular version: java version "1.6.0_24",OpenJDK version, and i think by the time the test was made in the same version of java. Or it would require me to have java 1.7?

I been thinking on that, why i'm keep receiving the "internal Error". I'll try on the ubuntu virtual machine and if i can there i'll check for diferences..

[Updated on: Mon, 03 September 2012 16:54]

Report message to a moderator

Re: Problem Starting Koneki with DM-Server 3.6 [message #907930 is a reply to message #907283] Tue, 04 September 2012 12:51 Go to previous messageGo to next message
Andre Tomas is currently offline Andre Tomas
Messages: 28
Registered: July 2012
Junior Member
Still no Luck. I've tried on Ubuntu, tried to change the Java to sun 1.6 jdk. Do i need to have a special user or special configuration on the postgresql engine and/or funambol database?

Right now i'm starting to question everything i can think of...

PS: I'm on postgresql server 9.1, maybe be something doing with that? I'm moving far from syncml now, because i'm not thinking anything else related to that by now...

[Updated on: Tue, 04 September 2012 12:54]

Report message to a moderator

Re: Problem Starting Koneki with DM-Server 3.6 [message #908062 is a reply to message #907930] Tue, 04 September 2012 16:20 Go to previous messageGo to next message
Andre Tomas is currently offline Andre Tomas
Messages: 28
Registered: July 2012
Junior Member
Just another question. I'm trying to find where the Unmarshal is registered for SyncML1.2, on the server side, maybe i'm getting something wrongly done and this is never registered and thus can't be found during runtime?
Re: Problem Starting Koneki with DM-Server 3.6 [message #908068 is a reply to message #908062] Tue, 04 September 2012 16:35 Go to previous messageGo to next message
Benjamin Cabé is currently offline Benjamin Cabé
Messages: 151
Registered: July 2009
Location: Toulouse, France
Senior Member

Unfortunately I don't use the Funambol server on a daily basis... I hope Brandon can help you here... It seems that for him switching from Debian to Ubuntu did the trick ; maybe he can provide you with more accurate information on what needs to be put on the Ubuntu box... Confused
Re: Problem Starting Koneki with DM-Server 3.6 [message #908079 is a reply to message #908068] Tue, 04 September 2012 16:58 Go to previous messageGo to next message
Andre Tomas is currently offline Andre Tomas
Messages: 28
Registered: July 2012
Junior Member
Benjamin Cabe wrote on Tue, 04 September 2012 12:35
Unfortunately I don't use the Funambol server on a daily basis... I hope Brandon can help you here... It seems that for him switching from Debian to Ubuntu did the trick ; maybe he can provide you with more accurate information on what needs to be put on the Ubuntu box... Confused


I understand that, and appreciate the help you gave us so far. Thank you Smile

I'll hope he come here anytime soon and may detail a little better the ubuntu instalation in term of Java versions in use, and all o ther components need to run the DM-Server with koneki.
Re: Problem Starting Koneki with DM-Server 3.6 [message #908414 is a reply to message #897575] Wed, 05 September 2012 10:47 Go to previous messageGo to next message
Brandon F is currently offline Brandon F
Messages: 14
Registered: August 2012
Junior Member
Hello guys,

here all the information how I got it to work:

Software:
- Ubuntu: ubuntu-12.04.1-desktop-i386 (32 Bit) via ht*p://www.ubuntu.com/download/desktop/thank-you?distro=desktop&release=lts&bits=32
- VirtualBox 4.1.18 with NAT and port forwarding for 8080 (though this shouldn't be necessary until you use Eclipse in your host OS and Funambol on your guest OS)
- jBoss: jboss-5.1.0.GA-jdk6 via ht*p://sourceforge.net/projects/jboss/files/JBoss/JBoss-5.1.0.GA/jboss-5.1.0.GA-jdk6.zip/download (Personally I think maybe this is what causes the error, maybe you used jBoss without the JDK6?)
- PostgreSQL 9.1.5 via apt-get
- postgresql-9.1-902.jdbc3 via ht*p://jdbc.postgresql.org/download/postgresql-9.1-902.jdbc3.jar
- Java OpenJDK 1.6.0_24 via apt-get (so you don't need the Sun Java)
- Eclipse 3.7.2-1 (Indigo) via apt-get
- Koneki simulator 0.8 via Eclipse package manager and ht*p://download.eclipse.org/koneki/releases as repository
- Funambol from a thread in this forum

File system looks like this:
/home/brandon/funambol/Funambol/dm-server/<funambol content>
/home/brandon/funambol/Funambol/jboss-5.1.0.GA/<jboss content>
/home/brandon/funambol/Funambol/postgresql-9.1-902.jdbc3.jar

I have a PostgreSQL-user named funambol with password funambol who has full rights on the database called funambol.
You can check it by switching to the "postgres" linux user (with "sudo su postgres" in Ubuntu since I actually never set a password for this user...)
Then you start the command line tool with "psql" and type "\l". You should see a database named funambol with encoding UTF8 and access privileges for a user called funambol.
If there is something wrong I can provide you the commands you need to enter to create a user.

Path variables in /home/brandon/.profile:
export J2EE_HOME="/home/brandon/funambol/Funambol/jboss-5.1.0.GA/"
export JAVA_HOME="/usr/lib/jvm/java-6-openjdk-i386/"
export JBOSS_CLASSPATH="/home/brandon/funambol/Funambol/postgresql-9.1-902.jdbc3.jar"


You can test if they work with "echo $J2EE_HOME" in a shell. Rebuilding the .profile-file is done with "source .profile".

My install.properties file for Funambol looks like this:
# ==============================================================================

# Funambol Device Management Server

# ==============================================================================

# Installation properties

# ==============================================================================

# The server URI

server-name=ht*p://localhost:8080/funambol/dm

# The context path to use to access DM Server

context-path=/funambol

#

# The DBMS name. One of:

#   - ansisql99

#   - hypersonic

#   - mysql

#   - oracle

#   - postgresql

#   - sqlserver

#   - sybase

#   - db2

#

dbms=postgresql

#

# JDBC settings:

#   classpath: the classpath of the JDBC driver

#   url:       the url to access the database with the choosen JDBC driver

#   user:      the db user

#   password:  the user's password

#

#

# Hypersonic

# ==========

#

# jdbc.classpath=<somepath>/hsqldb.jar

# jdbc.driver=org.hsqldb.jdbcDriver

# jdbc.url=jdbc:hsqldb:hsql://<hostname>:1476

# jdbc.user=sa

# jdbc.password=

#

# PostgreSQL

# ==========

#

# jdbc.classpath=<somepath>/postgresql.jar

# jdbc.driver=org.postgresql.Driver

# jdbc.url=jdbc:postgresql://<hostname>/funambol

# jdbc.user=funambol

# jdbc.password=funambol

#

# MySQL

# =====

#

# jdbc.classpath=<somepath>/mysql-connector-java-3.0.8-stable-bin.jar

# jdbc.driver=com.mysql.jdbc.Driver

# jdbc.url=jdbc:mysql://[hostname][,failoverhost...][:port]/[dbname][?param1=value1][&param2=value2]

# jdbc.user=funambol

# jdbc.password=funambol

#

# ORACLE

# ==========

#

# jdbc.classpath=<somepath>/ojdbc14.jar

# jdbc.driver=oracle.jdbc.driver.OracleDriver

# jdbc.url=jdbc:oracle:thin:[@hostname][:<port1521>][:sid]

# jdbc.user=funambol

# jdbc.password=funambol

#

# Sybase

# ==========

#

# jdbc.classpath=

# jdbc.driver=com.sybase.jdbc.SybDriver

# jdbc.url=jdbc:sybase:Tds:host:port[/database]?property=value[?property=value] 

# jdbc.user=funambol

# jdbc.password=funambol

#

# SQL Server

# ==========

#

# jdbc.classpath=

# jdbc.driver=com.microsoft.jdbc.sqlserver.SQLServerDriver

# jdbc.url=jdbc:microsoft:sqlserver://localhost:1433;SelectMethod=Cursor

# jdbc.user=funambol

# jdbc.password=funambol

#

# DB2

# ==========

#

# jdbc.classpath=<somepath>/db2jcc_license_x.jar;<somepath>/db2jcc.jar

# jdbc.driver=com.ibm.db2.jcc.DB2Driver

# jdbc.url=jdbc:db2://[hostname][:<port50000>]/[dbname]

# jdbc.user=funambol

# jdbc.password=funambol

#

# ORACLE

# ==========

#

# jdbc.classpath=<somepath>/ojdbc14.jar

# jdbc.driver=oracle.jdbc.driver.OracleDriver

# jdbc.url=jdbc:oracle:thin:[@hostname][:<port1521>][:sid]

# jdbc.user=funambol

# jdbc.password=funambol

#

#

# THIS ONE BELOW !!!
jdbc.classpath=/home/brandon/funambol/Funambol/postgresql-9.1-902.jdbc3.jar
# THIS ONE ABOVE !!!

jdbc.driver=org.postgresql.Driver

jdbc.url=jdbc:postgresql://localhost/funambol

jdbc.user=funambol

jdbc.password=funambol


Be sure that the line discretely marked is correct in your file.

After starting the Funambol server and creating a new device called "device1" here ht*p://localhost:8080/dmdemo/ and adding a command like "get device details", connect with Koneki:
Server URI: ht*p://localhost:8080/funambol/dm
Server login: funambol
Server password: funambol
Device ID: device1 (remember to remove the "FREE:" or anything else in front of it after you used the creation guide).

That's it. I hope I didn't forget any information. If I did, feel free to ask, I'll try to look into this thread at least every day.

And sorry for masking all the links to ht*p but the forum doesn't trust me.

Regards

Brandon
Re: Problem Starting Koneki with DM-Server 3.6 [message #908433 is a reply to message #908414] Wed, 05 September 2012 11:33 Go to previous messageGo to next message
Benjamin Cabé is currently offline Benjamin Cabé
Messages: 151
Registered: July 2009
Location: Toulouse, France
Senior Member

Wow, great work Brandon thanks so much!
I think that pieces of this should probably be used to update the documentation on the wiki. We should try to do that when Andre will have figured out what was wrong on his installation.

BTW Brandon you can subscribe to the topic to get e-mail notifications when a new post arrives!

Benjamin.
Re: Problem Starting Koneki with DM-Server 3.6 [message #908609 is a reply to message #908433] Wed, 05 September 2012 16:30 Go to previous messageGo to next message
Andre Tomas is currently offline Andre Tomas
Messages: 28
Registered: July 2012
Junior Member
Hello, and thank you Brandon for your excellent post explaining every step of the way. But i'm out of luck for sure Sad I tried exactly as u wrote, step by step, using the same components in the same version. The OS is exactly the same, the virtual machine is VirtualBox 4.1.20 (can't be that), the java version is also the same installed trough apt-get aswell. The eclipse was installed via apt-get as well... Alcomponents are inside the virtual machine, altho the host syste is on 64bits, but the vm i insalled is the 32bit one. Everything "by the book" and still got that error message saying it has no unmarshaller for element {SYNCML:SYNCML1.2}SYNCML :S.

I'm so frustrated right now..

I don't understand much yet about unmarshaller elements, but i think they have to be in one specific document, is it possible that need document is missing from my installation by any reason?

I can also leave the debug messages given by the eclipse during the connection, it may help on something:

root@atomas-VirtualBox:/opt# 19:07:01.578 [pool-1-thread-1] DEBUG o.a.h.i.c.t.ThreadSafeClientConnManager - Get connection: ht*pRoute[{}->ht*p://localhost:8080], timeout = 0
19:07:01.608 [pool-1-thread-1] DEBUG o.a.h.i.conn.tsccm.ConnPoolByRoute - [ht*pRoute[{}->ht*p://localhost:8080]] total kept alive: 0, total issued: 0, total allocated: 0 out of 20
19:07:01.609 [pool-1-thread-1] DEBUG o.a.h.i.conn.tsccm.ConnPoolByRoute - No free connections [ht*pRoute[{}->ht*p://localhost:8080]][null]
19:07:01.610 [pool-1-thread-1] DEBUG o.a.h.i.conn.tsccm.ConnPoolByRoute - Available capacity: 2 out of 2 [ht*pRoute[{}->ht*p://localhost:8080]][null]
19:07:01.610 [pool-1-thread-1] DEBUG o.a.h.i.conn.tsccm.ConnPoolByRoute - Creating new connection [ht*pRoute[{}->ht*p://localhost:8080]]
19:07:01.674 [pool-1-thread-1] DEBUG o.a.h.i.c.DefaultClientConnectionOperator - Connecting to localhost/127.0.0.1:8080
19:07:01.791 [pool-1-thread-1] DEBUG o.a.h.c.protocol.RequestAddCookies - CookieSpec selected: best-match
19:07:01.940 [pool-1-thread-1] DEBUG o.a.h.impl.client.Defaultht*pClient - Attempt 1 to execute request
19:07:01.956 [pool-1-thread-1] DEBUG o.a.h.i.conn.DefaultClientConnection - Sending request: POST /funambol/dm ht*p/1.1
19:07:01.963 [pool-1-thread-1] DEBUG org.apache.ht*p.wire - >> "POST /funambol/dm ht*p/1.1[\r][\n]"
19:07:01.966 [pool-1-thread-1] DEBUG org.apache.ht*p.wire - >> "Transfer-Encoding: chunked[\r][\n]"
19:07:01.978 [pool-1-thread-1] DEBUG org.apache.ht*p.wire - >> "Content-Type: application/vnd.syncml.dm+xml[\r][\n]"
19:07:01.986 [pool-1-thread-1] DEBUG org.apache.ht*p.wire - >> "Content-Encoding: UTF-8[\r][\n]"
19:07:01.987 [pool-1-thread-1] DEBUG org.apache.ht*p.wire - >> "Host: localhost:8080[\r][\n]"
19:07:01.988 [pool-1-thread-1] DEBUG org.apache.ht*p.wire - >> "Connection: Keep-Alive[\r][\n]"
19:07:01.992 [pool-1-thread-1] DEBUG org.apache.ht*p.wire - >> "User-Agent: Apache-ht*pClient/4.1 (java 1.5)[\r][\n]"
19:07:01.993 [pool-1-thread-1] DEBUG org.apache.ht*p.wire - >> "[\r][\n]"
19:07:01.998 [pool-1-thread-1] DEBUG org.apache.ht*p.headers - >> POST /funambol/dm ht*p/1.1
19:07:01.998 [pool-1-thread-1] DEBUG org.apache.ht*p.headers - >> Transfer-Encoding: chunked
19:07:01.999 [pool-1-thread-1] DEBUG org.apache.ht*p.headers - >> Content-Type: application/vnd.syncml.dm+xml
19:07:01.999 [pool-1-thread-1] DEBUG org.apache.ht*p.headers - >> Content-Encoding: UTF-8
19:07:01.999 [pool-1-thread-1] DEBUG org.apache.ht*p.headers - >> Host: localhost:8080
19:07:02.000 [pool-1-thread-1] DEBUG org.apache.ht*p.headers - >> Connection: Keep-Alive
19:07:02.000 [pool-1-thread-1] DEBUG org.apache.ht*p.headers - >> User-Agent: Apache-ht*pClient/4.1 (java 1.5)
19:07:02.136 [pool-1-thread-1] DEBUG org.apache.ht*p.wire - >> "420[\r][\n]"
19:07:02.150 [pool-1-thread-1] DEBUG org.apache.ht*p.wire - >> "<?xml version="1.0" encoding="UTF-8"?><SyncML xmlns="SYNCML:SYNCML1.2"><SyncHdr><VerDTD>1.2</VerDTD><VerProto>DM/1.2</VerProto><SessionID>1</SessionID><MsgID>1</MsgID><Target><LocURI>ht*p://localhost:8080/funambol/dm</LocURI></Target><Source><LocURI>MyID</LocURI></Source><Cred><Meta><Format xmlns="syncml:metinf">b64</Format><Type xmlns="syncml:metinf">syncml:auth-basic</Type></Meta><Data>ZnVuYW1ib2w6ZnVuYW1ib2w=</Data></Cred></SyncHdr><SyncBody><Alert><CmdID>1</CmdID><Data>1201</Data></Alert><Replace><CmdID>2</CmdID><Meta><Format xmlns="syncml:metinf">chr</Format><Type xmlns="syncml:metinf">text/plain</Type></Meta><Item><Source><LocURI>./DevInfo/DevId</LocURI></Source><Data>MyID</Data></Item><Item><Source><LocURI>./DevInfo/DwV</LocURI></Source><Data></Data></Item><Item><Source><LocURI>./DevInfo/Man</LocURI></Source><Data>Samssung</Data></Item><Item><Source><LocURI>./DevInfo/Mod</LocURI></Source><Data>P-1000G</Data></Item><Item><Source><LocURI>./DevInfo/Lang</LocURI></Source><Data>PT</Data></Item></Replace><Final></Final></SyncBody></SyncML>"
19:07:02.155 [pool-1-thread-1] DEBUG org.apache.ht*p.wire - >> "[\r][\n]"
19:07:02.523 [pool-1-thread-1] DEBUG org.apache.ht*p.wire - >> "0[\r][\n]"
19:07:02.525 [pool-1-thread-1] DEBUG org.apache.ht*p.wire - >> "[\r][\n]"
19:07:03.388 [pool-1-thread-1] DEBUG org.apache.ht*p.wire - << "ht*p/1.1 500 Internal Server Error[\r][\n]"
19:07:03.407 [pool-1-thread-1] DEBUG org.apache.ht*p.wire - << "Server: Apache-Coyote/1.1[\r][\n]"
19:07:03.407 [pool-1-thread-1] DEBUG org.apache.ht*p.wire - << "Content-Type: text/html;charset=utf-8[\r][\n]"
19:07:03.408 [pool-1-thread-1] DEBUG org.apache.ht*p.wire - << "Transfer-Encoding: chunked[\r][\n]"
19:07:03.408 [pool-1-thread-1] DEBUG org.apache.ht*p.wire - << "Date: Wed, 05 Sep 2012 18:07:03 GMT[\r][\n]"
19:07:03.408 [pool-1-thread-1] DEBUG org.apache.ht*p.wire - << "Connection: close[\r][\n]"
19:07:03.408 [pool-1-thread-1] DEBUG org.apache.ht*p.wire - << "[\r][\n]"
19:07:03.410 [pool-1-thread-1] DEBUG o.a.h.i.conn.DefaultClientConnection - Receiving response: ht*p/1.1 500 Internal Server Error
19:07:03.410 [pool-1-thread-1] DEBUG org.apache.ht*p.headers - << ht*p/1.1 500 Internal Server Error
19:07:03.410 [pool-1-thread-1] DEBUG org.apache.ht*p.headers - << Server: Apache-Coyote/1.1
19:07:03.411 [pool-1-thread-1] DEBUG org.apache.ht*p.headers - << Content-Type: text/html;charset=utf-8
19:07:03.411 [pool-1-thread-1] DEBUG org.apache.ht*p.headers - << Transfer-Encoding: chunked
19:07:03.411 [pool-1-thread-1] DEBUG org.apache.ht*p.headers - << Date: Wed, 05 Sep 2012 18:07:03 GMT
19:07:03.411 [pool-1-thread-1] DEBUG org.apache.ht*p.headers - << Connection: close

[Updated on: Wed, 05 September 2012 18:14]

Report message to a moderator

Re: Problem Starting Koneki with DM-Server 3.6 [message #908654 is a reply to message #897575] Wed, 05 September 2012 18:34 Go to previous messageGo to next message
Brandon F is currently offline Brandon F
Messages: 14
Registered: August 2012
Junior Member
Hey,

I'm actually out of ideas now.
I uploaded my dm-server folder, my .profile file and an overview over all installed packages here:
h*tp://netload.in/datei934otcRlvI/dm-server.tar.bz2.htm

Unzip it with the command "tar xfvj dm-server.tar.bz2" if there is no GUI tool for that. You can create a list of all installed packages with "dpkg -l > packages.txt".

Remember to edit the .profile file and the file dm-server/install.properties. Maybe you should just copy all the files to the folder /home/USERNAME/funambol/Funambol.
So this folder should contain:
- the folder "dm-server" copied from my archieve
- the folder "jboss-5.1.0.GA", maybe you should download it again (remember, the -SDK version)
- the file "postgresql-9.1.902.jdbc3.jar"

Then you just have to edit the .profile and the dm-server/install.properties the way that you overwrite the word "USER" with your username. And maybe doublecheck the database account.

Oh and maybe you should check the rights on all the files and folders. If you don't care about the rights, I think a "chmod -R 777" on the folder funambol would definitely be worth a try!

When you did all of this and it won't work, I really have no clue how to help. If you have any ideas what you would like to check, let me know. My last idea would be a complete image of my VM, but this would be several gigabyte and with my internet connection it would take forever to upload.

Best of luck,

Brandon

P.S.: Oh and I doubt debugging the code is worth trying, in my opinion is a problem with the installation since I had the same problem and it got solved by choosing the right software environment.

[Updated on: Wed, 05 September 2012 18:38]

Report message to a moderator

Re: Problem Starting Koneki with DM-Server 3.6 [message #909075 is a reply to message #908654] Thu, 06 September 2012 13:45 Go to previous messageGo to next message
Andre Tomas is currently offline Andre Tomas
Messages: 28
Registered: July 2012
Junior Member
I've analised every packet comparing to Brandon F file. The based packets were the same, there were some codec packets and video ones that i didn't install same for language ones. I used the .profile file you gave me, btw, thank you for the time spent gathering the material, i've used your funambol server, changing only the install.properties, used my home folder exactly like you told me, checked the postgresql server, permissions, user and database, everything was ok. I also didn't forgot to change the files permissions i've used the chmod 777 as you recomended.
Downloaded again the Jboss with the -SDK and the postgresql obdc driver, run the install.sh jboss5, everything ok (build success), then start.sh and no problems i could see in the startup. Then, wehn i tried out connect with koneki, same error..


My biggest fear is missing something on the installation process of the server and because of that i'm getting this error :S

My last try will be do this on a new machine, install the ubuntu on a usb-stick with persistante changes and see what happens there.

Thank you again Brandon for you time, and thank you Benjamin for the start up help.

Anyway ill keep you posted till the end of day how it all went with this installation.

EDIT: Tell me something if you know, do the system go outside, onto the network search for a file or something like that on a specific port or protocol???

[Updated on: Thu, 06 September 2012 13:53]

Report message to a moderator

Re: Problem Starting Koneki with DM-Server 3.6 [message #909224 is a reply to message #909075] Thu, 06 September 2012 18:57 Go to previous messageGo to next message
Andre Tomas is currently offline Andre Tomas
Messages: 28
Registered: July 2012
Junior Member
I finally manage to get the funambol server communicate with the Koneki Smile
Not in Linux, i have no idea what so ever why, but in windows 7, i learn a lot with each try and noticed there were some ".cmd" files, then i thought the process should be the same, it was quite similar, but not totally equal, but its working now, and i can finally start to do domething good with it Smile

Again thank you guys for kept trying to help me and by doing so i didn't give up. Sad as to be on windows, but at least is working.
When i got some more time i'll try to understand why i couldn't install the server on linux.

Do you like me to post the changes need to put the server running on windows? (DM-Server, the koneki part is the same Smile )
Re: Problem Starting Koneki with DM-Server 3.6 [message #909471 is a reply to message #909075] Fri, 07 September 2012 07:48 Go to previous messageGo to next message
Brandon F is currently offline Brandon F
Messages: 14
Registered: August 2012
Junior Member
Hey,

Andre Tomas wrote on Thu, 06 September 2012 09:45

EDIT: Tell me something if you know, do the system go outside, onto the network search for a file or something like that on a specific port or protocol???


At least I didn't notice it, but since my virtual machine was only forwarding port 8080, I doubt something like that happened.

Anyway, congrats on getting it to work on Windows. If you rather want to use Linux (and if you want to give it one last try) I could install everything again myself and write down every step and command, like a walkthrough.
I just can't imagine why it wouldn't work when you use virtually the same software and configuration as me Very Happy

Regards

Brandon
Re: Problem Starting Koneki with DM-Server 3.6 [message #909482 is a reply to message #909471] Fri, 07 September 2012 08:07 Go to previous messageGo to next message
Benjamin Cabé is currently offline Benjamin Cabé
Messages: 151
Registered: July 2009
Location: Toulouse, France
Senior Member

Very cool, Andre, congrats! Smile

BTW guys, I'd be very interested in knowing more about what you are doing with OMA-DM, if you can share! Smile
Re: Problem Starting Koneki with DM-Server 3.6 [message #909551 is a reply to message #909471] Fri, 07 September 2012 10:17 Go to previous messageGo to next message
Andre Tomas is currently offline Andre Tomas
Messages: 28
Registered: July 2012
Junior Member
Brandon F wrote on Fri, 07 September 2012 03:48

...
If you rather want to use Linux (and if you want to give it one last try) I could install everything again myself and write down every step and command, like a walkthrough.
...


I think that's not a big priority for me, linux or windows, i just wanted to see the packages exchange and how some specific messages are built.
Thanks anyway, you already spend so much time with me.
But when i got some more free time, i really would like to try it one more time from a full clean Linux again and see if it works or not.

Benjamin Cabe wrote on Fri, 07 September 2012 04:07

BTW guys, I'd be very interested in knowing more about what you are doing with OMA-DM, if you can share!


I'm trying to build an ANDSF core so the operator can manage policies inside the mobile phone of the client. And so, ANDSF uses OMA-DM principle to exchange messages and sync and somethings more.. thats my project Smile

[Updated on: Fri, 07 September 2012 10:18]

Report message to a moderator

Re: Problem Starting Koneki with DM-Server 3.6 [message #910088 is a reply to message #909482] Sat, 08 September 2012 16:11 Go to previous messageGo to next message
Brandon F is currently offline Brandon F
Messages: 14
Registered: August 2012
Junior Member
Hey,
Benjamin Cabe wrote on Fri, 07 September 2012 04:07

BTW guys, I'd be very interested in knowing more about what you are doing with OMA-DM, if you can share! Smile

I'm working on a security analysis of OTA communication and OMA-DM is the theoretical part of my work. I use Koneki so I don't have to write all the XML structures by hand Smile

Regards

Brandon
Re: Problem Starting Koneki with DM-Server 3.6 [message #1020656 is a reply to message #910088] Mon, 18 March 2013 16:40 Go to previous messageGo to next message
welde tesfay is currently offline welde tesfay
Messages: 2
Registered: March 2013
Junior Member
Hi Andre,

I am trying to set up a Funambol-Koneki communication on windows 7 like you did for a similar purpose as yours. Would you please tell me how it worked for you?

I appreciate that.

Thanks in advance
Re: Problem Starting Koneki with DM-Server 3.6 [message #1029960 is a reply to message #897575] Sat, 30 March 2013 12:37 Go to previous messageGo to next message
Heeseok Kang is currently offline Heeseok Kang
Messages: 2
Registered: March 2013
Junior Member
The solution of "org.jibx.runtime.JiBXException" is simple.

You have to JIBX compile after finishing java file compile.

I have compiled Funambol DM Server ver 3.7 which I downloaded in "h*tp://en.sourceforge.jp/projects/okamoto/"

Okamoto Funambol DM Server 3.7 is tomcat server based and built by "ant".

If you look into "build.xml", you will find jibx compile task.

Good luck.
Re: Problem Starting Koneki with DM-Server 3.6 [message #1066984 is a reply to message #1029960] Fri, 05 July 2013 10:50 Go to previous messageGo to next message
Attila Heidrich is currently offline Attila Heidrich
Messages: 4
Registered: July 2013
Junior Member
We experience the same problem here as the others.

dm-server looks good, but the when connecting /funambol/dm we have the same error message.

The system is Ubuntu 13.04, I have tried Funambol versions:

3.5.1, bundled with hsql, java and jboss 3.2, no distribution-dependent component at all.

3.6 with jboss 4.1, and Sun Java 1.7

3.7 with tomcat7 and openjdk7

the result is the same for all... /dmdemo works fine, but /funambol/dm drops the "unsupported method" message.

Anyway, what should happen if I just open a browser and point to ht2p://localhost:8080/funambol/dm ?? 'cos now the error happens, but the guys developing the client reports the same error when connecting with the sample koneki client as well!
Re: Problem Starting Koneki with DM-Server 3.6 [message #1067631 is a reply to message #1066984] Tue, 09 July 2013 16:56 Go to previous messageGo to next message
Praveen - is currently offline Praveen -
Messages: 6
Registered: June 2013
Junior Member
H Brandon F,

I know this is a long shot, but by any chance have you gotten OTA to work with Koneki? I am trying to get it working right now, and am stuck. Any help would be much appreciated.

Thanks!
Re: Problem Starting Koneki with DM-Server 3.6 [message #1343183 is a reply to message #909551] Fri, 09 May 2014 07:07 Go to previous messageGo to next message
Brijesh Mistry is currently offline Brijesh Mistry
Messages: 2
Registered: May 2014
Junior Member
Hi Andre ,
I am also doing work on same.I installed DM server 3.7 .But my simulator is not able to connect with server.Please help me this.

I am also working on same project to push policies to (MO object ) to UE.Can you have any other server to test it (Guide) .

Thank you so much.
Re: Problem Starting Koneki with DM-Server 3.6 [message #1416607 is a reply to message #899513] Tue, 21 August 2012 17:45 Go to previous messageGo to next message
Andre Tomas is currently offline Andre Tomas
Messages: 28
Registered: July 2012
Junior Member
Julien Vermillard wrote on Wed, 01 August 2012 05:11
> The generated XML is fine for me. I suppose the problem is funambol.
> Yio uare sure your funambol path is correct ? 8080:/funambol/dm is for OMADM ?
>
> Please can you make a wireshark capture of the client/server communication ? The idea is to check in the HTTP content-type is correct.


Hello there, and thank you for your answer. Well i think the path is corrected, (this may sound newbie, but its kinda what i fell now), when i open the path 8080:/funambol/dm the browser gives me the follow message:

HTTP Status 405 - HTTP method GET is not supported by this URL

type Status report

message HTTP method GET is not supported by this URL

description The specified HTTP method is not allowed for the requested resource (HTTP method GET is not supported by this URL).
JBoss Web/2.1.2.G

Furthermore, the message was built, if i try to connect to any other place witch don't have any OMADM server running the Koneki "message" is not even built.

I'll send the wireshark file as soon as i get to the server.
Re: Problem Starting Koneki with DM-Server 3.6 [message #1416628 is a reply to message #905020] Wed, 29 August 2012 16:46 Go to previous messageGo to next message
Andre Tomas is currently offline Andre Tomas
Messages: 28
Registered: July 2012
Junior Member
Hello there and thank you for the quick responses :)

I had the same problem noted in that thread, but with some search i end up finding a version of the Dm-Server 3.6, but it may be modifed i don't know. Tomorrow i will try the version you posted here and give some feedback. Thank you :)
Re: Problem Starting Koneki with DM-Server 3.6 [message #1416629 is a reply to message #1416628] Wed, 29 August 2012 17:38 Go to previous messageGo to next message
Brandon F is currently offline Brandon F
Messages: 14
Registered: August 2012
Junior Member
Hey,
I changed from Debian to Ubuntu and everything works fine suddenly :)
I used exactly the same versions as stated in the guide, on Debian I used Postgresql 8 and JDBC v4, maybe that was the reason, but I'm not sure. But I used the DM server version which was linked in the thread above.
Anyway thank you for your help!

Best regards

Brandon
Re: Problem Starting Koneki with DM-Server 3.6 [message #1416630 is a reply to message #905104] Wed, 29 August 2012 17:57 Go to previous messageGo to next message
Eclipse User
Yeah, great news Brandon! :)
Looking forward to helping you again if need be!

Cheers,
Benjamin
Re: Problem Starting Koneki with DM-Server 3.6 [message #1416633 is a reply to message #1416630] Mon, 03 September 2012 15:57 Go to previous messageGo to next message
Andre Tomas is currently offline Andre Tomas
Messages: 28
Registered: July 2012
Junior Member
No luck on me, i used the server you linked on yhe other thread, but still got the exact same error... :( is it because i'm using an OpenSuse distribution?? I know they are different, but what differs form Ubuntu that's causing me to have this error??

Well, i'll install an Ubuntu virtual machine on one of my machines and try to connect Funambol with Koneki again and see if i got any luck.

Thanks a lot for all the suggestions.
Re: Problem Starting Koneki with DM-Server 3.6 [message #1416636 is a reply to message #1416633] Mon, 03 September 2012 16:40 Go to previous messageGo to next message
Eclipse User
Hi Andre,

What JRE version are you using? Maybe that where the difference can be between Ubuntu and the rest of the world?

Benjamin.
Re: Problem Starting Koneki with DM-Server 3.6 [message #1416642 is a reply to message #908068] Tue, 04 September 2012 16:58 Go to previous messageGo to previous message
Andre Tomas is currently offline Andre Tomas
Messages: 28
Registered: July 2012
Junior Member
Benjamin Cabe wrote on Tue, 04 September 2012 12:35
> Unfortunately I don't use the Funambol server on a daily basis... I hope Brandon can help you here... It seems that for him switching from Debian to Ubuntu did the trick ; maybe he can provide you with more accurate information on what needs to be put on the Ubuntu box... :?


I understand that, and appreciate the help you gave us so far. Thank you :)

I'll hope he come here anytime soon and may detail a little better the ubuntu instalation in term of Java versions in use, and all o ther components need to run the DM-Server with koneki.
Previous Topic:Missing dll
Next Topic:koneki OMA-DM client as a library on Android
Goto Forum:
  


Current Time: Thu Oct 30 13:52:06 GMT 2014

Powered by FUDForum. Page generated in 0.20778 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software