Welcome!

Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

inside custom component

Java Development

Reply
New Contributor
Posts: 7
Registered: ‎06-21-2011
My Device: blackberry curve 9300
My Carrier: Digicel Jamaica

dual simulators cant communicate over bbm

[ Edited ]

http://docs.blackberry.com/en/developers/deliverables/25813/index.jsp?name=Getting+Started+Guide+-+B...

 

i followed the whole guide here. the two instances of the blackberry simulator can connect to the internet but they cant seem to see each other's bbm invites. what did i miss?

BlackBerry Development Advisor
Posts: 15,727
Registered: ‎07-09-2008
My Device: BlackBerry PRIV
My Carrier: Bell

Re: dual simulators cant communicate over bbm

Do you see any errors in the MDS-CS Simulator when the invites are sent?

Mark Sohm
BlackBerry Development Advisor

Please refrain from posting new questions in solved threads.
Problem solved? Click the Accept As Solution button.
Found a bug? Report it using Issue Tracker
New Contributor
Posts: 7
Registered: ‎06-21-2011
My Device: blackberry curve 9300
My Carrier: Digicel Jamaica

Re: dual simulators cant communicate over bbm

mds log

 

nothing happened. mds gets really active when I browse the internet though.

 

I googled bits and pieces of MDP.map.destination.routing.point.value.3 is missing but I could not find out what it was

 

 

BlackBerry Development Advisor
Posts: 15,727
Registered: ‎07-09-2008
My Device: BlackBerry PRIV
My Carrier: Bell

Re: dual simulators cant communicate over bbm

I don't see a definitive error there.  Can you post the entire output from the MDS-CS Simulator (paste as code to preserve formatting)?

 

I recommend going over the guide once more:  http://docs.blackberry.com/en/developers/deliverables/25813/Configuring_your_system_for_BBM_support_...

 

You may have missed a step along the way.

Mark Sohm
BlackBerry Development Advisor

Please refrain from posting new questions in solved threads.
Problem solved? Click the Accept As Solution button.
Found a bug? Report it using Issue Tracker
New Contributor
Posts: 7
Registered: ‎06-21-2011
My Device: blackberry curve 9300
My Carrier: Digicel Jamaica

Re: dual simulators cant communicate over bbm

SCM 4.1.4.19 19 2007/07/10
<2011-06-30 13:58:12.638 GMT-05:00>:[2]:<MDS-CS_MDS>:<INFO >:<LAYER = SCM, J2SE 1.6.0_25 Charsets su
pported:Big5,Big5-HKSCS,EUC-JP,EUC-KR,GB18030,GB2312,GBK,IBM-Thai,IBM00858,IBM01140,IBM01141,IBM0114
2,IBM01143,IBM01144,IBM01145,IBM01146,IBM01147,IBM01148,IBM01149,IBM037,IBM1026,IBM1047,IBM273,IBM27
7,IBM278,IBM280,IBM284,IBM285,IBM297,IBM420,IBM424,IBM437,IBM500,IBM775,IBM850,IBM852,IBM855,IBM857,
IBM860,IBM861,IBM862,IBM863,IBM864,IBM865,IBM866,IBM868,IBM869,IBM870,IBM871,IBM918,ISO-2022-CN,ISO-
2022-JP,ISO-2022-JP-2,ISO-2022-KR,ISO-8859-1,ISO-8859-13,ISO-8859-15,ISO-8859-2,ISO-8859-3,ISO-8859-
4,ISO-8859-5,ISO-8859-6,ISO-8859-7,ISO-8859-8,ISO-8859-9,JIS_X0201,JIS_X0212-1990,KOI8-R,KOI8-U,Shif
t_JIS,TIS-620,US-ASCII,UTF-16,UTF-16BE,UTF-16LE,UTF-32,UTF-32BE,UTF-32LE,UTF-8,windows-1250,windows-
1251,windows-1252,windows-1253,windows-1254,windows-1255,windows-1256,windows-1257,windows-1258,wind
ows-31j,x-Big5-HKSCS-2001,x-Big5-Solaris,x-euc-jp-linux,x-EUC-TW,x-eucJP-Open,x-IBM1006,x-IBM1025,x-
IBM1046,x-IBM1097,x-IBM1098,x-IBM1112,x-IBM1122,x-IBM1123,x-IBM1124,x-IBM1381,x-IBM1383,x-IBM33722,x
-IBM737,x-IBM833,x-IBM834,x-IBM856,x-IBM874,x-IBM875,x-IBM921,x-IBM922,x-IBM930,x-IBM933,x-IBM935,x-
IBM937,x-IBM939,x-IBM942,x-IBM942C,x-IBM943,x-IBM943C,x-IBM948,x-IBM949,x-IBM949C,x-IBM950,x-IBM964,
x-IBM970,x-ISCII91,x-ISO-2022-CN-CNS,x-ISO-2022-CN-GB,x-iso-8859-11,x-JIS0208,x-JISAutoDetect,x-Joha
b,x-MacArabic,x-MacCentralEurope,x-MacCroatian,x-MacCyrillic,x-MacDingbat,x-MacGreek,x-MacHebrew,x-M
acIceland,x-MacRoman,x-MacRomania,x-MacSymbol,x-MacThai,x-MacTurkish,x-MacUkraine,x-MS932_0213,x-MS9
50-HKSCS,x-MS950-HKSCS-XP,x-mswin-936,x-PCK,x-SJIS_0213,x-UTF-16LE-BOM,X-UTF-32BE-BOM,X-UTF-32LE-BOM
,x-windows-50220,x-windows-50221,x-windows-874,x-windows-949,x-windows-950,x-windows-iso2022jp>
<2011-06-30 13:58:15.077 GMT-05:00>:[3]:<MDS-CS_MDS>:<INFO >:<LAYER = SCM, EVENT = Default Job Pool
size = 10>
<2011-06-30 13:58:15.077 GMT-05:00>:[4]:<MDS-CS_MDS>:<INFO >:<LAYER = SCM, maxMem: 477233152 maxPool
Size: 10>
Jun 30, 2011 1:58:18 PM org.apache.catalina.startup.Embedded start
INFO: Starting tomcat server
<2011-06-30 13:58:19.873 GMT-05:00>:[5]:<MDS-CS_MDS>:<DEBUG>:<LAYER = SCM, EVENT = Connected, TOPSER
VICE = SRPH, LOWERSERVICE = GME>
<2011-06-30 13:58:19.874 GMT-05:00>:[6]:<MDS-CS_MDS>:<DEBUG>:<LAYER = SCM, EVENT = Connected, TOPSER
VICE = IPPP, LOWERSERVICE = GME>
<2011-06-30 13:58:19.875 GMT-05:00>:[7]:<MDS-CS_MDS>:<DEBUG>:<LAYER = SCM, EVENT = Connected, TOPSER
VICE = GME, LOWERSERVICE = MDP>
<2011-06-30 13:58:19.875 GMT-05:00>:[8]:<MDS-CS_MDS>:<DEBUG>:<LAYER = SCM, EVENT = Connected, TOPSER
VICE = MDP, LOWERSERVICE = GPAK>
<2011-06-30 13:58:19.876 GMT-05:00>:[9]:<MDS-CS_MDS>:<DEBUG>:<LAYER = SCM, EVENT = Connected, TOPSER
VICE = GPAK, LOWERSERVICE = UDP>
<2011-06-30 13:58:19.881 GMT-05:00>:[10]:<MDS-CS_MDS>:<EVENT>:<LAYER = SCM, EVENT = MDS-CS server ha
s started>
<2011-06-30 13:58:20.744 GMT-05:00>:[11]:<MDS-CS_MDS>:<DEBUG>:<LAYER = MDP, EVENT = Initialization>
<2011-06-30 13:58:20.745 GMT-05:00>:[12]:<MDS-CS_MDS>:<DEBUG>:<LAYER = MDP, EVENT = Started>
<2011-06-30 13:58:20.747 GMT-05:00>:[14]:<MDS-CS_MDS>:<DEBUG>:<LAYER = MDP, EVENT = Started, THREAD
= MdpLayerDatagramGC>
<2011-06-30 13:58:20.747 GMT-05:00>:[13]:<MDS-CS_MDS>:<DEBUG>:<LAYER = MDP, EVENT = Started, THREAD
= MdpLayerHigherLayerListeningThread:GME>
<2011-06-30 13:58:20.748 GMT-05:00>:[15]:<MDS-CS_MDS>:<DEBUG>:<LAYER = MDP, EVENT = Started, THREAD
= MdpLayerLowerLayerListeningThread:GPAK>
<2011-06-30 13:58:20.965 GMT-05:00>:[16]:<MDS-CS_MDS>:<DEBUG>:<LAYER = UDP, EVENT = Initialization>
<2011-06-30 13:58:20.965 GMT-05:00>:[17]:<MDS-CS_MDS>:<DEBUG>:<LAYER = UDP, EVENT = Started>
<2011-06-30 13:58:20.967 GMT-05:00>:[18]:<MDS-CS_MDS>:<DEBUG>:<LAYER = UDP, EVENT = Started, THREAD
= UdpLayerReceiverThread>
<2011-06-30 13:58:20.968 GMT-05:00>:[19]:<MDS-CS_MDS>:<DEBUG>:<LAYER = UDP, EVENT = Started, THREAD
= UdpLayerSenderThread:GPAK>
<2011-06-30 13:58:21.114 GMT-05:00>:[20]:<MDS-CS_MDS>:<DEBUG>:<LAYER = SCM, EVENT = Expire records f
rom device storage that are expired or older than 0 hours; 0>
<2011-06-30 13:58:21.115 GMT-05:00>:[21]:<MDS-CS_MDS>:<DEBUG>:<LAYER = SCM, EVENT = Expire records p
rocess ended; 0>
<2011-06-30 13:58:21.116 GMT-05:00>:[22]:<MDS-CS_MDS>:<DEBUG>:<LAYER = SCM, EVENT = The push service
 is ready to receive requests>
