[jira] [Commented] (JUDDI-1005) Need To have correct options to upgrade JUDDI DB Schema
[
https://issues.apache.org/jira/browse/JUDDI-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17054192#comment-17054192
]
ASF subversion and git services commented on JUDDI-1005:
Commit a28db0a7a6f30a15bcdd588057a1cfb410a9ff28 in juddi's branch
refs/heads/master from Alex O'Ree
[ https://gitbox.apache.org/repos/asf?p=juddi.git;h=a28db0a ]
JUDDI-1003 updates spring web dependency
JUDDI-1005 related, fixes the distrubtion so that the executable jar for the
migration tool is included
NOJIRA minor jsp code cleanup
> Need To have correct options to upgrade JUDDI DB Schema
> ---
>
> Key: JUDDI-1005
> URL: https://issues.apache.org/jira/browse/JUDDI-1005
> Project: jUDDI
> Issue Type: Bug
> Components: juddi-tomcat
>Affects Versions: 3.3.6, 3.3.7
>Reporter: Amol Bhonsle
>Priority: Major
> Attachments:
> uddi-migration-tool-3.3.8-SNAPSHOT-jar-with-dependencies.jar
>
>
> We are trying to update JUDDI DB from JUDDI-3.0.4 to JUDDI-3.3.7. JUDDI DB is
> hosted on SQL Server. We use openjpa-2.3.0 which is provided by juddi-3.3.7
> distribution.
>
> As per openjpa-2.3.0 documentation:
> {{drop option of SchemaTool should do following:}}
> {{drop}}: Drop all schema components in the schema XML. Tables will only be
> dropped if they would have 0 columns after dropping all columns listed in the
> XML.
> and add option should do following:
> {{add}}: This is the default action if you do not specify one. It brings the
> schema up-to-date with the given XML document by adding tables, columns,
> indexes, etc. This action never drops any schema components.
> Also it is allowed in persistence.xml to use options as comma separated, so
> we tried following option in persistence.xml to drop old tables and create
> new tables as per juddi-3.3.7 schema but it did not work:
> value="buildSchema(SchemaAction='drop,add')"/>
>
> This gives following Exception when JUDDI is deployed by tomcat :
>
> {code:java}
> SEVERE: Exception sending context initialized event to listener instance of
> class org.springframework.web.context.ContextLoaderListenerSEVERE: Exception
> sending context initialized event to listener instance of class
> org.springframework.web.context.ContextLoaderListenerorg.springframework.beans.factory.BeanCreationException:
> Error creating bean with name 'inquiry': Cannot create inner bean '(inner
> bean)#fa6535a' of type [org.apache.juddi.api.impl.UDDIInquiryImpl] while
> setting constructor argument; nested exception is
> org.springframework.beans.factory.BeanCreationException: Error creating bean
> with name '(inner bean)#fa6535a': Instantiation of bean failed; nested
> exception is org.springframework.beans.BeanInstantiationException: Failed to
> instantiate [org.apache.juddi.api.impl.UDDIInquiryImpl]: Constructor threw
> exception; nested exception is general error> org.apache.openjpa.persistence.PersistenceException: The
> object 'PK__j3_clerk__5609ADDDCF01D08E' is dependent on column 'clerk_name'.
> \{stmnt 1807668378 ALTER TABLE j3_clerk DROP COLUMN clerk_name} [code=5074,
> state=S0001] at
> org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveInnerBean(BeanDefinitionValueResolver.java:389)
> at
> org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:134)
> at
> org.springframework.beans.factory.support.ConstructorResolver.resolveConstructorArguments(ConstructorResolver.java:691)
> at
> org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:196)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1358)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1204)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:557)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:517)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:323)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory$$Lambda$208/1654431226.getObject(Unknown
> Source) at
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:321)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.get
[jira] [Commented] (JUDDI-1005) Need To have correct options to upgrade JUDDI DB Schema
[
https://issues.apache.org/jira/browse/JUDDI-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17039614#comment-17039614
]
Alex O'Ree commented on JUDDI-1005:
---
it should be in
[uddi-client-distro-3.3.7.zip|http://apache.claz.org/juddi/juddi/3.3.7/uddi-client-distro-3.3.7.zip]
> Need To have correct options to upgrade JUDDI DB Schema
> ---
>
> Key: JUDDI-1005
> URL: https://issues.apache.org/jira/browse/JUDDI-1005
> Project: jUDDI
> Issue Type: Bug
> Components: juddi-tomcat
>Affects Versions: 3.3.6, 3.3.7
>Reporter: Amol Bhonsle
>Priority: Major
> Attachments:
> uddi-migration-tool-3.3.8-SNAPSHOT-jar-with-dependencies.jar
>
>
> We are trying to update JUDDI DB from JUDDI-3.0.4 to JUDDI-3.3.7. JUDDI DB is
> hosted on SQL Server. We use openjpa-2.3.0 which is provided by juddi-3.3.7
> distribution.
>
> As per openjpa-2.3.0 documentation:
> {{drop option of SchemaTool should do following:}}
> {{drop}}: Drop all schema components in the schema XML. Tables will only be
> dropped if they would have 0 columns after dropping all columns listed in the
> XML.
> and add option should do following:
> {{add}}: This is the default action if you do not specify one. It brings the
> schema up-to-date with the given XML document by adding tables, columns,
> indexes, etc. This action never drops any schema components.
> Also it is allowed in persistence.xml to use options as comma separated, so
> we tried following option in persistence.xml to drop old tables and create
> new tables as per juddi-3.3.7 schema but it did not work:
> value="buildSchema(SchemaAction='drop,add')"/>
>
> This gives following Exception when JUDDI is deployed by tomcat :
>
> {code:java}
> SEVERE: Exception sending context initialized event to listener instance of
> class org.springframework.web.context.ContextLoaderListenerSEVERE: Exception
> sending context initialized event to listener instance of class
> org.springframework.web.context.ContextLoaderListenerorg.springframework.beans.factory.BeanCreationException:
> Error creating bean with name 'inquiry': Cannot create inner bean '(inner
> bean)#fa6535a' of type [org.apache.juddi.api.impl.UDDIInquiryImpl] while
> setting constructor argument; nested exception is
> org.springframework.beans.factory.BeanCreationException: Error creating bean
> with name '(inner bean)#fa6535a': Instantiation of bean failed; nested
> exception is org.springframework.beans.BeanInstantiationException: Failed to
> instantiate [org.apache.juddi.api.impl.UDDIInquiryImpl]: Constructor threw
> exception; nested exception is general error> org.apache.openjpa.persistence.PersistenceException: The
> object 'PK__j3_clerk__5609ADDDCF01D08E' is dependent on column 'clerk_name'.
> \{stmnt 1807668378 ALTER TABLE j3_clerk DROP COLUMN clerk_name} [code=5074,
> state=S0001] at
> org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveInnerBean(BeanDefinitionValueResolver.java:389)
> at
> org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:134)
> at
> org.springframework.beans.factory.support.ConstructorResolver.resolveConstructorArguments(ConstructorResolver.java:691)
> at
> org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:196)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1358)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1204)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:557)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:517)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:323)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory$$Lambda$208/1654431226.getObject(Unknown
> Source) at
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:321)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:202)
> at
> org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:879)
> at
> org.springframework.context.support.AbstractApplicationContext.finishBeanFacto
[jira] [Commented] (JUDDI-1005) Need To have correct options to upgrade JUDDI DB Schema
[
https://issues.apache.org/jira/browse/JUDDI-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17039613#comment-17039613
]
Alex O'Ree commented on JUDDI-1005:
---
just attached the correct jar, sorry about that.
> Need To have correct options to upgrade JUDDI DB Schema
> ---
>
> Key: JUDDI-1005
> URL: https://issues.apache.org/jira/browse/JUDDI-1005
> Project: jUDDI
> Issue Type: Bug
> Components: juddi-tomcat
>Affects Versions: 3.3.6, 3.3.7
>Reporter: Amol Bhonsle
>Priority: Major
> Attachments:
> uddi-migration-tool-3.3.8-SNAPSHOT-jar-with-dependencies.jar
>
>
> We are trying to update JUDDI DB from JUDDI-3.0.4 to JUDDI-3.3.7. JUDDI DB is
> hosted on SQL Server. We use openjpa-2.3.0 which is provided by juddi-3.3.7
> distribution.
>
> As per openjpa-2.3.0 documentation:
> {{drop option of SchemaTool should do following:}}
> {{drop}}: Drop all schema components in the schema XML. Tables will only be
> dropped if they would have 0 columns after dropping all columns listed in the
> XML.
> and add option should do following:
> {{add}}: This is the default action if you do not specify one. It brings the
> schema up-to-date with the given XML document by adding tables, columns,
> indexes, etc. This action never drops any schema components.
> Also it is allowed in persistence.xml to use options as comma separated, so
> we tried following option in persistence.xml to drop old tables and create
> new tables as per juddi-3.3.7 schema but it did not work:
> value="buildSchema(SchemaAction='drop,add')"/>
>
> This gives following Exception when JUDDI is deployed by tomcat :
>
> {code:java}
> SEVERE: Exception sending context initialized event to listener instance of
> class org.springframework.web.context.ContextLoaderListenerSEVERE: Exception
> sending context initialized event to listener instance of class
> org.springframework.web.context.ContextLoaderListenerorg.springframework.beans.factory.BeanCreationException:
> Error creating bean with name 'inquiry': Cannot create inner bean '(inner
> bean)#fa6535a' of type [org.apache.juddi.api.impl.UDDIInquiryImpl] while
> setting constructor argument; nested exception is
> org.springframework.beans.factory.BeanCreationException: Error creating bean
> with name '(inner bean)#fa6535a': Instantiation of bean failed; nested
> exception is org.springframework.beans.BeanInstantiationException: Failed to
> instantiate [org.apache.juddi.api.impl.UDDIInquiryImpl]: Constructor threw
> exception; nested exception is general error> org.apache.openjpa.persistence.PersistenceException: The
> object 'PK__j3_clerk__5609ADDDCF01D08E' is dependent on column 'clerk_name'.
> \{stmnt 1807668378 ALTER TABLE j3_clerk DROP COLUMN clerk_name} [code=5074,
> state=S0001] at
> org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveInnerBean(BeanDefinitionValueResolver.java:389)
> at
> org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:134)
> at
> org.springframework.beans.factory.support.ConstructorResolver.resolveConstructorArguments(ConstructorResolver.java:691)
> at
> org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:196)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1358)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1204)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:557)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:517)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:323)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory$$Lambda$208/1654431226.getObject(Unknown
> Source) at
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:321)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:202)
> at
> org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:879)
> at
> org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:878)
> at
> org.sprin
[jira] [Commented] (JUDDI-1005) Need To have correct options to upgrade JUDDI DB Schema
[
https://issues.apache.org/jira/browse/JUDDI-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17039004#comment-17039004
]
Amol Bhonsle commented on JUDDI-1005:
-
Hi [~spyhunter99]
Can you help me here.
I checked documentation on Migration Tool on below link:
https://juddi.apache.org/docs/3.3/juddi-client-guide/pdf/jUDDI_Guide.pdf (
Chapter 8 on page 73) and also got uddi-migration-tool from
https://juddi.apache.org/uddi-client-dist/source-repository.html
When, I am trying to run it, I am getting error as "no main manifest attribute,
in uddi-migration-tool-3.3.7.jar". Am I using incorrect jar here ? document
talks about juddi-migration-tool-(VERSION)-jar-with-dependencies.jar which
seems to be a different file but I don't see it anywhere on apache site.
> Need To have correct options to upgrade JUDDI DB Schema
> ---
>
> Key: JUDDI-1005
> URL: https://issues.apache.org/jira/browse/JUDDI-1005
> Project: jUDDI
> Issue Type: Bug
> Components: juddi-tomcat
>Affects Versions: 3.3.6, 3.3.7
>Reporter: Amol Bhonsle
>Priority: Major
>
> We are trying to update JUDDI DB from JUDDI-3.0.4 to JUDDI-3.3.7. JUDDI DB is
> hosted on SQL Server. We use openjpa-2.3.0 which is provided by juddi-3.3.7
> distribution.
>
> As per openjpa-2.3.0 documentation:
> {{drop option of SchemaTool should do following:}}
> {{drop}}: Drop all schema components in the schema XML. Tables will only be
> dropped if they would have 0 columns after dropping all columns listed in the
> XML.
> and add option should do following:
> {{add}}: This is the default action if you do not specify one. It brings the
> schema up-to-date with the given XML document by adding tables, columns,
> indexes, etc. This action never drops any schema components.
> Also it is allowed in persistence.xml to use options as comma separated, so
> we tried following option in persistence.xml to drop old tables and create
> new tables as per juddi-3.3.7 schema but it did not work:
> value="buildSchema(SchemaAction='drop,add')"/>
>
> This gives following Exception when JUDDI is deployed by tomcat :
>
> {code:java}
> SEVERE: Exception sending context initialized event to listener instance of
> class org.springframework.web.context.ContextLoaderListenerSEVERE: Exception
> sending context initialized event to listener instance of class
> org.springframework.web.context.ContextLoaderListenerorg.springframework.beans.factory.BeanCreationException:
> Error creating bean with name 'inquiry': Cannot create inner bean '(inner
> bean)#fa6535a' of type [org.apache.juddi.api.impl.UDDIInquiryImpl] while
> setting constructor argument; nested exception is
> org.springframework.beans.factory.BeanCreationException: Error creating bean
> with name '(inner bean)#fa6535a': Instantiation of bean failed; nested
> exception is org.springframework.beans.BeanInstantiationException: Failed to
> instantiate [org.apache.juddi.api.impl.UDDIInquiryImpl]: Constructor threw
> exception; nested exception is general error> org.apache.openjpa.persistence.PersistenceException: The
> object 'PK__j3_clerk__5609ADDDCF01D08E' is dependent on column 'clerk_name'.
> \{stmnt 1807668378 ALTER TABLE j3_clerk DROP COLUMN clerk_name} [code=5074,
> state=S0001] at
> org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveInnerBean(BeanDefinitionValueResolver.java:389)
> at
> org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:134)
> at
> org.springframework.beans.factory.support.ConstructorResolver.resolveConstructorArguments(ConstructorResolver.java:691)
> at
> org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:196)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1358)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1204)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:557)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:517)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:323)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory$$Lambda$208/1654431226.getObject(Unknown
> Source) at
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
> at
> org.springframework.beans.factory
[jira] [Commented] (JUDDI-1005) Need To have correct options to upgrade JUDDI DB Schema
[
https://issues.apache.org/jira/browse/JUDDI-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17038330#comment-17038330
]
Alex O'Ree commented on JUDDI-1005:
---
the migration tool will backup and uddi server and restore it to another. if
the jpa update mechanism fails, then this is the only mechanism i am aware of.
start juddi 304
run the migration tool is backup mode
stop juddi
drop the tables/databases
start the new juddi
run the migration tool in restore mode
obviously, take a snapshot t or backup first
[~kurt.s...@gmail.com] have any other ideas? i can't even get 304 to start up
with mssql, different jpa error...
> Need To have correct options to upgrade JUDDI DB Schema
> ---
>
> Key: JUDDI-1005
> URL: https://issues.apache.org/jira/browse/JUDDI-1005
> Project: jUDDI
> Issue Type: Bug
> Components: juddi-tomcat
>Affects Versions: 3.3.6, 3.3.7
>Reporter: Amol Bhonsle
>Priority: Major
>
> We are trying to update JUDDI DB from JUDDI-3.0.4 to JUDDI-3.3.7. JUDDI DB is
> hosted on SQL Server. We use openjpa-2.3.0 which is provided by juddi-3.3.7
> distribution.
>
> As per openjpa-2.3.0 documentation:
> {{drop option of SchemaTool should do following:}}
> {{drop}}: Drop all schema components in the schema XML. Tables will only be
> dropped if they would have 0 columns after dropping all columns listed in the
> XML.
> and add option should do following:
> {{add}}: This is the default action if you do not specify one. It brings the
> schema up-to-date with the given XML document by adding tables, columns,
> indexes, etc. This action never drops any schema components.
> Also it is allowed in persistence.xml to use options as comma separated, so
> we tried following option in persistence.xml to drop old tables and create
> new tables as per juddi-3.3.7 schema but it did not work:
> value="buildSchema(SchemaAction='drop,add')"/>
>
> This gives following Exception when JUDDI is deployed by tomcat :
>
> {code:java}
> SEVERE: Exception sending context initialized event to listener instance of
> class org.springframework.web.context.ContextLoaderListenerSEVERE: Exception
> sending context initialized event to listener instance of class
> org.springframework.web.context.ContextLoaderListenerorg.springframework.beans.factory.BeanCreationException:
> Error creating bean with name 'inquiry': Cannot create inner bean '(inner
> bean)#fa6535a' of type [org.apache.juddi.api.impl.UDDIInquiryImpl] while
> setting constructor argument; nested exception is
> org.springframework.beans.factory.BeanCreationException: Error creating bean
> with name '(inner bean)#fa6535a': Instantiation of bean failed; nested
> exception is org.springframework.beans.BeanInstantiationException: Failed to
> instantiate [org.apache.juddi.api.impl.UDDIInquiryImpl]: Constructor threw
> exception; nested exception is general error> org.apache.openjpa.persistence.PersistenceException: The
> object 'PK__j3_clerk__5609ADDDCF01D08E' is dependent on column 'clerk_name'.
> \{stmnt 1807668378 ALTER TABLE j3_clerk DROP COLUMN clerk_name} [code=5074,
> state=S0001] at
> org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveInnerBean(BeanDefinitionValueResolver.java:389)
> at
> org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:134)
> at
> org.springframework.beans.factory.support.ConstructorResolver.resolveConstructorArguments(ConstructorResolver.java:691)
> at
> org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:196)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1358)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1204)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:557)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:517)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:323)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory$$Lambda$208/1654431226.getObject(Unknown
> Source) at
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:321)
> at
> org.springframework.beans.factory.support.AbstractBeanFac
[jira] [Commented] (JUDDI-1005) Need To have correct options to upgrade JUDDI DB Schema
[
https://issues.apache.org/jira/browse/JUDDI-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17038099#comment-17038099
]
Amol Bhonsle commented on JUDDI-1005:
-
Yes [~spyhunter99], that is correct. Everything is fine for JUDDI-3.0.4.
upgrade attempt from 3.0.4 to 3.3.7 does not go through. We tried to follow
steps as per documentation of Open JPA 2.3.0 but JUDDI DB schema does not
update accordingly.
As I mentioned in description, we tried following option in persistence.xml as
per guidelines from OpenJPA
this drops tables of JUDDI-3.0.4 but does not recreate when tomcat comes up and
deploy JUDDI with version 3.3.7.
I have gone through documentation for uddi migration tool but did not get any
way to get this done. Can you help me here if I missed any specific step which
will update DB for JUDDI ?
I know we can have a manual step to drop tables of JUDDI-3.0.4 and when tomcat
will come up, as per schema definitions of 3.3.7, new tables will get created,
but we cannot drop tables manually as we have multi-client and dynamic
deployment kind of product.
> Need To have correct options to upgrade JUDDI DB Schema
> ---
>
> Key: JUDDI-1005
> URL: https://issues.apache.org/jira/browse/JUDDI-1005
> Project: jUDDI
> Issue Type: Bug
> Components: juddi-tomcat
>Affects Versions: 3.3.6, 3.3.7
>Reporter: Amol Bhonsle
>Priority: Major
>
> We are trying to update JUDDI DB from JUDDI-3.0.4 to JUDDI-3.3.7. JUDDI DB is
> hosted on SQL Server. We use openjpa-2.3.0 which is provided by juddi-3.3.7
> distribution.
>
> As per openjpa-2.3.0 documentation:
> {{drop option of SchemaTool should do following:}}
> {{drop}}: Drop all schema components in the schema XML. Tables will only be
> dropped if they would have 0 columns after dropping all columns listed in the
> XML.
> and add option should do following:
> {{add}}: This is the default action if you do not specify one. It brings the
> schema up-to-date with the given XML document by adding tables, columns,
> indexes, etc. This action never drops any schema components.
> Also it is allowed in persistence.xml to use options as comma separated, so
> we tried following option in persistence.xml to drop old tables and create
> new tables as per juddi-3.3.7 schema but it did not work:
> value="buildSchema(SchemaAction='drop,add')"/>
>
> This gives following Exception when JUDDI is deployed by tomcat :
>
> {code:java}
> SEVERE: Exception sending context initialized event to listener instance of
> class org.springframework.web.context.ContextLoaderListenerSEVERE: Exception
> sending context initialized event to listener instance of class
> org.springframework.web.context.ContextLoaderListenerorg.springframework.beans.factory.BeanCreationException:
> Error creating bean with name 'inquiry': Cannot create inner bean '(inner
> bean)#fa6535a' of type [org.apache.juddi.api.impl.UDDIInquiryImpl] while
> setting constructor argument; nested exception is
> org.springframework.beans.factory.BeanCreationException: Error creating bean
> with name '(inner bean)#fa6535a': Instantiation of bean failed; nested
> exception is org.springframework.beans.BeanInstantiationException: Failed to
> instantiate [org.apache.juddi.api.impl.UDDIInquiryImpl]: Constructor threw
> exception; nested exception is general error> org.apache.openjpa.persistence.PersistenceException: The
> object 'PK__j3_clerk__5609ADDDCF01D08E' is dependent on column 'clerk_name'.
> \{stmnt 1807668378 ALTER TABLE j3_clerk DROP COLUMN clerk_name} [code=5074,
> state=S0001] at
> org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveInnerBean(BeanDefinitionValueResolver.java:389)
> at
> org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:134)
> at
> org.springframework.beans.factory.support.ConstructorResolver.resolveConstructorArguments(ConstructorResolver.java:691)
> at
> org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:196)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1358)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1204)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:557)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:517)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFa
[jira] [Commented] (JUDDI-1005) Need To have correct options to upgrade JUDDI DB Schema
[
https://issues.apache.org/jira/browse/JUDDI-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17037327#comment-17037327
]
Alex O'Ree commented on JUDDI-1005:
---
just to confirm, everything was working with juddi 3.0.4 and after an attempted
upgrade, most of the tables are gone?
It may be easier to use the uddi migration tool. it's included with the more
recent distributions, 3.2 or newer i believe. it's a command line tool that
exports content from one registry to another.
> Need To have correct options to upgrade JUDDI DB Schema
> ---
>
> Key: JUDDI-1005
> URL: https://issues.apache.org/jira/browse/JUDDI-1005
> Project: jUDDI
> Issue Type: Bug
> Components: juddi-tomcat
>Affects Versions: 3.3.6, 3.3.7
>Reporter: Amol Bhonsle
>Priority: Major
>
> We are trying to update JUDDI DB from JUDDI-3.0.4 to JUDDI-3.3.7. JUDDI DB is
> hosted on SQL Server. We use openjpa-2.3.0 which is provided by juddi-3.3.7
> distribution.
>
> As per openjpa-2.3.0 documentation:
> {{drop option of SchemaTool should do following:}}
> {{drop}}: Drop all schema components in the schema XML. Tables will only be
> dropped if they would have 0 columns after dropping all columns listed in the
> XML.
> and add option should do following:
> {{add}}: This is the default action if you do not specify one. It brings the
> schema up-to-date with the given XML document by adding tables, columns,
> indexes, etc. This action never drops any schema components.
> Also it is allowed in persistence.xml to use options as comma separated, so
> we tried following option in persistence.xml to drop old tables and create
> new tables as per juddi-3.3.7 schema but it did not work:
> value="buildSchema(SchemaAction='drop,add')"/>
>
> This gives following Exception when JUDDI is deployed by tomcat :
>
> {code:java}
> SEVERE: Exception sending context initialized event to listener instance of
> class org.springframework.web.context.ContextLoaderListenerSEVERE: Exception
> sending context initialized event to listener instance of class
> org.springframework.web.context.ContextLoaderListenerorg.springframework.beans.factory.BeanCreationException:
> Error creating bean with name 'inquiry': Cannot create inner bean '(inner
> bean)#fa6535a' of type [org.apache.juddi.api.impl.UDDIInquiryImpl] while
> setting constructor argument; nested exception is
> org.springframework.beans.factory.BeanCreationException: Error creating bean
> with name '(inner bean)#fa6535a': Instantiation of bean failed; nested
> exception is org.springframework.beans.BeanInstantiationException: Failed to
> instantiate [org.apache.juddi.api.impl.UDDIInquiryImpl]: Constructor threw
> exception; nested exception is general error> org.apache.openjpa.persistence.PersistenceException: The
> object 'PK__j3_clerk__5609ADDDCF01D08E' is dependent on column 'clerk_name'.
> \{stmnt 1807668378 ALTER TABLE j3_clerk DROP COLUMN clerk_name} [code=5074,
> state=S0001] at
> org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveInnerBean(BeanDefinitionValueResolver.java:389)
> at
> org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:134)
> at
> org.springframework.beans.factory.support.ConstructorResolver.resolveConstructorArguments(ConstructorResolver.java:691)
> at
> org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:196)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1358)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1204)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:557)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:517)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:323)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory$$Lambda$208/1654431226.getObject(Unknown
> Source) at
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:321)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:202)
> at
> org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListab
[jira] [Commented] (JUDDI-1005) Need To have correct options to upgrade JUDDI DB Schema
[
https://issues.apache.org/jira/browse/JUDDI-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17035909#comment-17035909
]
Amol Bhonsle commented on JUDDI-1005:
-
We are on jdk 8 already. Afterwards we attempted to upgrade from juddi-3.0.4 to
juddi-3.3.7.
I also see only two JUDDI tables i.e. j3_clerk and j3_node getting created in
database, along with Exception which I mentioned in description.
> Need To have correct options to upgrade JUDDI DB Schema
> ---
>
> Key: JUDDI-1005
> URL: https://issues.apache.org/jira/browse/JUDDI-1005
> Project: jUDDI
> Issue Type: Bug
> Components: juddi-tomcat
>Affects Versions: 3.3.6, 3.3.7
>Reporter: Amol Bhonsle
>Priority: Major
>
> We are trying to update JUDDI DB from JUDDI-3.0.4 to JUDDI-3.3.7. JUDDI DB is
> hosted on SQL Server. We use openjpa-2.3.0 which is provided by juddi-3.3.7
> distribution.
>
> As per openjpa-2.3.0 documentation:
> {{drop option of SchemaTool should do following:}}
> {{drop}}: Drop all schema components in the schema XML. Tables will only be
> dropped if they would have 0 columns after dropping all columns listed in the
> XML.
> and add option should do following:
> {{add}}: This is the default action if you do not specify one. It brings the
> schema up-to-date with the given XML document by adding tables, columns,
> indexes, etc. This action never drops any schema components.
> Also it is allowed in persistence.xml to use options as comma separated, so
> we tried following option in persistence.xml to drop old tables and create
> new tables as per juddi-3.3.7 schema but it did not work:
> value="buildSchema(SchemaAction='drop,add')"/>
>
> This gives following Exception when JUDDI is deployed by tomcat :
>
> SEVERE: Exception sending context initialized event to listener instance of
> class org.springframework.web.context.ContextLoaderListenerSEVERE: Exception
> sending context initialized event to listener instance of class
> org.springframework.web.context.ContextLoaderListenerorg.springframework.beans.factory.BeanCreationException:
> Error creating bean with name 'inquiry': Cannot create inner bean '(inner
> bean)#fa6535a' of type [org.apache.juddi.api.impl.UDDIInquiryImpl] while
> setting constructor argument; nested exception is
> org.springframework.beans.factory.BeanCreationException: Error creating bean
> with name '(inner bean)#fa6535a': Instantiation of bean failed; nested
> exception is org.springframework.beans.BeanInstantiationException: Failed to
> instantiate [org.apache.juddi.api.impl.UDDIInquiryImpl]: Constructor threw
> exception; nested exception is general error> org.apache.openjpa.persistence.PersistenceException: The
> object 'PK__j3_clerk__5609ADDDCF01D08E' is dependent on column 'clerk_name'.
> \{stmnt 1807668378 ALTER TABLE j3_clerk DROP COLUMN clerk_name} [code=5074,
> state=S0001] at
> org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveInnerBean(BeanDefinitionValueResolver.java:389)
> at
> org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:134)
> at
> org.springframework.beans.factory.support.ConstructorResolver.resolveConstructorArguments(ConstructorResolver.java:691)
> at
> org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:196)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1358)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1204)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:557)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:517)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:323)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory$$Lambda$208/1654431226.getObject(Unknown
> Source) at
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:321)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:202)
> at
> org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:879)
> at
> org.springframework.context.support.AbstractApplicationConte
[jira] [Commented] (JUDDI-1005) Need To have correct options to upgrade JUDDI DB Schema
[
https://issues.apache.org/jira/browse/JUDDI-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17035891#comment-17035891
]
Alex O'Ree commented on JUDDI-1005:
---
juddi 3.0.4 is super old at this point. i have attempted to recreate the issue
using jdk7, juddi 3.0.4 and sqlserver express v14 with the mssql driver v7 as
it was the last version that supported jdk7. i get this after hitting the juddi
splash page
org.apache.openjpa.lib.jdbc.ReportingSQLException: Invalid object name
'j3_publisher'. \{prepstmnt 1165479944 SELECT t0.email_address, t0.is_admin,
t0.is_enabled, t0.max_bindings_per_service, t0.max_businesses,
t0.max_services_per_business, t0.max_tmodels, t0.publisher_name FROM
j3_publisher t0 WHERE t0.authorized_name = ? [params=(String) root]} [code=208,
state=S0002]
and after checking mssql, only two tables are created that were related to
addresses. if you have any hints for getting 3.0.4 to work or have differences
in your environment, please comment back
> Need To have correct options to upgrade JUDDI DB Schema
> ---
>
> Key: JUDDI-1005
> URL: https://issues.apache.org/jira/browse/JUDDI-1005
> Project: jUDDI
> Issue Type: Bug
> Components: juddi-tomcat
>Affects Versions: 3.3.6, 3.3.7
>Reporter: Amol Bhonsle
>Priority: Major
>
> We are trying to update JUDDI DB from JUDDI-3.0.4 to JUDDI-3.3.7. JUDDI DB is
> hosted on SQL Server. We use openjpa-2.3.0 which is provided by juddi-3.3.7
> distribution.
>
> As per openjpa-2.3.0 documentation:
> {{drop option of SchemaTool should do following:}}
> {{drop}}: Drop all schema components in the schema XML. Tables will only be
> dropped if they would have 0 columns after dropping all columns listed in the
> XML.
> and add option should do following:
> {{add}}: This is the default action if you do not specify one. It brings the
> schema up-to-date with the given XML document by adding tables, columns,
> indexes, etc. This action never drops any schema components.
> Also it is allowed in persistence.xml to use options as comma separated, so
> we tried following option in persistence.xml to drop old tables and create
> new tables as per juddi-3.3.7 schema but it did not work:
> value="buildSchema(SchemaAction='drop,add')"/>
>
> This gives following Exception when JUDDI is deployed by tomcat :
>
> SEVERE: Exception sending context initialized event to listener instance of
> class org.springframework.web.context.ContextLoaderListenerSEVERE: Exception
> sending context initialized event to listener instance of class
> org.springframework.web.context.ContextLoaderListenerorg.springframework.beans.factory.BeanCreationException:
> Error creating bean with name 'inquiry': Cannot create inner bean '(inner
> bean)#fa6535a' of type [org.apache.juddi.api.impl.UDDIInquiryImpl] while
> setting constructor argument; nested exception is
> org.springframework.beans.factory.BeanCreationException: Error creating bean
> with name '(inner bean)#fa6535a': Instantiation of bean failed; nested
> exception is org.springframework.beans.BeanInstantiationException: Failed to
> instantiate [org.apache.juddi.api.impl.UDDIInquiryImpl]: Constructor threw
> exception; nested exception is general error> org.apache.openjpa.persistence.PersistenceException: The
> object 'PK__j3_clerk__5609ADDDCF01D08E' is dependent on column 'clerk_name'.
> \{stmnt 1807668378 ALTER TABLE j3_clerk DROP COLUMN clerk_name} [code=5074,
> state=S0001] at
> org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveInnerBean(BeanDefinitionValueResolver.java:389)
> at
> org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:134)
> at
> org.springframework.beans.factory.support.ConstructorResolver.resolveConstructorArguments(ConstructorResolver.java:691)
> at
> org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:196)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1358)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1204)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:557)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:517)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:323)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory$$Lambda$208/165
[jira] [Commented] (JUDDI-1005) Need To have correct options to upgrade JUDDI DB Schema
[
https://issues.apache.org/jira/browse/JUDDI-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17035870#comment-17035870
]
Alex O'Ree commented on JUDDI-1005:
---
thanks for the report, i'll look into it as soon as possible
> Need To have correct options to upgrade JUDDI DB Schema
> ---
>
> Key: JUDDI-1005
> URL: https://issues.apache.org/jira/browse/JUDDI-1005
> Project: jUDDI
> Issue Type: Bug
> Components: juddi-tomcat
>Affects Versions: 3.3.6, 3.3.7
>Reporter: Amol Bhonsle
>Priority: Major
>
> We are trying to update JUDDI DB from JUDDI-3.0.4 to JUDDI-3.3.7. JUDDI DB is
> hosted on SQL Server. We use openjpa-2.3.0 which is provided by juddi-3.3.7
> distribution.
>
> As per openjpa-2.3.0 documentation:
> {{drop option of SchemaTool should do following:}}
> {{drop}}: Drop all schema components in the schema XML. Tables will only be
> dropped if they would have 0 columns after dropping all columns listed in the
> XML.
> and add option should do following:
> {{add}}: This is the default action if you do not specify one. It brings the
> schema up-to-date with the given XML document by adding tables, columns,
> indexes, etc. This action never drops any schema components.
> Also it is allowed in persistence.xml to use options as comma separated, so
> we tried following option in persistence.xml to drop old tables and create
> new tables as per juddi-3.3.7 schema but it did not work:
> value="buildSchema(SchemaAction='drop,add')"/>
>
> This gives following Exception when JUDDI is deployed by tomcat :
>
> SEVERE: Exception sending context initialized event to listener instance of
> class org.springframework.web.context.ContextLoaderListenerSEVERE: Exception
> sending context initialized event to listener instance of class
> org.springframework.web.context.ContextLoaderListenerorg.springframework.beans.factory.BeanCreationException:
> Error creating bean with name 'inquiry': Cannot create inner bean '(inner
> bean)#fa6535a' of type [org.apache.juddi.api.impl.UDDIInquiryImpl] while
> setting constructor argument; nested exception is
> org.springframework.beans.factory.BeanCreationException: Error creating bean
> with name '(inner bean)#fa6535a': Instantiation of bean failed; nested
> exception is org.springframework.beans.BeanInstantiationException: Failed to
> instantiate [org.apache.juddi.api.impl.UDDIInquiryImpl]: Constructor threw
> exception; nested exception is general error> org.apache.openjpa.persistence.PersistenceException: The
> object 'PK__j3_clerk__5609ADDDCF01D08E' is dependent on column 'clerk_name'.
> \{stmnt 1807668378 ALTER TABLE j3_clerk DROP COLUMN clerk_name} [code=5074,
> state=S0001] at
> org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveInnerBean(BeanDefinitionValueResolver.java:389)
> at
> org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:134)
> at
> org.springframework.beans.factory.support.ConstructorResolver.resolveConstructorArguments(ConstructorResolver.java:691)
> at
> org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:196)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1358)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1204)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:557)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:517)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:323)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory$$Lambda$208/1654431226.getObject(Unknown
> Source) at
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:321)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:202)
> at
> org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:879)
> at
> org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:878)
> at
> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.ja
