×

Discussion Board

Results 1 to 13 of 13
  1. #1
    Registered User
    Join Date
    Sep 2003
    Posts
    11

    Error: jes-16b-ConnectionsEventServer

    I have obtained this errror reading a stream from a web server.


    I have checked the configuration of my connection to Internet and all seems correct.

    It seems to occcur when the data exceedes a limit...

    Please, any suggestion?

  2. #2
    Registered User
    Join Date
    Sep 2003
    Posts
    11

    More information about error

    Once the error has appeared for the first time, it appears again each time I try to make a new connection with the web server.

    Please, could anyone tell me where could I find more information about this error? I have looked for it in the web but I have not found almost anything of interest.

  3. #3
    Registered User
    Join Date
    Sep 2003
    Posts
    8

    Workaround for the EventServer problem

    Dear Han Solo, Skywalker and the rest..


    After having spend (many) hours on this undocumented eventserver problem, and talking intensively to my network operator, the following facts have been discovered:

    Using an Url like: "http://xx.xxx.xxx.xx/XXXXX" produces a hit on the operator gateway like: "http://xx.xxx.xxx.xx/XXXXXX,4,200,1,4,0,,1,4,373713,1,0,,,,,,,,,,,,"

    The last portion of the hit is produced in the handset, by the handset.

    To workaround some of the problems with the ConnectionsEventServer FAULT, I have come up with the following advice (using these rules I now have (for the first time in a week) a stable application (it has not broken down after intensive testing today)):

    Dont use ANY special characters in your URL only letters and numbers.

    Dont connect to ANY other port than standard http-80.

    Dont even think about using any other protocol than http.



    And to really make sure:
    Take your Nokia 3650 - put it into an airtight container, and put this container under at least 4 feet of water and leave for holiday..

    If anybody have some conspriacy teories on this one Id be happy to listen (:

    Regards
    Casper

    -Still wandering when Nokia will acknowledge this major problem in their JVM.

  4. #4
    Registered User
    Join Date
    Sep 2003
    Posts
    11
    Thank you very much Casper for your suggestions but unfortunately the error persists in my software after applying your rules.

    The most strange thing for me is that this error only appears after a number of correct executions. I seems to depend on the data amount transfered between the server and the handheld...

    May the force be with us....

  5. #5
    Registered User
    Join Date
    Sep 2003
    Posts
    8

    More info

    Hello Sir Solo

    Ok, this properly means that my application is still unstable ):

    I have tried making 51 contiuos connections through it without failure, but this is not really scientific, as none of us knows WHAT THIS ERROR MEANS (capitalized just in case anybody is actually working at Nokia, and are monitoring this newsgroup, properly not...)

    I just got in Contact with one of the chief Nokia executives today - the project im working on is sponsored by his good personal friend - and will call him first thing tomorrow and get a technician to look at this. Maybe a little cooperate pressure on the techs will get at least some official Nokia comment on their FAULTY jvm.


    "Dont underestimate the power of the dark side" - Darth Vader (| SW episode V.

    Regards
    Casper

  6. #6
    Registered User
    Join Date
    Sep 2003
    Posts
    8

    Heres somebody with similar challenges

    http://lists.bawug.org/pipermail/wir...ly/012510.html

    http://forum.java.sun.com/thread.jsp...&thread=316097

    http://groups.google.dk/groups?hl=da...25C3%25B8gning

    And a there is a lot more out there - nobody can actually define what the problem is, but here is some of the discovered causes for it:

    Making around 15 connection attempts in row.

    Including any special characters in the url for opening Streams.

    TCP/IP not implemented on the 3650 platform until some time next year (Nokia Call-center information)

    Making loud noices in the vicinity of the device.


    Solutions varies also:

    Tune your threadhandling.

    Use an internet access point instead of a wap access point.

    Dont use any other protocol than http.

    Dont use any other port than standard port 80.

    Dont use any special characters in url

    Dont use java

  7. #7
    Registered User
    Join Date
    Sep 2003
    Posts
    8

    InputStream.read(byte[])

    Oh yeah and btw Han S:
    InputStream.read(byte[]) have an (undocumented) barrier on the maximum size of bytes returned: 512 byte.

    /Casper

  8. #8
    Registered User
    Join Date
    Sep 2003
    Posts
    11
    Thank you very much Sir Casper for all your comments.

    We are going to contact with some technical staff outside our trade and if we get whatever information about this Darth error I will post it as soos as possible.


    Now I am trying to relate this error with the length of my http request...

    If Darth Vader help us to solve this, I will have to think about joining to the Dark Side...

    Best regards.

  9. #9
    Registered User
    Join Date
    Sep 2003
    Posts
    8

    Max url length

    Ola Han


    Reading your mail I tested what you said and da da raaa:

    Url have a maximum length of 256. Everything larger than this number also causes the now well renowned (and still? by Nokia unrecognized) FAULT in their series 60 jvm.

    The 256 limit are the number of characters in the url after the "http://xxx.xx.xx.xx/" identifier.

    So one more cause is added to the expanding list... Maybe Nokia should start paying me for debugging their software (?

  10. #10
    Registered User
    Join Date
    Sep 2003
    Posts
    11

    Partial solution

    Hello CaSkywalper:

    I have limited the length of the URLs and make all the requests through POST and now the application SEEMS to belong to the good side of the force, but like you said, we dont know what the error means and what are its reasons...

    We are going to have a meeting on Monday 29th with people from our services provider, with the intentions of asking for help inside their trade and to make pressure to NOKIA people here in Spain.

    It will a pleasure for me to inform you about the results.

    May the force be with you.

  11. #11
    Registered User
    Join Date
    Sep 2003
    Location
    Istanbul
    Posts
    12

    Maximum URL size...

    Hi,

    Is the maximum length of URL in series 60 jvm is 256 ? And does Series 60 have a limit on byte[] for reading inputstream?


    Alp Eren YILMAZ

  12. #12
    Registered User
    Join Date
    Mar 2003
    Posts
    25

    Same Problem with the 7650

    Unfortunatly this thead stops but I have the same problem ! Doing a HTTP GET throws and error like JES-xx etc. ! Did you solves your problem. The URL I like to connect is less than 256 chars (www.google.de ) !

    best regards

    joerg

  13. #13
    Registered User
    Join Date
    Oct 2003
    Posts
    10
    Wondering if anyone was still out there monitoring this thread.. Updates? Anything???

    This error doesn't occur right away, does it? On my 3650, it'll usually happen on the 3rd or so connection. I notice that the error _usually_ happens when it's following a previous connection too closely. As if the previous connection didn't clean up and conflicted with the next connection.

    How closely are your connections?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •