• About Us
  • Blog
  • Basket
  • Account
  • Sign In
  •  

Forums

PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 03 Aug 2016 11:00 AM by  Gerhard
Cannot download 51degrees data file
 2 Replies
Sort:
You are not authorized to post a reply.
Author Messages

Greg



New Member


Posts:2
New Member


--
12 Feb 2016 04:51 PM
    Hi,

    We started seeing the following error in our logs when attempting to download the 51degrees.dat using the auto updater.

    ERROR [FiftyOneDataFileUpdateScheduler] An error occurred while updating the 51Degrees data file. This may need performing manually.
    fiftyone.mobile.detection.AutoUpdateException: Device data download failed: java.security.cert.CertificateException: No subject alternative DNS name matching 51degrees.com found.
    at fiftyone.mobile.detection.AutoUpdate.download(Unknown Source)
    at fiftyone.mobile.detection.AutoUpdate.getNewDataset(Unknown Source)
    at fiftyone.mobile.detection.AutoUpdate.update(Unknown Source)
    at fiftyone.mobile.detection.AutoUpdate.update(Unknown Source)
    at com.gamesworkshop.device.detection.FiftyOneDataFileUpdateScheduler.doUpdate(FiftyOneDataFileUpdateScheduler.java:31)
    at com.gamesworkshop.device.detection.FiftyOneDataFileUpdateScheduler.doStartService(FiftyOneDataFileUpdateScheduler.java:18)

    Replacing our current copy of the 51degress.dat file with the latest version downloaded from https://51degrees.com/products/down...ds/premium gives the following error:

    ERROR [[jsp]] Servlet.service() for servlet jsp threw exception
    java.lang.NullPointerException
    at fiftyone.mobile.detection.Match.resetNextCharacterPositionIndex(Unknown Source)
    at fiftyone.mobile.detection.Match.init(Unknown Source)
    at fiftyone.mobile.detection.Match.reset(Unknown Source)
    at fiftyone.mobile.detection.Provider.matchNoCache(Unknown Source)
    at fiftyone.mobile.detection.Provider.match(Unknown Source)
    at fiftyone.mobile.detection.Provider.match(Unknown Source)
    at com.gamesworkshop.device.detection.FiftyOneDeviceDetector.detectDeviceType(FiftyOneDeviceDetector.java:30)

    We've not made any changes to our codebase around 51degrees recently, so we're a little unsure to why it would suddenly be failing. Has there been any changes on your end recently that could be causing us problems?

    Thanks

    Greg

    0

    Mike



    Basic Member


    Posts:147
    Basic Member


    --
    16 Feb 2016 04:09 PM
    Hi Greg,

    Thank you for reporting this issue.

    No, as far as the automatic updates are concerned we have not altered the URL. We have been working on updating the API over the last few months but that should not interfere with the existing implementations.

    We did have a few brief periods of service disruptions recently due to issues with the underlying Microsoft Azure infrastructure which could have influenced the automatic updates for some customers.

    Which version of the API do you use? The second issue could have been caused if you used the V3.2 data file with a 3.1 API as the data files are very similar but have some key differences in the data structure. So a 3.2 data file could hypothetically be loaded by the 3.1 API but would not work properly.

    Kind regards,
    Mike
    0

    Gerhard



    New Member


    Posts:1
    New Member


    --
    03 Aug 2016 11:00 AM
    Hi Greg,

    this error comes because your java client is not able to handle SNI handshakes. SNI is available since Java 1.7:
    http://docs.oracle.com/javase/7/doc...nts-7.html
    Server Name Indication (SNI) for JSSE client: The Java SE 7 release supports the Server Name Indication (SNI) extension in the JSSE client. SNI is described in RFC 4366. This enables TLS clients to connect to virtual servers.

    Most likely afterwards you will fail again, because the certificate which 51degrees.com is using is from a (java) untrusted CA godaddy. You can check http://tozny.com/blog/godaddys-ssl-...-solution/ to solve this.
    0
    You are not authorized to post a reply.