<2011-06-30 13:58:21.117 GMT-05:00>:[23]:<MDS-CS_MDS>:<DEBUG>:<LAYER = SCM, EVENT = Admin. Task- pen
ding push messages>
Jun 30, 2011 1:58:22 PM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/5.5.20
Jun 30, 2011 1:58:22 PM org.apache.catalina.core.StandardHost start
INFO: XML validation disabled
<2011-06-30 13:58:23.963 GMT-05:00>:[24]:<MDS-CS_MDS>:<INFO >:<LAYER = IPPP, Sending Queue Size per
device =200>
Jun 30, 2011 1:58:23 PM org.apache.catalina.startup.ContextConfig defaultWebConfig
INFO: No default web.xml
<2011-06-30 13:58:24.002 GMT-05:00>:[25]:<MDS-CS_MDS>:<INFO >:<LAYER = IPPP, IPPP: Receiving Queue S
ize =10>
<2011-06-30 13:58:24.006 GMT-05:00>:[26]:<MDS-CS_MDS>:<INFO >:<LAYER = IPPP, IPPP: Receiving Queue S
ize =10>
<2011-06-30 13:58:24.016 GMT-05:00>:[27]:<MDS-CS_MDS>:<DEBUG>:<LAYER = IPPP, LAYER = IPPP, EVENT = S
tarted>
<2011-06-30 13:58:24.023 GMT-05:00>:[28]:<MDS-CS_MDS>:<DEBUG>:<LAYER = IPPP, EVENT = Started, THREAD
 = ListenOnDatagramStatus>
<2011-06-30 13:58:24.024 GMT-05:00>:[29]:<MDS-CS_MDS>:<DEBUG>:<LAYER = IPPP, EVENT = Started, THREAD
 = ConnectionsInputStreamesReader0>
<2011-06-30 13:58:24.024 GMT-05:00>:[30]:<MDS-CS_MDS>:<DEBUG>:<LAYER = IPPP, EVENT = Started, THREAD
 = QueuesManager>
<2011-06-30 13:58:24.025 GMT-05:00>:[31]:<MDS-CS_MDS>:<DEBUG>:<LAYER = IPPP, EVENT = Started, THREAD
 = ListenForClientsPackets>
