Thanks, Tim. That's mysterious, as this is definitely a fresh install--in
fact, it's the second fresh install of beta 5 after clearing all existing
dspace files on the server, as I figured an earlier beta 4 file might have
gotten copied in by accident during the first beta 5 install. I wonder if
something is stuck in a cache somewhere?
Clearing and replacing the spring folder with ant update *did* clear the
error, but now I'm getting a new one:
Caused by: org.hibernate.tool.schema.spi.SchemaManagementException:
Schema-validation: missing column [tilted] in table
[public.relationship_type]
at
org.hibernate.tool.schema.internal.AbstractSchemaValidator.validateTable(AbstractSchemaValidator.java:136)
at
org.hibernate.tool.schema.internal.GroupedSchemaValidatorImpl.validateTables(GroupedSchemaValidatorImpl.java:42)
at
org.hibernate.tool.schema.internal.AbstractSchemaValidator.performValidation(AbstractSchemaValidator.java:89)
at
org.hibernate.tool.schema.internal.AbstractSchemaValidator.doValidation(AbstractSchemaValidator.java:68)
at
org.hibernate.tool.schema.spi.SchemaManagementToolCoordinator.performDatabaseAction(SchemaManagementToolCoordinator.java:192)
at
org.hibernate.tool.schema.spi.SchemaManagementToolCoordinator.process(SchemaManagementToolCoordinator.java:73)
at
org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:320)
at
org.hibernate.boot.internal.SessionFactoryBuilderImpl.build(SessionFactoryBuilderImpl.java:462)
at
org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:708)
at
org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:724)
at
org.springframework.orm.hibernate5.LocalSessionFactoryBean.buildSessionFactory(LocalSessionFactoryBean.java:616)
at
org.springframework.orm.hibernate5.LocalSessionFactoryBean.afterPropertiesSet(LocalSessionFactoryBean.java:600)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1855)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1792)
... 178 more
It occurs to me I am still using the postgres database I created for beta
4. Has anything changed in the database structure since then?
Mateo
On Thursday, May 13, 2021 at 9:53:34 AM UTC-4 Tim Donohue wrote:
> Mateo,
>
> It sounds like something is "invalid" in your `config/spring/` directory
> in general....it could be that you have a config or two from Beta 4 that
> are now conflicting with your attempt to install Beta 5 over Beta 4.
>
> You might simply try removing that entire 'config/spring/' directory, and
> then reinstalling Beta 5 (via ant update), which should recreate that
> folder with the Beta 5 expected configurations.
>
> I will note this error doesn't appear in a fresh install of Beta
> 5....that's why I suspect it's something with the fact that you are trying
> to install Beta 5 over an existing Beta 4. Keep in mind that these Beta
> releases are not considered "stable" so they may or may not be easy to
> upgrade between....but, we are ensuring it will be possible to upgrade from
> DSpace 6.x to 7.0 final (once that's ready to go).
>
> Tim
> ------------------------------
> *From:* 'Mateo Palos' via DSpace Technical Support <
> [email protected]>
> *Sent:* Thursday, May 13, 2021 8:07 AM
> *To:* DSpace Technical Support <[email protected]>
> *Subject:* Re: [dspace-tech] Webapp deployment error in Dspace 7 beta 5
>
>
> Thanks, Mark. I do see that bean defined in that file, so I'm not sure
> what to make of that error.
>
> Has anyone had any success disabling this integration, or at least
> bypassing this check for startup? I tried commenting out the integration in
> external-services.xml, but that just yielded a similar error to the
> original NoSuchBeanDefinitionException error.
>
> Mateo
>
> On Tuesday, May 11, 2021 at 3:32:24 PM UTC-4 Mark H. Wood wrote:
>
> On Tue, May 11, 2021 at 10:06:46AM -0700, 'Mateo Palos' via DSpace
> Technical Support wrote:
> > I'm trying to troubleshoot an issue that occurs when I try to run the
> > Dspace 7 beta 5 backend. I was able to run the beta 4 with similar
> configs,
> > so I'm wondering what might be going on here.
>
> [snip]
>
> > 64 moreCaused by:
> > org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean
> > named 'maxRetry' availableat
>
> This is what I would check first. It should be defined near the
> bottom of 'config/spring/api/pubmed-integration.xml'.
> 'dspace-api/src/main/java/org/dspace/importer/external/service/components/AbstractRemoteMetadataSource.java'
>
>
> requests to have it injected via its constructor, and Spring is trying
> to instantiate it in order to do that.
>
> --
> Mark H. Wood
> Lead Technology Analyst
>
> University Library
> Indiana University - Purdue University Indianapolis
> 755 W. Michigan Street
> Indianapolis, IN 46202
> 317-274-0749 <(317)%20274-0749>
> www.ulib.iupui.edu
>
> --
> All messages to this mailing list should adhere to the 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/fadf638b-2993-4ffc-9f12-f12667905957n%40googlegroups.com
>
> <https://groups.google.com/d/msgid/dspace-tech/fadf638b-2993-4ffc-9f12-f12667905957n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
--
All messages to this mailing list should adhere to the 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/aabf4e49-b0a7-4b88-bdc4-5ab5edf864f1n%40googlegroups.com.
