MAU Frontend does not start on PDA

[Former Member]

Hi all.

Well am posting a lot of questions this week.

I have a problem starting the Frontend of MAU. We extended the Frontend but on PC it works fine. When I try to start the Frontend on the PDA after i synced all needed data the Pocket IE is running an running and running ...

There are logs that shows that my extended Controllerclass is called (onLoad). So it seems to work. The last log is:

[MI/API/Runtime/JSP ] AbstractMEHttpServlet:dispatch request to '/notification/re_main_menu.jsp'

Then nothing. I can wait 10 minutes but nothing happens. When i Cancel the request and click on a link of MI afterwards (Settings) I have the same problem. Looks like the MI is not responding anymore.

I am using MI 2.5 SP13 P00 on Creme 3.25.

Any ideas?

thanks.

Regards,

Sascha

[Former Member]

hello sascha,

do you have load-on-startup settings in you MAU's web.xml?

from the logs, it seems that the MAU is initialized prior

to ME... which might be the cause if you have some MI

API invocations in your MAU's initialization process. you

have to let MI load first before loading MAU...

regards

jo

[Former Member]

Hi Jo.

Unfortunately I am home now and do not have access to the web.xml. Actually I am not sure what you mean. I have to start MI prior and after that I start MAU from the link in MI. What I do not understand is why exactly the same WAR file is working without any problem on the PC Version of MI. Do you think it could be a good idea to patch the MI? As I said we are using MI 2.5 SP0 P00.

Thanks for the answer.

Cheers,

Sascha

[Former Member]

Hi all.

I solved it by upgrading to SP 16. Now the Frontend starts without any problems.

Thanks for your helps so far.

Regards,

Sascha

[Former Member]

Hi,

have you checked the JSPCOUT trace file of creme?

May provide more info (e.g. traces of MI).

Rgds Thomas

[Former Member]

Hi Thomas.

Hier is the trace:

[20030320 22:49:13:141] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:doGet(...) called

[20030320 22:49:13:145] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:getEvent() done with event name = ''

[20030320 22:49:13:151] A [Unknown ] [REHomeController.onLoad] start

[20030320 22:49:13:156] D [MI/Persistence ] Get IPersistenceManager for ConversationID: 44C71D8E536A29A3E10000000A64328F

[20030320 22:49:13:162] D [MI/Persistence ] beginTransaction() called with doWait=false for instance 2180278

[20030320 22:49:13:166] D [MI/Persistence ] PersistenceManagerImpl.beginTransaction():false

[20030320 22:49:13:172] D [MI/Persistence ] PersistenceManagerImpl.get(IClassDescriptor,ICondition):(IClassDescriptor(Name: cUMAM_070_TOP)),(state <16)

[20030320 22:49:13:259] D [MI/Persistence ] commit() called on instance 2180278

[20030320 22:49:13:263] D [MI/Persistence ] PersistenceManagerImpl.commit()

[20030320 22:49:18:000] D [Unknown ] OS: WindowsCE

[20030320 22:49:18:128] A [Unknown ] [REHomeController.onLoad] end

[20030320 22:49:18:137] A [Unknown ] [MainMenuController.onLoad] Meldungen: 0. Davon offen 0

[20030320 22:49:18:143] D [MI/Persistence ] Get IPersistenceManager for ConversationID: 44C71D8E536A29A3E10000000A64328F

[20030320 22:49:18:148] D [MI/Persistence ] beginTransaction() called with doWait=false for instance 2393567

[20030320 22:49:18:152] D [MI/Persistence ] PersistenceManagerImpl.beginTransaction():false

[20030320 22:49:18:157] D [MI/Persistence ] PersistenceManagerImpl.get(IClassDescriptor,ICondition):(IClassDescriptor(Name: cUMAM_090_TOP)),(state <16)

[20030320 22:49:18:168] D [MI/Persistence ] commit() called on instance 2393567

[20030320 22:49:18:172] D [MI/Persistence ] PersistenceManagerImpl.commit()

[20030320 22:49:18:190] D [MI/Persistence ] Get IPersistenceManager for ConversationID: 44C71D8E536A29A3E10000000A64328F

