Tim, I build an out of the box 6.3, and before I did an "ant fresh_install" I removed all the tables from my database, but the fresh_install did not build all the tables. Do I have to start over with a new db?
Thanks! -Jose On Thu, Feb 13, 2020 at 1:10 PM Jose Blanco <[email protected]> wrote: > I did add the following, but did not think it would cause an issue: > > private String sessionStatus; > > > this gets initialized: > > sessionStatus = ""; > > > And these two methods: > > > > public void setSessionStatus(String info) > > > { > > > sessionStatus = info; > > > } > > > > > > > public String getSessionStatus() > > > { > > > return sessionStatus; > > > } > > > > > > On Thu, Feb 13, 2020 at 12:47 PM Tim Donohue <[email protected]> > wrote: > >> Jose, >> >> Have you customized the v6.3 "Context" class in some way? The error line >> numbers there do not seem to match up with the out-of-the-box DSpace 6.3 >> codebase. These are the error lines I'm talking about >> >> at org.dspace.core.Context.init(Context.java:173) >> at org.dspace.core.Context.<init>(Context.java:129) >> >> In the v6.3 codebase, lines #129 and #173 in the Context class are both >> empty lines: >> >> https://github.com/DSpace/DSpace/blob/dspace-6.3/dspace-api/src/main/java/org/dspace/core/Context.java#L129 >> >> https://github.com/DSpace/DSpace/blob/dspace-6.3/dspace-api/src/main/java/org/dspace/core/Context.java#L173 >> >> It's difficult to help you debug the issue here as it doesn't look like >> your Context class is the same as out-of-the-box DSpace 6.3. So, my >> immediate guess is that your customizations may be causing an issue here -- >> either customizations in the Context class, or some sort of database >> customizations or both. If you didn't mean to customize the Context class, >> then you might want to try and re-sync it with the one in DSpace 6.3. >> >> Tim >> >> ------------------------------ >> *From:* [email protected] <[email protected]> on >> behalf of Jose Blanco <[email protected]> >> *Sent:* Thursday, February 13, 2020 11:35 AM >> *To:* José Geraldo <[email protected]> >> *Cc:* DSpace Technical Support <[email protected]> >> *Subject:* Re: [dspace-tech] starting dspace 6.3 >> >> Still stuck on this issue. >> >> On Wed, Feb 12, 2020 at 3:16 PM Jose Blanco <[email protected]> wrote: >> >> The dspace.log does not have much info. I think the error happens when >> the code tries to do this: >> >> https://github.com/DSpace/DSpace/blob/dspace-6.3/dspace-api/src/main/java/org/dspace/core/Context.java#L160 >> >> Not sure why it was not able to get the db connection in: >> >> >> https://github.com/DSpace/DSpace/blob/dspace-6.3/dspace-api/src/main/java/org/dspace/core/Context.java#L160 >> >> I see I get the same error when I try this: >> >> *> /l1/dspace/repository/dev63/bin/dspace create-administrator* >> >> Exception: The schema validator returned: Could not determine type for: >> org.dspace.core.Context, at table: bitstreamformatregistry, for columns: >> [org.hibernate.mapping.Column(bfContext)] >> >> org.dspace.core.exception.DatabaseSchemaValidationException: The schema >> validator returned: Could not determine type for: org.dspace.core.Context, >> at table: bitstreamformatregistry, for columns: >> [org.hibernate.mapping.Column(bfContext)] >> at org.dspace.core.Context.init(Context.java:173) >> at org.dspace.core.Context.<init>(Context.java:129) >> at >> org.dspace.administer.CreateAdministrator.<init>(CreateAdministrator.java:101) >> at >> org.dspace.administer.CreateAdministrator.main(CreateAdministrator.java:70) >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> at >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) >> at >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) >> at java.lang.reflect.Method.invoke(Method.java:607) >> at >> org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:229) >> at org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:81) >> >> On Wed, Feb 12, 2020 at 2:58 PM José Geraldo <[email protected]> wrote: >> >> Check o dspace.log [dspace]/log/dspace.log >> >> >> >> Em qua., 12 de fev. de 2020 às 15:11, Jose Blanco <[email protected]> >> escreveu: >> >> I'm getting this error when trying to deploy webapp via tomcat: >> >> 2020-02-12 12:55:16,566 FATAL org.dspace.core.Context @ Cannot obtain the >> bean which provides a database connection. Check previous entries in the >> dspace.log to find why the db failed to initialize. The schema validator >> returned: Could not determine type for: org.dspace.core.Context, at table: >> bitstreamformatregistry, for columns: >> [org.hibernate.mapping.Column(bfContext)] >> >> >> Not sure what it means. >> >> -- >> All messages to this mailing list should adhere to the DuraSpace Code of >> Conduct: https://duraspace.org/about/policies/code-of-conduct/ >> --- >> You received this message because you are subscribed to the Google Groups >> "DSpace Technical Support" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/dspace-tech/CAK%3DKc-vQZL39XzwN8aGiAM03nQX57Rgk65V7_ioeA7Tw2MU0PA%40mail.gmail.com >> <https://groups.google.com/d/msgid/dspace-tech/CAK%3DKc-vQZL39XzwN8aGiAM03nQX57Rgk65V7_ioeA7Tw2MU0PA%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> >> >> >> -- >> At.te, >> >> José Geraldo >> >> -- >> All messages to this mailing list should adhere to the DuraSpace Code of >> Conduct: https://duraspace.org/about/policies/code-of-conduct/ >> --- >> You received this message because you are subscribed to the Google Groups >> "DSpace Technical Support" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/dspace-tech/CANP4ikQ3mj8hmqjA_92_Mhhq4vU9nFMeksJO14QoXwYQ22kTiw%40mail.gmail.com >> <https://groups.google.com/d/msgid/dspace-tech/CANP4ikQ3mj8hmqjA_92_Mhhq4vU9nFMeksJO14QoXwYQ22kTiw%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> >> -- >> All messages to this mailing list should adhere to the DuraSpace Code of >> Conduct: https://duraspace.org/about/policies/code-of-conduct/ >> --- >> You received this message because you are subscribed to the Google Groups >> "DSpace Technical Support" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/dspace-tech/CAK%3DKc-tx-Dk5FBEDhNinG-YmqUdSbdxqL0v5%2B4K7Kkv%3DdfFT1w%40mail.gmail.com >> <https://groups.google.com/d/msgid/dspace-tech/CAK%3DKc-tx-Dk5FBEDhNinG-YmqUdSbdxqL0v5%2B4K7Kkv%3DdfFT1w%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > -- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/ --- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/CAK%3DKc-sWoOQpecqUVheJPGFRL8uz8uryA3JQsSArVgi2p07%2B5Q%40mail.gmail.com.