<2011-06-30 13:58:24.038 GMT-05:00>:[32]:<MDS-CS_MDS>:<DEBUG>:<LAYER = SRPH, LAYER = SRPH, EVENT = I
nitialization>
<2011-06-30 13:58:24.110 GMT-05:00>:[33]:<MDS-CS_MDS>:<INFO >:<maxMem: 477233152 maxQueueSize: 250>
<2011-06-30 13:58:24.117 GMT-05:00>:[34]:<MDS-CS_MDS>:<DEBUG>:<LAYER = SRPH, LAYER = SRPH, EVENT = S
tarted>
<2011-06-30 13:58:24.119 GMT-05:00>:[35]:<MDS-CS_MDS>:<DEBUG>:<LAYER = SRPH, EVENT = Started, THREAD
 = SRPHprotocolMainThread>
<2011-06-30 13:58:24.121 GMT-05:00>:[36]:<MDS-CS_MDS>:<DEBUG>:<LAYER = SRPH, EVENT = Started, THREAD
 = SRPHListenForClientsPackets>
<2011-06-30 13:58:24.123 GMT-05:00>:[37]:<MDS-CS_MDS>:<DEBUG>:<LAYER = SRPH, EVENT = Started, THREAD
 = SRPHListenOnDatagramStatus>
<2011-06-30 13:58:24.124 GMT-05:00>:[38]:<MDS-CS_MDS>:<DEBUG>:<LAYER = SRPH, EVENT = Started, THREAD
 = SRPHQueuesManager>
<2011-06-30 13:58:24.226 GMT-05:00>:[39]:<MDS-CS_MDS>:<DEBUG>:<LAYER = GPAK, EVENT = Initialization>

<2011-06-30 13:58:24.227 GMT-05:00>:[40]:<MDS-CS_MDS>:<DEBUG>:<LAYER = GPAK, EVENT = Started>
<2011-06-30 13:58:24.236 GMT-05:00>:[41]:<MDS-CS_MDS>:<DEBUG>:<LAYER = GPAK, EVENT = Started, THREAD
 = GpakLayerHigherLayerListeningThread:MDP>
<2011-06-30 13:58:24.242 GMT-05:00>:[42]:<MDS-CS_MDS>:<DEBUG>:<LAYER = GPAK, EVENT = Started, THREAD
 = GpakLayerLowerLayerListeningThread:UDP>
