Problems with the built in server in wap toolkit 2.1

[Nokia_Archived]

Posted by Roberto D'Angelo, roberto@difnet.net
on February 13, 2001 at 22:48

The built in server doesn't start. Here is what I see in the dos windows when I try to start it manually:

-----------------------------------------------------------------------------
Nokia WAP Server Simulator. Based on:

Nokia Activ Server 2.0 Professional (build 2451A))

Copyright (c) Nokia Corporation 2000. All rights reserved.
-----------------------------------------------------------------------------

Java Version: 1.3.0 / Sun Microsystems Inc.
Character Set: Cp1252
Virtual Machine: Java HotSpot(TM) Client VM 1.3.0-C / Sun Microsystems Inc.
Operating System: Windows 98 4.90

ServerMgr: Loading libraries
ServerMgr: Library loading completed
------------------------------------
ServerMgr: Initialising Server components
ServerMgr: Initialisation of Server components completed
--------------------------------------------------------
ServerMgr: Server initialised, starting traffic
ServerMgr: Starting components
BearerMgr: UDP start
BearerMgr: UDP failed to start
ServerMgr: Traffic start failed: Component Startup failed
ServerMgr: Server initialised. Traffic is stopped: com.nokia.wap.gw.manager.Mana
gerException Error: 5103(Component Startup failed)


So I can't use the 2 emulators but only the blueprint that doesn't need the server to run.

Any idea why the UDP failed and stopped the server?

[Nokia_Archived]

Posted by WAP Toolkit Team, info.wapbrowser@nokia.com
on February 15, 2001 at 22:20

When you use emulators, emulators start the in-built server (Server Simulator). You dont have to start it manually. Please check the messages window in Toolkit panel to see if Server Simulator has been started correctly when you launch the emulators.

[Nokia_Archived]

Posted by WAP Toolkit Team, info.wapbrowser@nokia.com
on February 16, 2001 at 18:38


Yes. The UDP fails to bind to a socket. You cannot start two identical instances of Server Simulator because they will attempt to use the same UDP ports. You can however, create a second, totally independent copy of Server Simulator installation, fix the configuration so that they use different ports and run two simulators at the same. But I don't know why would anyone want to do that.

If the single instance does not start with the same "UDP failed to start" error message, it most likely means that there's a stale Server Simulator process running (toolkit starts server simulator as a separate process as opposed to loading it into the same JVM). For instance, if you manually kill the toolkit, the Server Simulator process will keep running. It shows up in Task manager as a "javaw.exe" process. Killing the Server Simulator process solves the problem (be careful, you may have more than one javaw.exe running, don't kill something useful). You also want to kill any stale 6210.exe and 7110.exe processes because they create a similar problem with phone simulators.