We are trying to deploy Worklight Enterprise edition on Ubuntu server over Tomcat
While we were successful with several steps, we got stuck with one error while getting the Tomcat up and running with our War file. We use MySQL as DB.
The specific error we are facing is ".BeanCreationException: Error creating bean with name 'deployService' defined in URL"
SEVERE: FWLST0003E: ========= Failed starting project /td_ibm
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'deployService' defined in URL [jar:file:/usr/share/tomcat6/lib/worklight-jee-library.jar!/conf/integration.xml]: Invocation of init method failed; nested exception is java.lang.NullPointerException
The complete log trace text file can be found at Tomcat Log
This is clearly a configuration issue.
1. run mysql-admin (MySQL UI front end) and make sure you can connect to the Worklight catalog under the name and user you defined in the worklight.properties.
if the database is on a different machine than the tomcat (make sure you have set the right remote access permissions for MySQL (for testing only: try giving Worklight DB user an untrusted access .i.e. use "#%" ))
another issue: if you are installing Worklight on Tomcat: did you run the SQL schema script to create the Worklight schema ? you must run it manually (there is a workaround though: connect to the same database from Eclipse which runs a Worklight project)
what files do you have under /var/lib/tomcat6/worklight.home/td_ibm/data/export/adapters ?
If its empty, there maybe a bug in the Worklight code.
Related
I am running Apache Directory as a service on Windows 10.
I installed and ran the service and it ran without difficulties. Then, using the Apache Directory Studio (in Schema Mode), I created a new schema project, added a new schema with a single object type and a single attribute type, exported the new schema information to an LDIF file, and imported it back into the LDAP browser (as instructed in https://directory.apache.org/apacheds/basic-ug/2.3.1-adding-schema-elements.html).
As instructed, I then attempted to restart the ApacheDS service.
The ApacheDS service now will not start! When I attempt to start it now, it consistently shows the following failure message:
error 1067: the process terminated unexpectedly
Does anyone know what is broken in the server that causes this failure? How can I fix this problem and get the service to run again?
The error could be anything, and might be as well unrelated to the schema update, to get more debug info, change FATAL in conf to DEBUG.
https://directory.apache.org/apacheds/advanced-ug/5.3-logs.html
My Weblogic server was running fine inside my Eclipse. But then I accidentally deployed an .ear into my Weblogic server (using the server's Admin Console) which conflicts with another .ear, and now my Weblogic server won't start up. I know how to remove the .ear. The way to remove it is to go to the Admin Console, choose Deployments, checkmark the offending .ear and then choose stop and delete. But I can't get to the Admin Console because the Weblogic server won't start up.
I want to undeploy it, but I can't, because I can't start up the Admin Console. I also tried undeploying it with the command line, but the command requires communicating with a running server.
The error message in the Eclipse console says: "Failed to initialize the application 'EILoggingSharedLib [LibSpecVersion=2.22,LibImplVersion=2.22]" due to error weblogic.application.library.LibraryDeploymentException: [J2EE:160145]Failed to deploy library Extension-Name: EILoggingSharedLib, Specification-Version: 2.9, Implementation-Version: 2.9, because of conflicting library Manifest values, and library information registered with the server: [Specification-Version: 2.9 vs. 2.22, Implementation-Version: 2.9 vs. 2.22]. Check the library MANIFEST.MF file and correct version information there to match server settings, or undeploy the misconfigured library."
This is the command line command I used:
C:\bea12c\wlserver\server\lib>java -cp weblogic.jar weblogic.Deployer -verbose -noexit -adminurl http://localhost:7016 -username (myusername) -password (mypassword) -name Dev12c -undeploy EILoggingSharedLib -timeout 300
weblogic.Deployer invoked with options: -verbose -noexit -adminurl http://localhost:7016 -username weblogic -name Dev12c -undeploy EILoggingSharedLib -timeout 300
Unexpected Error Initializing Deployer: weblogic.Deployer$DeployerException: weblogic.deploy.api.tools.deployer.DeployerException: Unable to connect to 'http://localhost:7016': Destination 0:0:0:0:0:0:0:1, 7016 unreachable; nested exception is:
java.net.ConnectException: Could not connect to /0:0:0:0:0:0:0:1; No available router to destination. Ensure the url represents a running admin server and that the credentials are correct. If using http protocol, tunneling must be enabled on the admin server.
I also tried starting the server with startweblogic.sh with the following command, using the same ID and password that I use to log into the admin console (when it was running). But it didn't help:
startweblogic.sh username=(myusername) password=(mypassword)
Thank you!
First, try to remove your application from deployed applications with Eclipse. If it does not work, edit the ${DOMAIN_HOME}/config/config.xml file and remove the declaration of your application. Then start your server.
I found a solution. My Weblogic server that had the problem was at http://localhost:7016. Since it's a localhost server, all the libraries and apps deployed to that localhost are in a directory in my C: drive where my Weblogic server installation is. I deleted the offending .ear using File Explorer, then the Weblogic server started up fine. I was able to go into the Admin Console and delete them again from there. After that, all was good. Thank you, Emmanuel and Wesley.
I am installing pentaho 8.1 CE on ubuntu 16.04
have made change of bd from HSQLDB to Mysql, tables have been created, jackrabbit, hibernate and hibernate.
When starting the server, not login, I imagine that the users are missing or not created. ??
the error that throws me in
catalina.out
ERROR [CompositeUserRoleListService] User / Role List could not be obtained.
java.lang.IllegalStateException: Target of Bean was never resolved: org.springframework.security.core.userdetails.UserDetailsService
atorg.pentaho.platform.engine.core.system.objfac.spring.BeanBuilder$1.invoke(BeanBuilder.java:159)
at com.sun.proxy.$Proxy84.loadUserByUsername(Unknown Source)
..
..
Database Jackrabbit no created tables..
any idea?
When changing the back-end database, there's a few things you need to make sure you check.
repository.xml
quartz.properties
hibernate-settings.xml
[your-database].hibernate.cfg.xml
context.xml (in WEB-INF)
You'll need to confirm the settings for the connection to the new database has been properly configured in all of these different config files. Some additional details on how to config these files for MySQL specifically can be found in the documentation here: https://help.pentaho.com/Documentation/8.1/Setup/Installation/Archive/MySQL_Repository
Past that, make sure that you delete the "repository" directory inside of /pentaho-solutions/system/jackrabbit as this is an index of the repository. If you change your database back-end, then this index needs to be rebuilt. The index is rebuilt automatically if the server sees that "repository" directory doesn't exist at startup.
I've found the same issue on Windows Server 2016 and MySQL8.0, with Pentaho 8.0.2.
Starting Pentaho server from the start-pentaho.bat command, everything was fine.
The problem arise when I was using Tomcat.
The solution was to be sure that Tomcat service was running with the LOCAL SYSTEM account.
If the Tomcat service runs with lower privileges, maybe it can't access to the pentaho-solutions directory and it cannot load the required java beans.
if everything as per the document is configured correctly, then You might be missing the connection change in applicationContext-spring-security-hibernate.properties, please check that.
After installing and configuring MobileFirst 8 on WebSphere Application Server 8.5.5.10, RedHat Linux 7.3, I am getting error
FWLSE3030E: The runtime "mfp" does not exist in the MobileFirst administration database. The database may be corrupted.
I am using WebSphere SDK 1.7 with FP40
I have checked the Database, and all tables are present.
In the SystemOut.log, I am getting exceptions and it is as below:
com.ibm.worklight.admin.common.util.exceptions.SystemException: FWLSE3002E: The resource is not found.
SystemOut.log
Edit1: I have installed MobileFirst 8 using Command line, and configured it using Ant task.
Edit2: WAS Full profile deployed applications.
The symptom you're seeing seems like an open issue that is being tracked as APAR PI71317. Please open a PMR and mention this APAR number; we can give you a test fix to try to help us confirm that it is indeed this issue.
first: go to the WAS ND JDBC data sources section and choose the MFP data source and press the "test connection" button.
look carefully at the DSN definition and make sure you can browse that same DB with other tool and ensure the schema and tables exist.
bare in mind: in WAS ND there should be two entries : one for runtime DB and one for MFP admin DB.
I am trying to deploy the MobileFirst Admin Operational console using Server Configuration Tool. Started the configuration tool as root user. Create a configuration and saved the xml. Pressed the "Deploy" button. Its failed with JVM terminated Exit code -1 error.
MobileFirst Server Version 7.1.0.0-MFPF-Server-IF201510051721
WebSphere 8.5.5.7
Installation Manager JRE:jre_7.0.7001.20140909_1712
After this error, I am able to see the Admin console application and admin services application in WebSphere. But in Configuration Tool not able to create / add runtime under this configuration. It says no configuration found.
After this error, I am able to see the Admin console application and admin services application in WebSphere. But in Configuration Tool not able to create / add runtime under this configuration. It says no configuration found.
This is not a solution to the JVM crash you experiment, but a workaround to enable to be able to add the runtime (I understand from the above description that the crash happens after the Server Configuration Tool saved the configuration and deployed it).
Go to (homeDir)/.mobilefirst_platform_server/server-configuration-tool. You should find a directory named after your configuration. In that directory, you should find a file named (ConfigName).xml. Copy this file as (ConfigName).lastdeployed (ie same name as the xml file but change the suffix). The Server Configuration Tool would have created this file after deployment completion (and uses it for later operations such as uninstall) and it uses it as an indicator that the configuration is deployed.