LSO: Java errors when using Authoring Environment to check-in eLearning

Question

Have any users here encountered any of these Java errors when trying to check-in eLearning content to the Master Repository?
reuseObj is null
java.lang.NullPointerException: reuseObj is null
     at com.sap.hcm.ls.shared.repository.exchange.DeltaVersionData.<init>(DeltaVersionData.java:62)
     at com.sap.hcm.ls.shared.repository.exchange.CopyMan.checkIn(CopyMan.java:160)
     at com.sap.hcm.ls.shared.repository.exchange.Publisher.checkInObjects(Publisher.java:270)
     at com.sap.hcm.ls.las.repository.explorer.wizard.steps.CheckInObjectsStep.workerThread(CheckInObjectsStep.java:85)
     at com.sap.hcm.ls.shared.util.swing.wizardfw.steps.ProgressWizardStep.run(ProgressWizardStep.java:209)
     at java.lang.Thread.run(Unknown Source)
No semaphore for: /<path>/_groupManProps.txt
java.io.IOException: No semaphore for: /<path>/_groupManProps.txt
     at com.sap.hcm.ls.shared.repository.control.implicit.ImpVersManager.getAndUpdateNextRevisionNumberForGroup(ImpVersManager.java:920)
     at com.sap.hcm.ls.shared.repository.control.implicit.ImpVersManager.postSpecifyRevisionNumber(ImpVersManager.java:624)
     at com.sap.hcm.ls.shared.repository.exchange.CopyMan.copyProps(CopyMan.java:867)
     at com.sap.hcm.ls.shared.repository.exchange.CopyMan.checkIn(CopyMan.java:227)
     at com.sap.hcm.ls.shared.repository.exchange.Publisher.checkInObjects(Publisher.java:270)
     at com.sap.hcm.ls.las.repository.explorer.wizard.steps.CheckInObjectsStep.workerThread(CheckInObjectsStep.java:85)
     at com.sap.hcm.ls.shared.util.swing.wizardfw.steps.ProgressWizardStep.run(ProgressWizardStep.java:209)
     at java.lang.Thread.run(Thread.java:619)
Unexpected object state: /<path>/v1/ [rep=http://<path>:80/publishing/LSO_SH1/, type=4, props={status=reserved, type=4, isVersioned=m, pathHash=1855656709}]
com.sap.hcm.ls.shared.repository.access.ConcurrentIOException: Unexpected object state: /<path>/v1/ [rep=http://<path>:80/publishing/LSO_SH1/, type=4, props={status=reserved, type=4, isVersioned=m, pathHash=1855656709}]
     at com.sap.hcm.ls.shared.repository.exchange.Publisher.announceToPublisherDB(Publisher.java:733)
     at com.sap.hcm.ls.shared.repository.exchange.Publisher.checkInObjects(Publisher.java:288)
     at com.sap.hcm.ls.las.repository.explorer.wizard.steps.CheckInObjectsStep.workerThread(CheckInObjectsStep.java:85)
     at com.sap.hcm.ls.shared.util.swing.wizardfw.steps.ProgressWizardStep.run(ProgressWizardStep.java:209)
     at java.lang.Thread.run(Thread.java:619)
They each seem to point to some degree or another to using Versioning, but I've gotten those errors whether the "Use Delta Versioning..." checkbox is checked or unchecked.  I do have the standard versioning settings set in the IMG, the standard delivered settings.  And it's referencing the same file, _groupManProps.txt, that doesn't exist in any of the packages I've tried to publish/check-in.  I've tried both AICC and SCORM content and I get the same errors.
We have an ECC6 system on EHP5, and using Authoring Environment version LSOAE09_0-10006103.
I'm running the Authoring Environment on a 64-bit Windows 7 PC.
I've tried to publish/check-in with the following versions of the Java SDK:
1.4.2 Update 13
1.4.2 Update 19 (the latest in 1.4.2 with a Windows installer available)
6 Update 14 (a colleague is using this version successfully with the AE)
6 Update 23
Each of those were the 32-bit versions after trying a 64-bit version of one (based on my PC's OS) and getting an unrelated 64-bit error.
I would appreciate any experience or wisdom any other users here have to share.
Thanks!
Jason
Edited by: jtrain on Nov 22, 2011 9:29 AM

Answer 1

It was an adjustment we made on our ISA 2006 server. Under
1. Open Array - Configurarion - General
2. Select Additional Security Policy - Configure Flood Mitigation
3. On the Flood Mitigations Tab, there are a number of flood mitigation settings that can be configured.
The setting we had to adjust is under the "Maximum HTTP requests per minute per IP address (Click on Edit)
Increase the  "Limit:"  setting. We set it to 1500 which resolved our problem.
4. Apply the policy and wait for the configuration to be updated on all array members ( may take several minutes)
Regards,