Unable to start EAR in Liberty Server in debug mode - debugging

Liberty server is started and when adding EAR to the server it is not starting and the server is terminated.
Whereas finding no issues in starting the application in regular mode.
Thanks in Advance

Related

Application deployment on Payara with JMS connection problems

We have noticed our web application is not being deployed on Payara 4.1 when Message Driven Beans fail to connect to the server properly or the queues are missing. We'd rather have the application up and running, then fail a deployment due to JMS connection issues. Is there a way on Payara to prevent deployment crashes due to JMS failing?
EDIT: We use IBM MQ with the wmq.jmsra resource adapter.
You didn't state which exact version of Payara (e.g. 4.1.174) and I forgot when this was added, but could you please try to set the system property
-Ddeployment.resource.validation=false
and check if this behaves as you desire.
You can do
asadmin create-jvm-options -Ddeployment.resource.validation=false
or simply put it in your domain.xml.

weblogic 10.3.6 application all time availability

I am using weblogic 10.3.6. I have a cluster configured and there are two managed servers MS-1 and MS-2. Now I have deployed my EAR into MS-1 and it is working fine. Now my requirement is while the application is running if somehow the MS-1 breaks down,all i want is that my application runs by switching to MS-2 ,that is I want my application to available all time, I am new to weblogic ,please help me .Detailed steps are needed
Weblogic Server 10.3.6 documentation : https://docs.oracle.com/cd/E23943_01/nav/wls.htm
WebLogic Server & Apache http server : https://docs.oracle.com/cd/E23943_01/web.1111/e16435/apache.htm#PLGWL395

WebSphere remote server debug configuration in IntelliJ Idea

I am trying to debug deployed application which is running in the remote WebSphere server version 7. When I try to configure server, I am getting error presented on the picture below. Please advise me how to configure the debug mode
I have referred following source https://www.jetbrains.com/idea/help/run-debug-configuration-websphere-server.html#d1145856e682

IBM Worklight - Can't run an app on WebSphere Application Server

My app runs well on Worklight Development Server, but not on WebSphere Application Server V8.5 Liberty Profile.
I tried both Oracle JDK and IBM JDK, there was no difference.
There was no problem connecting to the server with jconsole, although I had to connect without ssl.
On Eclipse Console,
[2014-07-11 17:18:10] Starting build process: application 'U1', all environments
[2014-07-11 17:18:12] Application 'U1' with all environments build finished.
[2014-07-11 17:18:12] Deploying application 'U1' with all environments to Worklight Server...
[2014-07-11 17:19:02] Failed to deploy the application to Worklight server: : JMX configuration error. Unable to obtain MBeans. Reason: "FWLSE3012E: JMX configuration
error. Unable to obtain MBeans. Reason: "Connection refused".".
Thank you.
I do not know how the Studio deploys to an external Liberty server.
You could also:
Install Worklight Server and deploy using
- the Server Configuration Tool
- or the ant tasks (provided by the Worklight Server installer)
- or manual procedure documented at https://www-01.ibm.com/support/knowledgecenter/SSZH4A_6.2.0/com.ibm.worklight.installconfig.doc/install_config/t_wlconsole_install.html
The manual procedure may give you hints about what is missing in your External Liberty Server.
It could be:
- rest connector and it's configuration https://www-01.ibm.com/support/knowledgecenter/SSZH4A_6.2.0/com.ibm.worklight.installconfig.doc/install_config/t_optional_config_app_server_liberty.html
- JNDI properties so that Liberty can use the REST connector (step 3 at https://www-01.ibm.com/support/knowledgecenter/SSZH4A_6.2.0/com.ibm.worklight.installconfig.doc/admin/t_configuring_liberty_profile_for_wladmin_manually.html )

WebSphere 8.5: Importing 6.1 Profile ends with "fail to deploy application isclite"

On the 6.1 server I run...
$AdminTask exportWasprofile {-archive c:/tmp/my.car}
On the 8.5 server I see...
$AdminTask importWasprofile {-archive c:/tmp/my.car}
WASX7015E: Exception running command: "$AdminTask importWasprofile {-archive c:/
tmp/my.car}"; exception information:
com.ibm.wsspi.configarchive.ConfigArchiveException
com.ibm.wsspi.configarchive.ConfigArchiveException: fail to deploy application isclite
Is there something special I have to do to properly migrate profiles? Is there a place I can look to get more info as to what is going wrong?
From IBM WebSphere Application Server Migration Toolkit's website:
The IBM® WebSphere® Application Server Migration Toolkit is a suite of
tools and knowledge collections that enables your organization to
quickly and cost-effectively migrate to WebSphere Application Server
V7, V8, or V8.5, whether from a previous version of WebSphere
Application Server or competitive application servers including Apache
Tomcat Server, JBoss Application Server, Oracle Application Server,
and Oracle® WebLogic Server.
You should use it as it's bundled in WebSphere Application Server 6.1 (and higher) and offers two scripts that help you in the migration: WASPreUpgrade and WASPostUpgrade.
WASPreUpgrade "saves the configuration of a previously installed version of WebSphere Application Server into a migration-specific backup directory." while WASPostUpgrade "retrieves the saved configuration that was created by the WASPreUpgrade command from the backupDirectory that you specified." (quoting their pages).
Although they might be using wsadmin/Jython, I think you may have more success with these two command-line utilities.

Resources