Jun 30, 2011 1:58:25 PM org.apache.catalina.core.ApplicationContext log
INFO: AdministrationController (Status):init
Jun 30, 2011 1:58:25 PM org.apache.catalina.core.ApplicationContext log
INFO: E:\Program Files\Research In Motion\BlackBerry Email and MDS Services Simulators 4.1.4\MDS
Jun 30, 2011 1:58:25 PM org.apache.catalina.core.ApplicationContext log
INFO: AdministrationController (Statistics):init
Jun 30, 2011 1:58:25 PM org.apache.catalina.core.ApplicationContext log
INFO: E:\Program Files\Research In Motion\BlackBerry Email and MDS Services Simulators 4.1.4\MDS
Jun 30, 2011 1:58:25 PM org.apache.coyote.http11.Http11BaseProtocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
Jun 30, 2011 1:58:25 PM org.apache.coyote.http11.Http11BaseProtocol start
INFO: Starting Coyote HTTP/1.1 on http-8080
<2011-06-30 13:58:25.755 GMT-05:00>:[43]:<MDS-CS_MDS>:<DEBUG>:<LAYER = SCM, Web Server Started>
<2011-06-30 14:00:54.554 GMT-05:00>:[44]:<MDS-CS_MDS>:<DEBUG>:<LAYER = MDP, MDP.map.destination.rout
ing.point.value.3 is missing>
<2011-06-30 14:01:00.716 GMT-05:00>:[45]:<MDS-CS_MDS>:<DEBUG>:<LAYER = MDP, MDP.map.destination.rout
ing.point.value.3 is missing>
<2011-06-30 14:01:11.680 GMT-05:00>:[46]:<MDS-CS_MDS>:<DEBUG>:<LAYER = MDP, MDP.map.destination.rout
ing.point.value.3 is missing>
<2011-06-30 14:01:20.872 GMT-05:00>:[47]:<MDS-CS_MDS>:<DEBUG>:<LAYER = MDP, MDP.map.destination.rout
ing.point.value.3 is missing>
<2011-06-30 14:01:26.003 GMT-05:00>:[48]:<MDS-CS_MDS>:<DEBUG>:<LAYER = MDP, MDP.map.destination.rout
ing.point.value.3 is missing>
<2011-06-30 14:01:32.110 GMT-05:00>:[49]:<MDS-CS_MDS>:<DEBUG>:<LAYER = MDP, MDP.map.destination.rout
ing.point.value.3 is missing>
<2011-06-30 14:01:36.642 GMT-05:00>:[50]:<MDS-CS_MDS>:<DEBUG>:<LAYER = MDP, MDP.map.destination.rout
ing.point.value.3 is missing>
<2011-06-30 14:01:52.416 GMT-05:00>:[51]:<MDS-CS_MDS>:<DEBUG>:<LAYER = MDP, MDP.map.destination.rout
ing.point.value.3 is missing>
<2011-06-30 14:01:56.778 GMT-05:00>:[52]:<MDS-CS_MDS>:<DEBUG>:<LAYER = MDP, MDP.map.destination.rout
ing.point.value.3 is missing>
<2011-06-30 14:02:16.949 GMT-05:00>:[53]:<MDS-CS_MDS>:<DEBUG>:<LAYER = MDP, MDP.map.destination.rout
ing.point.value.3 is missing>
<2011-06-30 14:02:32.527 GMT-05:00>:[54]:<MDS-CS_MDS>:<DEBUG>:<LAYER = MDP, MDP.map.destination.rout
ing.point.value.3 is missing>
<2011-06-30 14:02:57.891 GMT-05:00>:[55]:<MDS-CS_MDS>:<DEBUG>:<LAYER = MDP, MDP.map.destination.rout
ing.point.value.3 is missing>
<2011-06-30 14:03:12.712 GMT-05:00>:[56]:<MDS-CS_MDS>:<DEBUG>:<LAYER = MDP, MDP.map.destination.rout
ing.point.value.3 is missing>
<2011-06-30 14:03:21.118 GMT-05:00>:[57]:<MDS-CS_MDS>:<DEBUG>:<LAYER = SCM, EVENT = Expire records f
rom device storage that are expired or older than 0 hours; 0>
<2011-06-30 14:03:21.118 GMT-05:00>:[58]:<MDS-CS_MDS>:<DEBUG>:<LAYER = SCM, EVENT = Expire records p
rocess ended; 0>
<2011-06-30 14:03:37.992 GMT-05:00>:[59]:<MDS-CS_MDS>:<DEBUG>:<LAYER = MDP, MDP.map.destination.rout
ing.point.value.3 is missing>
<2011-06-30 14:03:41.020 GMT-05:00>:[60]:<MDS-CS_MDS>:<DEBUG>:<LAYER = SCM, EVENT = Statistics save
task started>
<2011-06-30 14:03:41.070 GMT-05:00>:[61]:<MDS-CS_MDS>:<DEBUG>:<LAYER = SCM, EVENT = Statistics save
task finished -- number of rows inserted:5>
<2011-06-30 14:04:12.813 GMT-05:00>:[62]:<MDS-CS_MDS>:<DEBUG>:<LAYER = MDP, MDP.map.destination.rout
ing.point.value.3 is missing>
<2011-06-30 14:04:38.881 GMT-05:00>:[63]:<MDS-CS_MDS>:<DEBUG>:<LAYER = MDP, MDP.map.destination.rout
ing.point.value.3 is missing>
<2011-06-30 14:05:11.404 GMT-05:00>:[64]:<MDS-CS_MDS>:<DEBUG>:<LAYER = MDP, MDP.map.destination.rout
ing.point.value.3 is missing>
<2011-06-30 14:05:16.694 GMT-05:00>:[65]:<MDS-CS_MDS>:<DEBUG>:<LAYER = MDP, MDP.map.destination.rout
ing.point.value.3 is missing>

 still no luck Smiley Sad

Highlighted
Developer
Posts: 79
Registered: ‎09-22-2010
My Device: 9700

Re: dual simulators cant communicate over bbm

i think

