On Wed, Apr 10, 2013 at 6:53 PM, Amandeep Kapila <[email protected]> wrote: > Thanks for all the information. I can't dare for Wheezy now with a production > server as I may bump into some bug issues. Its always wise to move a little > behind especially the OS.
Paradoxically, if you look at the number of bugs at this time in Squeeze and in Wheezy, the Squeeze number is significantly higher. The Wheezy number will now go down a bit and when Wheezy becomes stable, it will climb again. I don't question your general policy, but this case at this time happens to be an exception. > I think OpenJDK has some known issues with dspace and so Oracle/Sun version > is recommended in documentation. While installing mvn from repository found > out that another version of java is also installed and had to update the > alternatives to use sun version. demo.dspace.org has been running on on OpenJDK 7 since DSpace 1.8.2. I have been running on OpenJDK 6 since DSpace 1.5. All of it in production. No problems I encountered were really Java-related. With OpenJDK you have the comfort of the distribution watching security updates for you. I don't know how many system you maintain, but I'm surely happy for that comfort, because it scales. On Thu, Apr 11, 2013 at 6:30 AM, Amandeep Kapila <[email protected]> wrote: > Thanks, for the response to my problem. I have doubled my RAM but > still getting the error. I think I am missing on something, I am pasting > here the error messages from stacktrace here, > > java.io.IOException: No such file or directory > Java stacktrace [hide] > > java.io.IOException: No such file or directory > at java.io.UnixFileSystem.createFileExclusively(Native Method) > at java.io.File.createNewFile(File.java:900) > at edu.sdsc.grid.io.local.LocalFile.createNewFile(LocalFile.java:486) > at > org.dspace.storage.bitstore.BitstreamStorageManager.store(BitstreamStorageManager.java:300) > at org.dspace.content.Bitstream.create(Bitstream.java:205) > at org.dspace.content.Bundle.createBitstream(Bundle.java:384) > at org.dspace.content.Item.createSingleBitstream(Item.java:1404) > at org.dspace.submit.step.UploadStep.processUploadFile(UploadStep.java:500) > at org.dspace.submit.step.UploadStep.doProcessing(UploadStep.java:145) This one is not RAM-related. The problem is that DSpace doesn't have the permissions to create a file in the [dspace]/assetstore directory. You'll avoid a whole class of problems if you chown the whole dspace directory to the tomcat user (tomcat6 in Squeeze). The continuation error is also related to submission, so I'll assume for now that it's a manifestation of the same problem. Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette ------------------------------------------------------------------------------ Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
