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.
Related
This is my first attempt at creating a Websphere Local run configuration in Intellij and obviously I need some help.
First question: is Websphere supposed to be running when I run the configuration?
Second question: when I run the configuration and Webshpere is not running Intellij will say 'cannot ping localhost:8880', so probably Websphere should be running. When I start Websphere and then start the Intellij run config it says "address localhost:8880 is already in use" and then "Unable to open debugger port (127.0.0.1:62019): java.net.SocketException: 'socket closed'".
Here is my setup:
Third question: from the Websphere admin console I got that port 8880 is configured as the SOAP_CONNECTOR_ADDRESS. Is Intellij supposed to use that?
Thanks!
The following worked for me:
Go to run/debug configuration and click on +
Choose Remote (and not Websphere Server)
Change port to the port you want to use(I choose 7777)
To answer your question: no, if you want to start the server from IntelliJ, you should first check the server is stopped.
For solving the problem: Have you checked if WebSphere is running as a service automatically?
For doing it on Windows:
Open a "File Explorer" window
Right click on "My Computer"
Click on "Manage"
Click on "Services and Applications"
Click on "Services"
Look for "IBM WebSphere Application Server"
Check if it's running and stop it, change it to manual if you want to start server from IntelliJ without repeating this whole process everytime you log in Windows.
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.
I have a weblogic domain (i.e. server1) that manages multiple managed servers (i.e. server2) on remote machines on which the admin server does not reside. I am trying to use WLST in online mode to dynamically pack the domain on the Admin Server into a JAR and transfer it to the managed server, but it fails due to CIE ConfigHelper service not being availble. I've tried to find a reference to this service with no lunck.
Here is the log of the output:
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
Connecting to t3://admin:7001 with userid admin ...
Successfully connected to Admin Server "wladmin_server" that belongs to domain "qa".
Warning: An insecure protocol was used to connect to the
server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.
Location changed to serverRuntime tree. This is a read-only tree with DomainMBean as the root.
For more help, use help('domainConfig')
CIE ConfigHelper online service is not available.
Disconnected from weblogic server: wladmin_server
I'm doing this based on the following link https://docs.oracle.com/middleware/1212/wls/WLSTG/domains.htm#WLSTG406 , but it just doesn't seem to work.
I am using Weblogic 12c (12.1.3) running on RH Linux.
Thanks.
pack and unpack scripts are working for us in similar scenario.
On admin server machine where domain is already created ,You can use this to pack/create managed server template :
$WL_HOME/common/bin/pack.sh -domain=${DOMAIN_HOME} \
-template=${DOMAIN_NAME}_managed_template.jar \
-template_name="${DOMAIN_NAME}" \
-template_author="YOU" \
-template_desc="${DOMAIN_NAME}-managed-template" \
-managed="true" \
-log=logs/pack_managed_${DOMAIN_NAME}.log
Then copy managed server template to different machines and unpack there:
$WL_HOME/common/bin/unpack.sh \
-domain=$DOMAIN_HOME \
-template=${DOMAIN_NAME}_managed_template.jar \
-overwrite_domain="true" \
-app_dir=$DOMAIN_HOME/../applications \
-log=logs/${DOMAIN_NAME}_creation.log
I have also encountered the same problem on my weblogic (ver 12.1.3). The problem seems to appear only when the weblogic server is started using wlst.
When I started the weblogic using startWeblogic.sh file and run the domain template wlst script the error(CIE ConfigHelper online service is not available.) has disappeared, and I can see that the template is created successfully.
It seems like a bug in weblogic wlst.
I am trying to port an application from WebLogic to JBoss EAP 6.2.
When running the standalone server in JBoss, in the admin console there is a button and in the command line interface there is a command line option to check the data source connection.
/subsystem=datasources/data-source=myds:test-connection-in-pool
These options do not appear to exist in either place when running the "domain" server. Am I missing something? Is there some further setting I must make to enable it? I tried a technique which is sometimes an analog in the domain server and it doesn't work here.
/profile=full/subsystem=datasources/data-source=myds:test-connection-in-pool
JBoss docs are much weaker for "domain" model than for "standalone".
You are absolutely correct that while running the standalone server in JBoss, in the admin console there is a button and in the command line interface there is a command line option to check the data source connection butThese options do not appear to exist in either place when running the "domain" server.
You still can use the command line of jboss-eap-6.x to test the configured data source connection in domain server. You need to navigate to $JBOSS_HOME/bin/ and execute script: jboss-cli.sh
Connect to the domain server controller with: connect :PORT_NO and execute the following commands:
For XA-DataSource:
/host=$Host_Controller_Name/server=$Server_Name/subsystem=datasources/xa-data-source=DataSource_JNDI_Name:test-connection-in-pool
For Non-XA-DataSource:
/host=$Host_Controller_Name/server=$Server_Name/subsystem=datasources/data-source=DataSource_JNDI_Name:test-connection-in-pool
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.