- SAP Community
- Products and Technology
- Technology
- Technology Q&A
- Syncronisation fails: Unexpected end of file from ...
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
Syncronisation fails: Unexpected end of file from server
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 05-31-2007 10:20 AM
Hey guys,
we work with MI 2.5.
We changed from SP15 to SP20.
But now the syncronisation doesn´t work.
The whole error message is:
• Synchronisation problems: Transport-layer (http) sync exception raised (root cause: cannot connect (java.net.SocketException: Unexpected end of file from server))
Does anyone have an idea about the problem?
Thanks & regards,
Barbara
- SAP Managed Tags:
- Mobile
Accepted Solutions (0)
Answers (8)
Answers (8)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Now I installed the SP13 on my PC, but the same problem occurs.
Any other idea?
The tracefile is attached:
Trace
[20070710 12:06:36:084] I [MI/API/Logging ] ***** LOG / TRACE SWITCHED ON
[20070710 12:06:36:084] I [MI/API/Logging ] ***** Mobile Engine version: MI 25 SP 13 Patch 02 Build 200508301427
[20070710 12:06:36:084] I [MI/API/Logging ] ***** Current timezone: Europe/Berlin
[20070710 12:06:36:100] I [MI ] Trace severity: All (1000)
[20070710 12:06:36:100] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:dispatch request to '/jsp/trace/trace.jsp'
[20070710 12:06:37:194] D [MI/Core ] Set current application to 'MOBILEENGINE_JSP'
[20070710 12:06:37:194] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:doGet(...) called
[20070710 12:06:37:194] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:getEvent() done with event name = ''
[20070710 12:06:37:194] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:dispatch request to '/jsp/trace/list.jsp'
[20070710 12:06:38:334] D [MI/Core ] Set current application to 'MOBILEENGINE_JSP'
[20070710 12:06:38:334] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:doGet(...) called
[20070710 12:06:38:334] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:getEvent() done with event name = ''
[20070710 12:06:38:334] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:dispatch request to '/jsp/home/home.jsp'
[20070710 12:06:39:334] D [MI/Core ] Set current application to 'MOBILEENGINE_JSP'
[20070710 12:06:39:334] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:doGet(...) called
[20070710 12:06:39:334] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:getEvent() done with event name = ''
[20070710 12:06:39:334] P [MI/Sync ] Notify R3 called
[20070710 12:06:39:334] D [MI/Sync ] There is already a container for method WAF_REGISTRY and user FALTERMEIERB in the outbound queue
[20070710 12:06:39:334] D [MI/API/Services ] MEResourceBundle:Constructor: Create MEResourceBundle(com/sap/ip/me/awtapps/home/mobile_engine, de_DE, (null))
[20070710 12:06:39:334] D [MI/API/Services ] MEResourceBundle:Constructor: Use classloader com.sap.ip.me.core.Startup@1e63e3d
[20070710 12:06:39:334] D [MI/API/Services ] CREATED MEPropertyResourceBundle com.sap.ip.me.api.services.MEResourceBundle$MEPropertyResourceBundle@106fc94 for bundleName: com/sap/ip/me/awtapps/home/mobile_engine with Locale: _de
[20070710 12:06:39:350] D [MI/API/Services ] CREATED parent MEPropertyResourceBundle for child bundle: com.sap.ip.me.api.services.MEResourceBundle$MEPropertyResourceBundle@106fc94 using bundle name: com/sap/ip/me/awtapps/home/mobile_engine
[20070710 12:06:39:350] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:dispatch request to '/jsp/home/home.jsp'
[20070710 12:06:39:366] I [MI/Sync ] Synchronize with backend called, Thread=Thread-26
[20070710 12:06:39:366] I [MI/Sync ] Thread=Thread-26 took lock for synchronization.
[20070710 12:06:39:366] P [MI/Sync ] Use following gateway for synchronization: http://132.247.222.59:8049
[20070710 12:06:39:366] D [MI/Sync ] Synchronisation: Fire SyncEvent 0
[20070710 12:06:39:366] D [MI/API/Sync ] SyncEvent com.sap.ip.me.api.sync.SyncEvent[source=com.sap.ip.me.sync.SyncManagerMerger@147c1db] skipped for User because he has not been installed on MW.
[20070710 12:06:39:366] D [MI/API/Sync ] SyncEvent com.sap.ip.me.api.sync.SyncEvent[source=com.sap.ip.me.sync.SyncManagerMerger@147c1db] skipped for User because he has not been installed on MW.
[20070710 12:06:39:366] D [MI/API/Sync ] SyncEvent com.sap.ip.me.api.sync.SyncEvent[source=com.sap.ip.me.sync.SyncManagerMerger@147c1db] skipped for User because he has not been installed on MW.
[20070710 12:06:39:366] D [MI/API/Sync ] SyncEvent com.sap.ip.me.api.sync.SyncEvent[source=com.sap.ip.me.sync.SyncManagerMerger@147c1db] skipped for User because he has not been installed on MW.
[20070710 12:06:39:366] D [MI/API/Sync ] SyncEvent com.sap.ip.me.api.sync.SyncEvent[source=com.sap.ip.me.sync.SyncManagerMerger@147c1db] skipped for User because he has not been installed on MW.
[20070710 12:06:39:366] P [MI/Sync ] Repetitive sync is turned off
[20070710 12:06:39:366] P [MI/Sync ] Synchronization started for user (SHARED)
[20070710 12:06:39:366] D [MI/Sync ] PackageManager: old package file c:\Programme\SAP Mobile Infrastructure\sync\(SHARED)\out\package.out could not be deleted
[20070710 12:06:39:366] D [MI/Sync ] PackageManager: create package with maximum 2147483647 items
[20070710 12:06:39:366] D [MI/Sync ] PackageManager: filled package with 0 acknowledge received container(s)
[20070710 12:06:39:381] D [MI/Sync ] PackageManager: filled package with 0 acknowledge container(s)
[20070710 12:06:39:381] D [MI/Sync ] PackageManager: filled package with 0 container items or headers
[20070710 12:06:39:381] D [MI/Sync ] PackageManager: filled package with 1 notify container(s)
[20070710 12:06:39:381] D [MI/Sync ] Package file c:\Programme\SAP Mobile Infrastructure\sync\(SHARED)\out\package.out exists and can be read
[20070710 12:06:39:381] P [MI/Sync ] Synchronisation started
[20070710 12:06:39:381] D [MI/Sync ] Begin: Dumping file c:\Programme\SAP Mobile Infrastructure\sync\(SHARED)\out\package.out
MISYNC0x1251300
0113b0062615fe263dbb
N
-1
NEW_PROTOCOL
0
-1
0
-1
-1
[20070710 12:06:39:381] D [MI/Sync ] End: Dumping file c:\Programme\SAP Mobile Infrastructure\sync\(SHARED)\out\package.out
[20070710 12:06:39:381] I [MI/Sync ] Outbound file size for user (SHARED) is 92
[20070710 12:06:39:381] P [MI/Sync ] Do not use http proxy (system properties update)
[20070710 12:06:39:397] P [MI/Sync ] Use following gateway for synchronization: http://132.247.222.59:8049
[20070710 12:06:39:397] I [MI/Sync ] GzipDataCompression: Gzip data compression is switched on
[20070710 12:06:49:397] D [MI/Core ] Set current application to 'MOBILEENGINE_JSP'
[20070710 12:06:49:397] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:doGet(...) called
[20070710 12:06:49:397] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:getEvent() done with event name = ''
[20070710 12:06:49:397] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:dispatch request to '/jsp/home/home.jsp'
[20070710 12:06:59:445] D [MI/Core ] Set current application to 'MOBILEENGINE_JSP'
[20070710 12:06:59:445] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:doGet(...) called
[20070710 12:06:59:445] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:getEvent() done with event name = ''
[20070710 12:06:59:445] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:dispatch request to '/jsp/home/home.jsp'
[20070710 12:07:02:304] A [MI/Sync ] HttpSynchronizer caught exception java.net.ConnectException: Connection timed out: connect
java.net.ConnectException: Connection timed out: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
at java.net.Socket.connect(Socket.java:461)
at java.net.Socket.connect(Socket.java:411)
at sun.net.NetworkClient.doConnect(NetworkClient.java:139)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:402)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:618)
at sun.net.www.http.HttpClient.(HttpClient.java:306)
at sun.net.www.http.HttpClient.(HttpClient.java:267)
at sun.net.www.http.HttpClient.New(HttpClient.java:339)
at sun.net.www.http.HttpClient.New(HttpClient.java:320)
at sun.net.www.http.HttpClient.New(HttpClient.java:315)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:521)
at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:498)
at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:569)
at com.sap.ip.me.sync.HTTPSynchronizer.synchronize(HTTPSynchronizer.java:234)
at com.sap.ip.me.sync.HTTPSynchronizer.synchronize(HTTPSynchronizer.java:376)
at com.sap.ip.me.sync.HTTPSynchronizer.exchangeData(HTTPSynchronizer.java:71)
at com.sap.ip.me.sync.SyncManagerImpl.processSyncCycle(SyncManagerImpl.java:691)
at com.sap.ip.me.sync.SyncManagerImpl.syncForUser(SyncManagerImpl.java:1142)
at com.sap.ip.me.sync.SyncManagerImpl.processSynchronization(SyncManagerImpl.java:770)
at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend(SyncManagerImpl.java:402)
at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend(SyncManagerImpl.java:285)
at com.sap.ip.me.api.sync.SyncManager.synchronizeWithBackend(SyncManager.java:79)
at com.sap.ip.me.apps.jsp.Home$SyncRunnable.run(Home.java:447)
at java.lang.Thread.run(Thread.java:534)
[20070710 12:07:02:304] E [MI/Sync ] Exception while synchronizing via http
com.sap.ip.me.api.services.HttpConnectionException: Exception while synchronizing (java.net.ConnectException: Connection timed out: connect)
at com.sap.ip.me.sync.HTTPSynchronizer.synchronize(HTTPSynchronizer.java:312)
at com.sap.ip.me.sync.HTTPSynchronizer.synchronize(HTTPSynchronizer.java:376)
at com.sap.ip.me.sync.HTTPSynchronizer.exchangeData(HTTPSynchronizer.java:71)
at com.sap.ip.me.sync.SyncManagerImpl.processSyncCycle(SyncManagerImpl.java:691)
at com.sap.ip.me.sync.SyncManagerImpl.syncForUser(SyncManagerImpl.java:1142)
at com.sap.ip.me.sync.SyncManagerImpl.processSynchronization(SyncManagerImpl.java:770)
at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend(SyncManagerImpl.java:402)
at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend(SyncManagerImpl.java:285)
at com.sap.ip.me.api.sync.SyncManager.synchronizeWithBackend(SyncManager.java:79)
at com.sap.ip.me.apps.jsp.Home$SyncRunnable.run(Home.java:447)
at java.lang.Thread.run(Thread.java:534)
[20070710 12:07:02:304] P [MI/Core ] original context restored
[20070710 12:07:02:304] W [MI/Sync ] Synchronisation problems
com.sap.ip.me.api.sync.SyncException: Transport-layer (http) sync exception raised (root cause: Exception while synchronizing (java.net.ConnectException: Connection timed out: connect))
at com.sap.ip.me.sync.HTTPSynchronizer.exchangeData(HTTPSynchronizer.java:80)
at com.sap.ip.me.sync.SyncManagerImpl.processSyncCycle(SyncManagerImpl.java:691)
at com.sap.ip.me.sync.SyncManagerImpl.syncForUser(SyncManagerImpl.java:1142)
at com.sap.ip.me.sync.SyncManagerImpl.processSynchronization(SyncManagerImpl.java:770)
at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend(SyncManagerImpl.java:402)
at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend(SyncManagerImpl.java:285)
at com.sap.ip.me.api.sync.SyncManager.synchronizeWithBackend(SyncManager.java:79)
at com.sap.ip.me.apps.jsp.Home$SyncRunnable.run(Home.java:447)
at java.lang.Thread.run(Thread.java:534)
[20070710 12:07:02:304] D [MI/Sync ] Synchronisation: Fire SyncEvent 1
[20070710 12:07:02:304] P [MI/Core ] Thread Thread-26 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)
[20070710 12:07:02:304] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.services.os.AgentManager$AgentSyncEventListener on ConversationId MI2853484152454429
[20070710 12:07:02:304] P [MI/Core ] original context restored
[20070710 12:07:02:304] P [MI/Core ] Thread Thread-26 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)
[20070710 12:07:02:304] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.sync.LogSender on ConversationId MI2853484152454429
[20070710 12:07:02:304] P [MI/Core ] original context restored
[20070710 12:07:02:304] P [MI/Core ] Thread Thread-26 switched context to MI46414c5445524d4549455242 / MI46414c5445524d4549455242 (User: FALTERMEIERB, MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)
[20070710 12:07:02:304] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.core.StatusUpdater on ConversationId MI46414c5445524d4549455242
[20070710 12:07:02:304] P [MI/Core ] original context restored
[20070710 12:07:02:304] P [MI/Core ] Thread Thread-26 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)
[20070710 12:07:02:304] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.ccms.LastSuccessfulSyncAlert on ConversationId MI2853484152454429
[20070710 12:07:02:304] P [MI/Core ] original context restored
[20070710 12:07:02:304] P [MI/Core ] Thread Thread-26 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)
[20070710 12:07:02:304] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.ccms.AlertManagerImpl on ConversationId MI2853484152454429
[20070710 12:07:02:304] P [MI/Core ] original context restored
[20070710 12:07:02:304] I [MI/Sync ] Synchronization finished, Thread=Thread-26
[20070710 12:07:09:492] D [MI/Core ] Set current application to 'MOBILEENGINE_JSP'
[20070710 12:07:09:492] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:doGet(...) called
[20070710 12:07:09:492] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:getEvent() done with event name = ''
[20070710 12:07:09:492] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:dispatch request to '/jsp/home/synclog.jsp'
[20070710 12:07:19:961] D [MI/Core ] Set current application to 'MOBILEENGINE_JSP'
[20070710 12:07:19:961] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:doGet(...) called
[20070710 12:07:19:961] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:getEvent() done with event name = ''
[20070710 12:07:19:961] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:dispatch request to '/jsp/home/home.jsp'
[20070710 12:07:20:930] D [MI/Core ] Set current application to 'MOBILEENGINE_JSP'
[20070710 12:07:20:930] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:doGet(...) called
[20070710 12:07:20:930] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:getEvent() done with event name = ''
[20070710 12:07:20:930] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:dispatch request to '/jsp/trace/trace.jsp'
[20070710 12:07:22:164] D [MI/Core ] Set current application to 'MOBILEENGINE_JSP'
[20070710 12:07:22:164] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:doGet(...) called
[20070710 12:07:22:164] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:getEvent() done with event name = ''
Regards,
Barbara
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Lakshmi,
the user is the same for the client and the middleware.
GUI-Login is possible, too.
Regards,
Barbara
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Barbara,
Have you logged in to the client with the same user which you used to log in to middleware?
You log says :- User has not been installed on MW, its not ready for sync
(User: FALTERMEIERB, MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)
[20070612 11:58:07:068] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.smartsync.core.SmartSyncRuntimeManager
[20070612 11:58:07:068] D [MI/Smartsync ] <b>User has not been installed on MW, it is not ready for sync :FALTERMEIERB</b> [20070612 11:58:07:068] P [MI/Core ] original context restored
Best Regards,
Lakshmi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hello Nameeta,
I use the SyncServlet to syncronise.
Regards,
Barbara
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hello Lakshmi,
I still have the same problem:
Synchronisation problems: Transport-layer (http) sync exception raised (root cause: Exception while synchronizing (java.net.ConnectException: Connection timed out: connect))
Well, I know it´s quiet long, but perhaps anyone finds another mistake:
20070612 11:58:03:318] I ***** LOG / TRACE SWITCHED ON
I ***** Mobile Engine version: MI 25 SP 09 Patch 00 Build 200409101427
I ***** Current timezone: Europe/Berlin
D AbstractMEHttpServlet:dispatch request to '/jsp/trace/trace.jsp'
D Set current application to 'MOBILEENGINE_JSP'
D AbstractMEHttpServlet:doGet(...) called
D AbstractMEHttpServlet:getEvent() done with event name = ''
D AbstractMEHttpServlet:dispatch request to '/jsp/trace/list.jsp'
D Set current application to 'MOBILEENGINE_JSP'
D AbstractMEHttpServlet:doGet(...) called
D AbstractMEHttpServlet:getEvent() done with event name = ''
D AbstractMEHttpServlet:dispatch request to '/jsp/home/home.jsp'
D Set current application to 'MOBILEENGINE_JSP'
D AbstractMEHttpServlet:doGet(...) called
D AbstractMEHttpServlet:getEvent() done with event name = ''
D There is already a container for method WAF_REGISTRY and user FALTERMEIERB in the outbound queue
D MEResourceBundle:Constructor: Create MEResourceBundle(com/sap/ip/me/awtapps/home/mobile_engine, de_DE, (null))
D MEResourceBundle:Constructor: Use classloader com.sap.ip.me.core.Startup@15ff48b
D CREATED MEPropertyResourceBundle com.sap.ip.me.api.services.MEResourceBundle$MEPropertyResourceBundle@14db0e3 for bundleName: com/sap/ip/me/awtapps/home/mobile_engine with Locale: _de
I Synchronize with backend called, Thread=Thread-25
I Thread=Thread-25 took lock for synchronizeation.
D Synchronisation: Fire SyncEvent 0
P Thread Thread-25 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)
I SyncEvent Performing com.sap.ip.me.ccms.LastSuccessfulSyncAlert
P Thread Thread-25 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)
I SyncEvent Performing com.sap.ip.me.ccms.AlertManager
D CREATED parent MEPropertyResourceBundle for child bundle: com.sap.ip.me.api.services.MEResourceBundle$MEPropertyResourceBundle@14db0e3 using bundle name: com/sap/ip/me/awtapps/home/mobile_engine
P Thread Thread-25 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)
D AbstractMEHttpServlet:dispatch request to '/jsp/home/home.jsp'
I SyncEvent Performing com.sap.ip.me.services.os.AgentManager
P Created outbound container for user (SHARED) and method AGENT_PARAMETERS
P Thread Thread-25 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)
I SyncEvent Performing com.sap.ip.me.sync.LogSender
P Thread Thread-25 switched context to MI46414c5445524d4549455242 / MI46414c5445524d4549455242 (User: FALTERMEIERB, MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)
I SyncEvent Performing com.sap.ip.me.smartsync.core.SmartSyncRuntimeManager
D User has not been installed on MW, it is not ready for sync :FALTERMEIERB
P Thread Thread-25 switched context to MI46414c5445524d4549455242 / MI46414c5445524d4549455242 (User: FALTERMEIERB, MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)
I SyncEvent Performing com.sap.ip.me.apps.jsp.SyncStatus
P Thread Thread-25 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)
I SyncEvent Performing com.sap.ip.me.core.StatusUpdater
P Synchronization started for user (SHARED)
D PackageManager: old package file c:ProgrammeSAP Mobile Infrastructuresync(SHARED)outpackage.out was successfully deleted
D PackageManager: create package with maximum 2147483647 items
D PackageManager: filled package with 0 acknowledge received container(s)
D PackageManager: filled package with 0 acknowledge container(s)
D PackageManager: filled package with 144 container items or headers
D PackageManager: filled package with 1 notify container(s)
D Package file c:ProgrammeSAP Mobile Infrastructuresync(SHARED)outpackage.out exists and can be read
D Dumping file 'c:ProgrammeSAP Mobile Infrastructuresync(SHARED)outpackage.out'
INH-H[1]=01131e47abb8116463af;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[1]=01131e47abb8116463af;TIMESTAMP;0;000000;19700101&INB-B[2]=01131e47abb8116463af;DEVICEID;0;&INB-B[3]=01131e47abb8116463af;USER;0;FALTERMEIERB&INH-H[2]=01131e4817a3386ac60f;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[4]=01131e4817a3386ac60f;TIMESTAMP;0;000000;19700101&INB-B[5]=01131e4817a3386ac60f;DEVICEID;0;&INB-B[6]=01131e4817a3386ac60f;USER;0;FALTERMEIERB&INH-H[3]=01131e56593096910fb0;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[7]=01131e56593096910fb0;TIMESTAMP;0;000000;19700101&INB-B[8]=01131e56593096910fb0;DEVICEID;0;&INB-B[9]=01131e56593096910fb0;USER;0;FALTERMEIERB&INH-H[4]=01131e57c46ca636ded3;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[10]=01131e57c46ca636ded3;TIMESTAMP;0;000000;19700101&INB-B[11]=01131e57c46ca636ded3;DEVICEID;0;&INB-B[12]=01131e57c46ca636ded3;USER;0;INVENTUR&INH-H[5]=01131e590106948d9c02;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[13]=01131e590106948d9c02;TIMESTAMP;0;000000;19700101&INB-B[14]=01131e590106948d9c02;DEVICEID;0;&INB-B[15]=01131e590106948d9c02;USER;0;INVENTUR&INH-H[6]=01131e5c82a45b1f9b77;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[16]=01131e5c82a45b1f9b77;TIMESTAMP;0;000000;19700101&INB-B[17]=01131e5c82a45b1f9b77;DEVICEID;0;&INB-B[18]=01131e5c82a45b1f9b77;USER;0;INVENTUR&INH-H[7]=01131e5d3404764f7ea1;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[19]=01131e5d3404764f7ea1;TIMESTAMP;0;000000;19700101&INB-B[20]=01131e5d3404764f7ea1;DEVICEID;0;&INB-B[21]=01131e5d3404764f7ea1;USER;0;INVENTUR&INH-H[8]=01131e5ec3c0895614f7;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[22]=01131e5ec3c0895614f7;TIMESTAMP;0;000000;19700101&INB-B[23]=01131e5ec3c0895614f7;DEVICEID;0;&INB-B[24]=01131e5ec3c0895614f7;USER;0;INVENTUR&INH-H[9]=01131e64f18a81be5bc3;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[25]=01131e64f18a81be5bc3;TIMESTAMP;0;000000;19700101&INB-B[26]=01131e64f18a81be5bc3;DEVICEID;0;&INB-B[27]=01131e64f18a81be5bc3;USER;0;FALTERMEIERB&INH-H[10]=01131e6f7de68fb520e3;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[28]=01131e6f7de68fb520e3;TIMESTAMP;0;000000;19700101&INB-B[29]=01131e6f7de68fb520e3;DEVICEID;0;&INB-B[30]=01131e6f7de68fb520e3;USER;0;FALTERMEIERB&INH-H[11]=01131e766cee9af72b4e;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[31]=01131e766cee9af72b4e;TIMESTAMP;0;000000;19700101&INB-B[32]=01131e766cee9af72b4e;DEVICEID;0;&INB-B[33]=01131e766cee9af72b4e;USER;0;FALTERMEIERB&INH-H[12]=01131e7d2bae445e3a3f;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[34]=01131e7d2bae445e3a3f;TIMESTAMP;0;000000;19700101&INB-B[35]=01131e7d2bae445e3a3f;DEVICEID;0;&INB-B[36]=01131e7d2bae445e3a3f;USER;0;FALTERMEIERB&INH-H[13]=01131e7e1054feecb208;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[37]=01131e7e1054feecb208;TIMESTAMP;0;000000;19700101&INB-B[38]=01131e7e1054feecb208;DEVICEID;0;&INB-B[39]=01131e7e1054feecb208;USER;0;FALTERMEIERB&INH-H[14]=01131e838cddb4153c03;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[40]=01131e838cddb4153c03;TIMESTAMP;0;000000;19700101&INB-B[41]=01131e838cddb4153c03;DEVICEID;0;&INB-B[42]=01131e838cddb4153c03;USER;0;FALTERMEIERB&INH-H[15]=01131e841d66d05bc7c8;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[43]=01131e841d66d05bc7c8;TIMESTAMP;0;000000;19700101&INB-B[44]=01131e841d66d05bc7c8;DEVICEID;0;&INB-B[45]=01131e841d66d05bc7c8;USER;0;FALTERMEIERB&INH-H[16]=01131e8a71173a68eb9c;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[46]=01131e8a71173a68eb9c;TIMESTAMP;0;000000;19700101&INB-B[47]=01131e8a71173a68eb9c;DEVICEID;0;&INB-B[48]=01131e8a71173a68eb9c;USER;0;FALTERMEIERB&INH-H[17]=01131e8b04506c0e5828;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[49]=01131e8b04506c0e5828;TIMESTAMP;0;000000;19700101&INB-B[50]=01131e8b04506c0e5828;DEVICEID;0;&INB-B[51]=01131e8b04506c0e5828;USER;0;FALTERMEIERB&INH-H[18]=01131e8bfc205172536c;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[52]=01131e8bfc205172536c;TIMESTAMP;0;000000;19700101&INB-B[53]=01131e8bfc205172536c;DEVICEID;0;&INB-B[54]=01131e8bfc205172536c;USER;0;FALTERMEIERB&INH-H[19]=01131e932b00cb836ef4;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[55]=01131e932b00cb836ef4;TIMESTAMP;0;000000;19700101&INB-B[56]=01131e932b00cb836ef4;DEVICEID;0;&INB-B[57]=01131e932b00cb836ef4;USER;0;FALTERMEIERB&INH-H[20]=01131ebb152bc734ed47;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[58]=01131ebb152bc734ed47;TIMESTAMP;0;000000;19700101&INB-B[59]=01131ebb152bc734ed47;DEVICEID;0;&INB-B[60]=01131ebb152bc734ed47;USER;0;FALTERMEIERB&INH-H[21]=01131ebb93a38e178aa7;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[61]=01131ebb93a38e178aa7;TIMESTAMP;0;000000;19700101&INB-B[62]=01131ebb93a38e178aa7;DEVICEID;0;&INB-B[63]=01131ebb93a38e178aa7;USER;0;FALTERMEIERB&INH-H[22]=01131f925bf0fde99cf6;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[64]=01131f925bf0fde99cf6;TIMESTAMP;0;000000;19700101&INB-B[65]=01131f925bf0fde99cf6;DEVICEID;0;&INB-B[66]=01131f925bf0fde99cf6;USER;0;FALTERMEIERB&INH-H[23]=01131f930c669ef4bef4;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[67]=01131f930c669ef4bef4;TIMESTAMP;0;000000;19700101&INB-B[68]=01131f930c669ef4bef4;DEVICEID;0;&INB-B[69]=01131f930c669ef4bef4;USER;0;FALTERMEIERB&INH-H[24]=01131fa83a227bbe7ab3;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[70]=01131fa83a227bbe7ab3;TIMESTAMP;0;000000;19700101&INB-B[71]=01131fa83a227bbe7ab3;DEVICEID;0;&INB-B[72]=01131fa83a227bbe7ab3;USER;0;FALTERMEIERB&INH-H[25]=01131fa98cb83af4a744;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[73]=01131fa98cb83af4a744;TIMESTAMP;0;000000;19700101&INB-B[74]=01131fa98cb83af4a744;DEVICEID;0;&INB-B[75]=01131fa98cb83af4a744;USER;0;FALTERMEIERB&INH-H[26]=01131fac31e255d56db1;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[76]=01131fac31e255d56db1;TIMESTAMP;0;000000;19700101&INB-B[77]=01131fac31e255d56db1;DEVICEID;0;&INB-B[78]=01131fac31e255d56db1;USER;0;FALTERMEIERB&INH-H[27]=01131fb44e0294de2930;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[79]=01131fb44e0294de2930;TIMESTAMP;0;000000;19700101&INB-B[80]=01131fb44e0294de2930;DEVICEID;0;&INB-B[81]=01131fb44e0294de2930;USER;0;INVENTUR&INH-H[28]=01131fb4f939f18b9695;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[82]=01131fb4f939f18b9695;TIMESTAMP;0;000000;19700101&INB-B[83]=01131fb4f939f18b9695;DEVICEID;0;&INB-B[84]=01131fb4f939f18b9695;USER;0;INVENTUR&INH-H[29]=01131fb7104af9a90707;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[85]=01131fb7104af9a90707;TIMESTAMP;0;000000;19700101&INB-B[86]=01131fb7104af9a90707;DEVICEID;0;&INB-B[87]=01131fb7104af9a90707;USER;0;INVENTUR&INH-H[30]=01131fb7781e2e5389f7;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[88]=01131fb7781e2e5389f7;TIMESTAMP;0;000000;19700101&INB-B[89]=01131fb7781e2e5389f7;DEVICEID;0;&INB-B[90]=01131fb7781e2e5389f7;USER;0;INVENTUR&INH-H[31]=01131fbc8914caa9f925;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[91]=01131fbc8914caa9f925;TIMESTAMP;0;000000;19700101&INB-B[92]=01131fbc8914caa9f925;DEVICEID;0;&INB-B[93]=01131fbc8914caa9f925;USER;0;FALTERMEIERB&INH-H[32]=01131fbd94bb9bb7002f;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[94]=01131fbd94bb9bb7002f;TIMESTAMP;0;000000;19700101&INB-B[95]=01131fbd94bb9bb7002f;DEVICEID;0;&INB-B[96]=01131fbd94bb9bb7002f;USER;0;FALTERMEIERB&INH-H[33]=01131fc354d0da4c4523;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[97]=01131fc354d0da4c4523;TIMESTAMP;0;000000;19700101&INB-B[98]=01131fc354d0da4c4523;DEVICEID;0;&INB-B[99]=01131fc354d0da4c4523;USER;0;FALTERMEIERB&INH-H[34]=01131fc42ad027e29895;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[100]=01131fc42ad027e29895;TIMESTAMP;0;000000;19700101&INB-B[101]=01131fc42ad027e29895;DEVICEID;0;&INB-B[102]=01131fc42ad027e29895;USER;0;FALTERMEIERB&INH-H[35]=01131fca00bf365ff575;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[103]=01131fca00bf365ff575;TIMESTAMP;0;000000;19700101&INB-B[104]=01131fca00bf365ff575;DEVICEID;0;&INB-B[105]=01131fca00bf365ff575;USER;0;FALTERMEIERB&INH-H[36]=01131fcc44cc84adfd4b;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[106]=01131fcc44cc84adfd4b;TIMESTAMP;0;000000;19700101&INB-B[107]=01131fcc44cc84adfd4b;DEVICEID;0;&INB-B[108]=01131fcc44cc84adfd4b;USER;0;FALTERMEIERB&INH-H[37]=01131fcc450bcb0fc19d;;N;;;;;;NEW_PROTOCOL;;0;;0;;&
D End of content of file 'c:ProgrammeSAP Mobile Infrastructuresync(SHARED)outpackage.out'
P Do not use http proxy (system properties update)
I GzipDataCompression: Gzip data compression is switched off
P Sending outbound file to server.
D Set current application to 'MOBILEENGINE_JSP'
D AbstractMEHttpServlet:doGet(...) called
D AbstractMEHttpServlet:getEvent() done with event name = ''
D AbstractMEHttpServlet:dispatch request to '/jsp/home/home.jsp'
D Set current application to 'MOBILEENGINE_JSP'
D AbstractMEHttpServlet:doGet(...) called
D AbstractMEHttpServlet:getEvent() done with event name = ''
D AbstractMEHttpServlet:dispatch request to '/jsp/home/home.jsp'
A HttpSynchronizer caught exception java.net.ConnectException: Connection timed out: connect
java.net.ConnectException: Connection timed out: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
at java.net.Socket.connect(Socket.java:461)
at java.net.Socket.connect(Socket.java:411)
at sun.net.NetworkClient.doConnect(NetworkClient.java:139)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:402)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:618)
at sun.net.www.http.HttpClient.(HttpClient.java:306)
at sun.net.www.http.HttpClient.(HttpClient.java:267)
at sun.net.www.http.HttpClient.New(HttpClient.java:339)
at sun.net.www.http.HttpClient.New(HttpClient.java:320)
at sun.net.www.http.HttpClient.New(HttpClient.java:315)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:521)
at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:498)
at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:569)
at com.sap.ip.me.sync.HTTPSynchronizer.synchronize(HTTPSynchronizer.java:301)
at com.sap.ip.me.sync.HTTPSynchronizer.synchronize(HTTPSynchronizer.java:190)
at com.sap.ip.me.sync.HTTPSynchronizer.exchangeData(HTTPSynchronizer.java:67)
at com.sap.ip.me.sync.SyncManagerImplNewProtocol.processSyncCycle(SyncManagerImplNewProtocol.java:147)
at com.sap.ip.me.sync.SyncManagerImpl.syncForUser(SyncManagerImpl.java:909)
at com.sap.ip.me.sync.SyncManagerImpl.processSynchronization(SyncManagerImpl.java:460)
at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend(SyncManagerImpl.java:274)
at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend(SyncManagerImpl.java:191)
at com.sap.ip.me.api.sync.SyncManager.synchronizeWithBackend(SyncManager.java:71)
at com.sap.ip.me.apps.jsp.Home$SyncRunnable.run(Home.java:443)
at java.lang.Thread.run(Thread.java:534)
E Exception while synchronizing via http
com.sap.ip.me.api.services.HttpConnectionException: Exception while synchronizing (java.net.ConnectException: Connection timed out: connect)
at com.sap.ip.me.sync.HTTPSynchronizer.synchronize(HTTPSynchronizer.java:342)
at com.sap.ip.me.sync.HTTPSynchronizer.synchronize(HTTPSynchronizer.java:190)
at com.sap.ip.me.sync.HTTPSynchronizer.exchangeData(HTTPSynchronizer.java:67)
at com.sap.ip.me.sync.SyncManagerImplNewProtocol.processSyncCycle(SyncManagerImplNewProtocol.java:147)
at com.sap.ip.me.sync.SyncManagerImpl.syncForUser(SyncManagerImpl.java:909)
at com.sap.ip.me.sync.SyncManagerImpl.processSynchronization(SyncManagerImpl.java:460)
at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend(SyncManagerImpl.java:274)
at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend(SyncManagerImpl.java:191)
at com.sap.ip.me.api.sync.SyncManager.synchronizeWithBackend(SyncManager.java:71)
at com.sap.ip.me.apps.jsp.Home$SyncRunnable.run(Home.java:443)
at java.lang.Thread.run(Thread.java:534)
com.sap.ip.me.api.sync.SyncException: Transport-layer (http) sync exception raised (root cause: Exception while synchronizing (java.net.ConnectException: Connection timed out: connect))
at com.sap.ip.me.sync.HTTPSynchronizer.exchangeData(HTTPSynchronizer.java:72)
at com.sap.ip.me.sync.SyncManagerImplNewProtocol.processSyncCycle(SyncManagerImplNewProtocol.java:147)
at com.sap.ip.me.sync.SyncManagerImpl.syncForUser(SyncManagerImpl.java:909)
at com.sap.ip.me.sync.SyncManagerImpl.processSynchronization(SyncManagerImpl.java:460)
at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend(SyncManagerImpl.java:274)
at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend(SyncManagerImpl.java:191)
at com.sap.ip.me.api.sync.SyncManager.synchronizeWithBackend(SyncManager.java:71)
at com.sap.ip.me.apps.jsp.Home$SyncRunnable.run(Home.java:443)
at java.lang.Thread.run(Thread.java:534)
D Synchronisation: Fire SyncEvent 1
P Thread Thread-25 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)
I SyncEvent Performing com.sap.ip.me.ccms.LastSuccessfulSyncAlert
P Thread Thread-25 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)
I SyncEvent Performing com.sap.ip.me.ccms.AlertManager
P Thread Thread-25 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)
I SyncEvent Performing com.sap.ip.me.services.os.AgentManager
P Thread Thread-25 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)
I SyncEvent Performing com.sap.ip.me.sync.LogSender
P Thread Thread-25 switched context to MI46414c5445524d4549455242 / MI46414c5445524d4549455242 (User: FALTERMEIERB, MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)
I SyncEvent Performing com.sap.ip.me.smartsync.core.SmartSyncRuntimeManager
D User has not been installed on MW, it is not ready for sync :FALTERMEIERB
P Thread Thread-25 switched context to MI46414c5445524d4549455242 / MI46414c5445524d4549455242 (User: FALTERMEIERB, MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)
I SyncEvent Performing com.sap.ip.me.apps.jsp.SyncStatus
P Thread Thread-25 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)
I SyncEvent Performing com.sap.ip.me.core.StatusUpdater
I Synchronization finished, Thread=Thread-25
D Set current application to 'MOBILEENGINE_JSP'
D AbstractMEHttpServlet:doGet(...) called
D AbstractMEHttpServlet:getEvent() done with event name = ''
D AbstractMEHttpServlet:dispatch request to '/jsp/home/synclog.jsp'
D Set current application to 'MOBILEENGINE_JSP'
D AbstractMEHttpServlet:doPost(...) called
D AbstractMEHttpServlet:getEvent() done with event name = ''
D AbstractMEHttpServlet:dispatch request to '/jsp/home/home.jsp'
D Set current application to 'MOBILEENGINE_JSP'
D AbstractMEHttpServlet:doGet(...) called
D AbstractMEHttpServlet:getEvent() done with event name = ''
D AbstractMEHttpServlet:dispatch request to '/jsp/trace/trace.jsp'
D Set current application to 'MOBILEENGINE_JSP'
D AbstractMEHttpServlet:doGet(...) called
D AbstractMEHttpServlet:getEvent() done with event name = ''
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Barbara,
I would like to know whether you are making use of ABAP Sync Service or the Sync Servlet to synchronize. If you are using the ABAP Sync Service, then please set these profile parameters to appropriate values.
icm/conn_timeout
icm/keep_alive_timeout
icm/server_port_< n >
This has to be set in the transaction RZ11. Well a restart of the system is necessary after this.
For more information on timeouts, you can refer to note 824554.
Regards,
Nameeta
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Barbara,
From the trace file you can see that the Client is on SP09 and not SP13
[20070612 11:58:03:318] I [MI/API/Logging ] ***** Mobile Engine version: MI 25 SP 09 Patch 00 Build 200409101427
Request you to upgrade the client framework.
I recommend that you have the same SP levels for the client and server as it will make use of all the new developments. But you need a minimum of 13 for it to work.
Thanks,
Karthik Setty
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Uwe,
the parameter was set to 6000.
Now I put it up to 600000, but I still get the same error.
I guess the problem is somewhere else ...
Any idea?
Barbara
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Now I get another error message:
Synchronisation problems: Transport-layer (http) sync exception raised (root cause: URL connection test timeout)
Does anybody know where I can set the timeout parameters??
Thanks,
Barbara
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Barbara,
did you set parameter MobileEngine.Sync.ConnectionTimeout?
Maybe you sholud have a look here:
<a href="http://help.sap.com/saphelp_nw2004s/helpdata/de/a7/893a5889e08b41b615688b1a93b559/frameset.htm">http://help.sap.com/saphelp_nw2004s/helpdata/de/a7/893a5889e08b41b615688b1a93b559/frameset.htm</a>
Regards,
Uwe
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Barbara,
I guess u wud have reinstalled the Client also.
After installation did u fill the parameters in the <b>Settings</b> page???
Give the parameters correctly...
Cheers,
Kiran Joshua
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Workload Analysis for HANA Platform Series - 1. Define and Understand the Workload Pattern in Technology Blogs by SAP
- Workload Analysis for HANA Platform Series - 0. HANA Workload Analysis Overview in Technology Blogs by SAP
- Taking Data Federation to the Next Level: Accessing Remote ABAP CDS View Entities in SAP HANA Cloud in Technology Blogs by SAP
- Deep dive into ABAP Debugging in Technology Blogs by Members
- sap system issue analysis by kernel snapshot analyzer tool in Technology Blogs by Members
| User | Count |
|---|---|
| 93 | |
| 10 | |
| 10 | |
| 9 | |
| 9 | |
| 7 | |
| 6 | |
| 5 | |
| 5 | |
| 4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.