04-18-2012 03:45 PM
Using BlackBerry plugin for Eclipse
For OS 6
After taking two weeks to try and fix a simple "do not close until you are done" error with SQLite, I am now having a little bit of a setup issue with the Eclipse software.
When I push a message to the simulator, I get the following error.
<2012-04-18 15:39:15.471 EDT>:[378]:<MDS-CS_MDS>:<DEBUG>:<LAYER = SCM, EVENT = N otifying to URL = http://172.17.111.35:14002?pushID=268848&clientID=dean.logan@bhemail.com&priority=2&besurl=192.168.1 ... pushId = -62be8811:136c6f71d73:-7ff576188, destination = dean.logan@bhemail.com, result code = 400 net.rim.protocol.iplayer.push.b: Push connection aborted by device>
According to the knowledge base, a 400 error is "Invalid Push format.
Mobile Data Service 3.7 and earlier: The email address or personal identification number (PIN) used in the Push was not recognized as a BlackBerry Enterprise Server user enabled for Mobile Data Service."
I'm sure it is something with the setup in the rim.property files. Something probably needs to be turned on or off that I can't figure out.
[MonitorAgent] MonitorAgent.listen.port=8070 [WebServer] WebServer.Tomcat.transcoding= false WebServer.listen.host=localhost WebServer.listen.port=8080 WebServer.listen.sslport=8443 WebServer.servlet.monitor.port=8070 WebServer.servlet.monitor.host=localhost WebServer.servlet.push.port=81 WebServer.servlet.push.host=localhost WebServer.servlet.push.ssl=false [SRP] SRP.UID= please get one SRP.AuthenticationString= Please get one SRP.InetAddress= Please get one SRP.Port=3101 SRP.logging=true [IPPP] IPPP.push.listen.tcp.port=81 IPPP.connection.MaxNumberOfKBytesToSend=128 IPPP.queue.flowcontrol.window.size=-1 IPPP.queue.flowcontrol.timeout=600000 IPPP.logging=true [UDP] UDP.receive.port=19781 UDP.send.default=19780 UDP.init=initialization_packet UDP.logging=true [HTTP HANDLER] application.handler.http.logging = true application.handler.http.CookieSupport = true application.handler.http.AuthenticationSupport = true application.handler.http.AuthenticationTimeout = 3600000 application.handler.http.device.connection.timeout = 140000 application.handler.http.server.connection.timeout = 150000 application.handler.http.device.credentialTimeout = 60000 application.handler.http.authentication.mechName2oid = Negotiate=1.2.840.113554.1.2.2, NTLM=1.3.6.1.4.1.311.2.2.10, Basic=1.3.6.1.4.1.88888.1.2 [Security] net.rim.security.auth.DefaultDomain = rim.net [HTTPS HANDLER] application.handler.https.allowUntrustedServer = false application.handler.https.logging = true [TLS HANDLER] application.handler.tls.allowUntrustedServer = false application.handler.tls.logging = true [OCSP HANDLER] application.handler.ocsp.StatusProviders = net.rim.protocol.iplayer.connection.handler.device .ocsp.OCSPProvider application.handler.StatusProviders.OCSP.PrimaryRe sponderRank = Default application.handler.StatusProviders.OCSP.Responder .Default = http://dhobbs-wnt.rim.net/ocsp application.handler.StatusProviders.OCSP.UseDevice Responders = yes application.handler.StatusProviders.OCSP.UseCertRe sponders = yes application.handler.ocsp.DebugLogging = no [LDAP HANDLER] application.handler.ldap.DEFAULT_SERVER = dhobbs-wnt application.handler.ldap.DEFAULT_PORT = 389 application.handler.ldap.DEFAULT_QUERY = ou=people, o=rim.net application.handler.ldap.DEFAULT_LIMIT = 20 application.handler.ldap.COMPRESSION = true application.handler.ldap.logging = false [Database] Database.shouldConnect=false BESName=DAISY1 Database.Driver=sun.jdbc.odbc.JdbcOdbcDriver Database.URL=jdbc:odbc:BESMgmt Database.DBCycleTimer=5 [ACL] ACL.Authorization.Datastore=net.rim.shared.service .authorization.JDBCAuthorizationDatastore ACL.Enabled=false [ESS] ESS.helpfile = help/Using_the_Email_Server_Simulator.html ESS.launcher = bin/launcher.exe [Email] Email.deviceId =2100000A Email.pop3Server =pop3.server Email.smtpServer =smtp.server Email.personal =Dean Logan Email.address =Dean.Logan@bhemail.com Email.smtpPort =25 Email.pop3Port =110
Any suggestions?
Solved! Go to Solution.
04-20-2012 08:45 AM
Figured it out.
When setting the device port, I had the wrong port
_notify = (StreamConnectionNotifier)Connector.open(appAttrib
My company uses a Test port and a Prod port, so that we could have 2 versions of the app on the device at the same time. So, chaning the listening port to 1313 from 1315 allowed the push service to push to the correct port and the app was able to read the data.