[20030320 22:49:18:195] D [MI/Persistence ] beginTransaction() called with doWait=false for instance 2401819

[20030320 22:49:18:199] D [MI/Persistence ] PersistenceManagerImpl.beginTransaction():false

[20030320 22:49:18:205] D [MI/Persistence ] PersistenceManagerImpl.get(IClassDescriptor,Object):(IClassDescriptor(Name: cUMAM_095_TOP)),1070997

[20030320 22:49:18:214] D [MI/Persistence ] commit() called on instance 2401819

[20030320 22:49:18:217] D [MI/Persistence ] PersistenceManagerImpl.commit()

[20030320 22:49:18:224] D [MI/Persistence ] Get IPersistenceManager for ConversationID: 44C71D8E536A29A3E10000000A64328F

[20030320 22:49:18:229] D [MI/Persistence ] beginTransaction() called with doWait=false for instance 2418407

[20030320 22:49:18:233] D [MI/Persistence ] PersistenceManagerImpl.beginTransaction():false

[20030320 22:49:18:240] D [MI/Persistence ] PersistenceManagerImpl.get(IClassDescriptor,ICondition):(IClassDescriptor(Name: cUMAM_095_030)),((syncBoKey =1070997) AND(state <16))

[20030320 22:49:18:249] D [MI/Persistence ] commit() called on instance 2418407

[20030320 22:49:18:252] D [MI/Persistence ] PersistenceManagerImpl.commit()

[20030320 22:49:20:047] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:dispatch request to '/notification/re_main_menu.jsp'

It looks exactly as on PC. Last entry on PC is also the dispatch entry. But there it works.

Here is the creme output:

NSIcom Ltd., CrEme(tm)

CrEme J2ME(tm)

CrEme V3.25 B080.040628 28-June-2004

MemoryLimit=27648Kb

EBCI(TM) Interpreter V1.00,

Copyright 1998-2002 by Bytecodes, Inc.

Do not use the MobileEngine classloader

-

---

Initialize framework ...

Configuration initialized. Installation Base = /MI

Path settings adjusted

Timezone initialized; use timezone id 'ECT'

Trace initialized. Log is switched on.

Framework singletons initialized.

Gzip data compression configuration initialized.

Registry initialized.

MI OS installer lib (/MI/bin/NATSTART.DLL) loaded successfully.

Dlls loaded.

Timed Sync initialized.

Persistence initialized.

Smart Sync initialized.

CCMS initialized.

Agents initialized.

Communication server initialized.

-

---

Framework initialized.

-

---

Check if running inside installation server.

Installation toolkit parameters /MI/itool.properties not detected

Use normal startup: true

Starting tomcat. Check logs/tomcat.log for error messages

Client Installer Packages status updated.

UnsatisfiedLinkError:getOS

================================================= ! ======================

UnsatisfiedLinkError:getOS

================================================= ! ======================

UnsatisfiedLinkError:getOS

Servlet.log:

2003-03-20 23:33:04 - path="" :jsp: init

2003-03-20 23:33:05 - path="/MAU" :jsp: init

2003-03-20 23:33:06 - path="/me" :jsp: init

2003-03-20 23:33:08 - path="/me" :com.sap.ip.me.apps.jsp.LoginServlet: init

2003-03-20 23:33:10 - path="/me" :jsp.login.login: init

2003-03-20 23:33:46 - path="/me" :jsp.home.home: init

2003-03-20 23:33:49 - path="/me" :com.sap.ip.me.apps.jsp.ControllerServlet: init

2003-03-20 23:33:49 - path="/MAU" :MAMStart: init

2003-03-20 23:33:56 - path="/MAU" :MAMStart: init

2003-03-20 23:34:01 - path="/MAU" :front: init

2003-03-20 23:49:37 - path="/MAU" :jsp: init

This is really strange. Seems that the problem is that i directly forward from the /mau_home.jsp to my new jsp in the onLoad method. The onLOad controller method of my new pages is called. But the site not displayed.

Strange is that the MI is not responding afterwards. Even if i restart the Pocket IE the MI does not showe the Loginpage. Just the progress image ... nothing more.

I dont have a clue.

Regards,

Sascha