I tried this tutorial, to get SSO working with JasperReports Server (JRS) 6.1.1 but I get the following Error in the JRS log:
2017-01-10 15:04:11,174 ERROR ContextLoader,localhost-startStop-1:331 - Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'filterChainProxy' defined in ServletContext resource
[/WEB-INF/applicationContext-security-web.xml]: Initialization of bean failed; nested exception is java.lang.NoClassDefFoundError:
com/jaspersoft/jasperserver/multipleTenancy/DefaultMultiTenancyConfiguration
I don't know exactly what multi tenancy means, something like I could use several domains?
And the JRS won't start anymore, what did I wrong?
Related
I Upgraded my project from Mule 2.2 to Mule 3.8,Project is working fine,But during starting of Mule Server i am getting "Several exceptions in logs when logging level is DEBUG".
[WrapperListener_start_runner] SpringRegistry - No bean named 'quartz:-948818277' is defined
org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'quartz:-948818277' is defined
[DEBUG] 2017-04-21 06:25:18.994 [WrapperListener_start_runner] SpringRegistry - No bean named 'endpoint.quartz.contestentsPhotoDelivery.task' is defined
org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'endpoint.quartz.contestentsPhotoDelivery.task' is defined
[DEBUG] 2017-04-21 06:25:19.024 [WrapperListener_start_runner] SpringRegistry - No bean named 'endpoint:24812436' is defined
org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'endpoint:24812436' is defined
[DEBUG] 2017-04-21 06:25:19.376 [WrapperListener_start_runner] SpringRegistry - No bean named 'vm:3767' is defined
org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'vm:3767' is defined
There are many more similar "No bean named" Exception, pls let me if you need more Info.Thanks!
During startup mule is looking for default connectors and beans, clustered components, etc. If they are not defined, it exceptions and knows that feature is not available or to use your values instead. This is normally handled in the background and you do not see it. You are getting these reports only because you steps Mule's log reporting up to DEBUG level which is giving you a view into some of the internal workings. This is not a worry and one of the reasons you do not bump Mule up to debug level reporting unless you really need to see what is going on because something is failing. One could argue that Mule should have put this normal execution level logging at TRACE level, but it is debatable.
When trying to authenticate an adapter using custom authenticator and login module, I am facing the following exception.
[ERROR ] FWLST0003E: ========= Failed starting project /CustomAuth [project CustomAuth]
Error creating bean with name 'taskManager' defined in URL [wsjar:file:/D:/worklight_workspace/WorklightServerConfig/shared/resources/worklight-jee-library-6.1.0.jar!/conf/core.xml]: Cannot resolve reference to bean 'worklightAuthenticationService' while setting bean property 'authenticationService'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'worklightAuthenticationService' defined in URL [wsjar:file:/D:/worklight_workspace/WorklightServerConfig/shared/resources/worklight-jee-library-6.1.0.jar!/conf/core.xml]: Cannot create inner bean 'com.worklight.core.auth.impl.LoginConfigurationServiceBean#7cffa209' of type [com.worklight.core.auth.impl.LoginConfigurationServiceBean] while setting bean property 'loginConfigurationService'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'com.worklight.core.auth.impl.LoginConfigurationServiceBean#7cffa209' defined in URL [wsjar:file:/D:/worklight_workspace/WorklightServerConfig/shared/resources/worklight-jee-library-6.1.0.jar!/conf/core.xml]: Invocation of init method failed; nested exception is java.lang.RuntimeException: Class 'com.mypackage.MyCustomLoginModule' defined in login module 'CustomLoginModule' in the authentication configuration file doesn't exist.
[AUDIT ] CWWKZ0001I: Application CustomAuth started in 0.948 seconds.
[ERROR ] SRVE0315E: An execption occurred: com.ibm.ws.webcontainer.webapp.WebAppErrorReport: javax.servlet.ServletException: Worklight Console initialization failed.Logged Exception: java.lang.RuntimeException: Class 'com.mypackage.MyCustomLoginModule' defined in login module 'CustomLoginModule' in the authentication configuration file doesn't exist.
at com.worklight.core.auth.impl.AuthenticationFilter.verifyServletInitialized(AuthenticationFilter.java:300)
at com.worklight.core.auth.impl.AuthenticationFilter.doFilter(AuthenticationFilter.java:111)
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:194)
at [internal classes]
Caused by: javax.servlet.ServletException: Worklight Console initialization failed.Logged Exception: java.lang.RuntimeException: Class 'com.mypackage.MyCustomLoginModule' defined in login module 'CustomLoginModule' in the authentication configuration file doesn't exist.
... 5 more
Could you help me?
Seems that your project war does not contain your java classes for some reason. I am not sure why, need more information on that, but I think that by deleting your bin folder and rebuilding all artifact you will be able to solve this issue.
Look your JDK version between your generated binary app and your Worklight server version. You can check if the binary is generated in Windows or Unix based operative system and redeploy your app taking the server operative system as a base for your binary app.
Need to write their own java class for custom authentication. These java class will act like authenticator and challenger while writing a custom authentication method.
Please find the documentation for the HTTP based custom authentication.
I have created a database endpoint. But while testing the connection I am getting the following error:
Test connection failed: Error creating bean with name '_muleSimpleRegistryBootstrap' defined in URL [jar:file:/D:/MuleStudio/plugins/org.mule.tooling.server.3.4.0.ee_3.4.0.201305131832/mule/mule/mule-module-spring-config-3.4.0.jar!/default-mule-config.xml]: Invocation of init method failed; nested exception is java.lang.NoClassDefFoundError: org/mule/security/oauth/processor/AbstractExpressionEvaluator (org.mule.api.lifecycle.InitialisationException)
org.mule.common.MuleArtifactFactoryException: Error initializing
at org.mule.config.spring.SpringXmlConfigurationMuleArtifactFactory.doGetArtifact(SpringXmlConfigurationMuleArtifactFactory.java:149)
at org.mule.config.spring.SpringXmlConfigurationMuleArtifactFactory.getArtifact(SpringXmlConfigurationMuleArtifactFactory.java:49)
at org.mule.config.spring.SpringXmlConfigurationMuleArtifactFactory.getArtifact(SpringXmlConfigurationMuleArtifactFactory.java:39)
at org.mule.tooling.metadata.api.utils.ConnectionTester.internalTestConnection(ConnectionTester.java:72)
at org.mule.tooling.metadata.api.utils.ConnectionTester.testConnectionFor(ConnectionTester.java:108)
at org.mule.tooling.messageflow.action.TestConnectorConnectionFromMuleConfigAction$1$1.run(TestConnectorConnectionFromMuleConfigAction.java:72)
at java.lang.Thread.run(Unknown Source)
Do you happen to have a Cloud Connector for Mule 3.5 in your project?
If yes, it's a well-known issue: https://www.mulesoft.org/jira/browse/STUDIO-3831
I am using bean validation in my application. When there is no constraint validation errors everything works nicely. Every time there is a validation error, Glassfish throws the following exception:
Caused by: java.lang.ClassNotFoundException: javax.validation.groups.Default: java.net.MalformedURLException: Unknown protocol: osgi
at com.sun.corba.ee.impl.util.JDKBridge.loadClassM(JDKBridge.java:325)
at com.sun.corba.ee.impl.util.JDKBridge.loadClass(JDKBridge.java:228)
at com.sun.corba.ee.impl.javax.rmi.CORBA.Util.loadClass(Util.java:640)
at com.sun.corba.ee.impl.util.RepositoryId.getClassFromType(RepositoryId.java:628)
at com.sun.corba.ee.impl.orbutil.RepIdDelegator.getClassFromType(RepIdDelegator.java:169)
at com.sun.corba.ee.impl.encoding.CDRInputStream_1_0.readClass(CDRInputStream_1_0.java:1439)
The bean-validation.jar is present in glassfish/modules folder. The startup doesn't throw any exceptions regarding validation.
PS. Note that we are using remote beans with CORBA.
Reproducable on GlassFish 3.1.2.2 and 3.1.1.
I traced this problem to serialization of the ConstraintValidationException through CORBA. Somehow the bean-validation module is not loaded properly with osgi and the javax.validation.groups.Default class is missing. I made a quick workaround so that the ConstraintValidationException is intercepted and never sent through CORBA. Instead the validation error information is gathered in a custom Exception class that can be actually serialized through the services.
Good morning,
I am trying to local test my web application, which makes use of:
Spring (core + MVC)
Google AppEngine
Google Cloud SQL
Hibernate
In this page https://developers.google.com/cloud-sql/docs/developers_guide_java Google explains how to make the hello world run, and that's right.
I deploy to AppEngine with no problems.
The next need is testing on the local system, with a local standard mysql instance and that document goes ahead in the explanation. You can give your local access credentials by command-line or by Google Eclipse Plugin.
But I am using the Maven GAE Plugin http://www.kindleit.net/maven_gae_plugin/ and simple mvn gae:run ends up with this error:
Cannot resolve reference to bean 'mySessionFactory' while setting bean property 'sessionFactory'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'mySessionFactory' defined in ServletContext resource [/WEB-INF/spring/root-context.xml]: Invocation of init method failed; nested exception is java.lang.IllegalStateException: System property rdbms.driver must be set.:
java.lang.IllegalStateException: System property rdbms.driver must be set.
at com.google.appengine.api.rdbms.dev.LocalRdbmsServiceLocalDriver.registerDriver(LocalRdbmsServiceLocalDriver.java:80)
That's a pretty descriptive error, so I desperately tried:
mvn gae:run -Drdbms.server=local -Drdbms.driver=com.mysql.jdbc.Driver -Drdbms.url=jdbc:mysql://localhost:3306/prova?user=root&password=pass
... with no result! :-(
Help! O.O
Solved using plugin's jvmFlags