it seems in in your bat files  src port is not set..

 

 

 

just check ur simulator bat files,sim1.bat and sim2.bat

set contents As

sim1.bat

@echo off
fledge.exe /app=Jvm.dll /handheld=9800 /session=Sim1 /app-param=JvmAlxConfigFile:9800.xml /data-port=0x4d44 /data-port=0x4d4e /pin=0x2100000A /app-param=regVersion=3 /app-param=regDestIP=127.0.0.1 /app-param=regDestPort=19781 /app-param=regSrcPort=19780 /app-param=DisableSyncServiceRecord /title="BlackBerry 9800-1 Simulator"

 

and sim2.bat

@echo off
fledge.exe /app=Jvm.dll /handheld=9800 /session=Sim2 /app-param=JvmAlxConfigFile:9800.xml /data-port=0x4d44 /data-port=0x4d4e /pin=0x2100000B /app-param=regVersion=3 /app-param=regDestIP=127.0.0.1 /app-param=regDestPort=19781 /app-param=regSrcPort=19782 /app-param=DisableSyncServiceRecord /title="BlackBerry 9800-2 Simulator"

 

then go to your Mds simulator's folder ,creat  a shortcut of run.bat

and remember  to modify  mds simulator's Bat  file property  checkout these steps

 


In Windows® Explorer, navigate to the folder where you created the Shortcut to run.bat file for the BlackBerry® MDS Simulator.

1.
In the folder where you extracted the .zip file containing the BlackBerry® Messenger SDK, open the MDS simulator folder.
2.
Extract the contents of the MDSv3.5.3.zip file.
3.
Open the sdk folder.
4.
Open the mds folder.
5.
Right-click run.bat and click Create Shortcut.
6.
Right-click the Shortcut to run.bat file and click Properties.
7.
In the Properties dialog box, in the Target field, add the following text:-log.console.dump -feature "bbm,keynego,monitor,servicebook,cmimep2p,ep2p,registration,ippp,http,httpm,htt pc,httpcm,defaulthandler" -webconfig all

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

 

 Make sure you have created the Shortcut to run.bat file in the task: Install and run the BlackBerry MDS Simulator.
1.

 

2.
Double-click Shortcut to run.bat to launch the BlackBerry MDS Simulator.
3.
In Windows Explorer, navigate to the folder where you installed the BlackBerry Smartphone Simulator. By default, the location of this folder is C:\Program Files\Research In Motion\BlackBerry Smartphone Simulators 6.0\6.0.0.313 (9800).
4.
Double-click the sim1.bat file (or your custom .bat file) to launch a BlackBerry Smartphone Simulator with appropriate settings to run your application and communicate with the BlackBerry MDS Simulator.
5.
To debug your application, in the BlackBerry JDE, click Debug > Attach To > Simulator.
6.
In Windows Explorer, in the BlackBerry Smartphone Simulator folder, double-click the sim2.bat file (or your second custom .bat file) to launch a second instance of the BlackBerry Smartphone Simulator with the appropriate settings to communicate with the first BlackBerry Smartphone Simulator.
7.
To have each instance of BlackBerry® Messenger have each other as contacts, in the first BlackBerry Smartphone Simulator instance, open BlackBerry Messenger.
8.
Click the Menu key and click the Invite Contact menu item.
9.
Click Invite by sending a PIN or email message.
10.
In the To field, type 2100000B. This is the default PIN of the second BlackBerry Smartphone Simulator instance.
11.
In the second BlackBerry Smartphone Simulator instance, open BlackBerry Messenger and accept the invitation.
12.
In the first BlackBerry Smartphone Simulator instance, close BlackBerry Messenger.
13.
On the Home screen, click the icon for your BlackBerry Messenger platform application.
You can now communicate between the two BlackBerry Smartphone Simulator instances.

 

 

 



Regular Visitor
Posts: 1
Registered: ‎03-14-2012
My Device: 9800
My Carrier: ATT

Re: dual simulators cant communicate over bbm

Hi,

 

  Did any one resolve the issue with 2 blacberry phone simulators not able to recognize each other and

send BBM message by using MDS 5?

 

   Is this forum monitored by BB developers ?

 

Thanks.