License server communication problem: E_ADEPT_INTERNAL ??

Question

When our customer downloads an epub link created by the adobe content server:
http://acs.riverwatcher.com:8080/fulfillment/URLLink.acsm?action=enterorder&ordersource=Sa gamore+Publishing+Store&orderid=1069267236_0&resid=urn%3Auuid%3A183e17c3-e5e3-43d9-8fde-ac c0177050b2&gbauthdate=09%2F27%2F2010+18%3A54+UTC&dateval=1285613645&gblver=4&auth=94ae7877 0104329ba549893bdff875f8e4582d1a
This allows them to open or save the following URLink.ascm file:
<fulfillmentToken fulfillmentType="buy" xmlns="http://ns.adobe.com/adept">
  <distributor>urn:uuid:c58286f7-2655-4df5-8b63-912344f3ffe3</distributor>
  <operatorURL>http://acs.riverwatcher.com:8080/fulfillment</operatorURL>
  <expiration>2010-09-07T11:37:34-04:00</expiration>
  <transaction>123456789</transaction>
  <resourceItemInfo>
    <resource>urn:uuid:7763a743-4a7d-4153-b0c4-5bccaec539a2</resource>
    <resourceItem>1</resourceItem>
    <metadata>
      <dc:title xmlns:dc="http://purl.org/dc/elements/1.1/">
  Edgar Poe, sa vie et ses oeuvres
</dc:title>
      <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">
  Baudelaire, Charles
</dc:creator>
      <dc:format xmlns:dc="http://purl.org/dc/elements/1.1/">application/epub+zip</dc:format>
      <dc:publisher xmlns:dc="http://purl.org/dc/elements/1.1/">
  Feedbooks (www.feedbooks.com)
</dc:publisher>
<dc:language xmlns:dc="http://purl.org/dc/elements/1.1/">
  fr
</dc:language>
      <dc:description xmlns:dc="http://purl.org/dc/elements/1.1/"></dc:description>
      <dc:identifier xmlns:dc="http://purl.org/dc/elements/1.1/">
  urn:uuid:5f652f06-2d90-11dd-804a-001cc049a027
</dc:identifier>
    </metadata>
    <src>http://acs.riverwatcher.com:8080/media/7763a743-4a7d-4153-b0c4-5bccaec539a2.epub</src>
    <downloadType>simple</downloadType>
  </resourceItemInfo>
  <hmac>c/D6CH3gm/2EAw54j0AwM7FDG74=</hmac>
</fulfillmentToken>
They receive the following error in Adobe Digital Editions:
Error getting license
License server communication problem: E_ADEPT_INTERNAL
Here is the log from our acs server:
java.lang.NullPointerException
    at java.io.ByteArrayInputStream.<init>(ByteArrayInputStream.java:106)
    at com.adobe.adept.shared.request.LicenseToken.<init>(LicenseToken.java:100)
   at com.adobe.adept.fulfillment.servlet.Fulfill.writeLicense(Fulfill.java:979)
    at com.adobe.adept.fulfillment.servlet.Fulfill.doPost(Fulfill.java:1137)
    at com.adobe.adept.fulfillment.servlet.Fulfill.doPost(Fulfill.java:73)
    at com.adobe.adept.servlet.AdeptServlet.doPost(AdeptServlet.java:184)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.j ava:290)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
    at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:852)
    at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.ja va:588)
    at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
    at java.lang.Thread.run(Thread.java:636)
Please advise, any help you can provide would be very helpful.  This is only happening with a select few of the books I packaged into the acs server.  Using the exact same packaging and fulfillment process works fine for many of the pdfs we uploaded.  There does not seem to be any common thread among the ones that fail vs. the ones that do not fail.
Things we have tried:
* Renaming the file  prior to upload to have no spaces/special characters.
* deleting the product and trying again from scratch.
Has ANYONE seen this before?  Or have any idea what could be the cause?
Thank you in advance,
Joe

Answer 1

Is the transaction in the fulfillmentToken really '123456789' and not '1079267236_0'?
At a quick look the exception is that it is unable to create a license for this.  From memory the usual error for this is that the transaction is already recorded in the fulfillment table but there is no corresponding item in the license in the license table (join the user from the fulfillment table with the resource with the fulfillment item table - join is the fulfillmentid)
-jim