Cannot deploy ADF application onto Weblogic - weblogic

I have jDeveloper 12c on Windows and WebLogic Server 12c on a Linux (as a remote server).
Im trying to deploy my application onto the weblogic on linux, but to no avail.
This is the error msg i've encounter.
[01:30:05 PM] ---- Deployment started. ----
[01:30:05 PM] Target platform is (Weblogic 10.3).
[01:30:05 PM] Retrieving existing application information
[01:30:05 PM] Running dependency analysis...
[01:30:05 PM] Building...
[01:30:06 PM] Deploying profile...
[01:30:08 PM] Wrote Web Application Module to C:\JDeveloper\mywork\TestApp\ViewController\deploy\TestApp_ViewController_webapp.war
[01:30:08 PM] Deploying Application...
[01:40:09 PM] weblogic.deploy.api.spi.exceptions.ServerConnectionException: [J2EE Deployment SPI:260041]Unable to upload "C:\JDeveloper\mywork\TestApp\ViewController\deploy\TestApp_ViewController_webapp.war" to "t3://10.186.116.221:7001"
[01:40:09 PM] Deployment cancelled.
[01:40:09 PM] ---- Deployment incomplete ----.
[01:40:09 PM] Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer)
Tested connection and all, it works out fine.

Related

Weblogic update of Apache CXF from 3.2.1 to 3.2.11

I have a Web application using Apache CXF version 3.2.1 which deploys and works successfully on Weblogic version 12.2.1.3.0.
Because of security vulnerabilities I need to bump the version of CXF library from 3.2.1 to latest (3.2.13 in that moment).
I got the following error when trying to deploy the application with version above 3.2.1(3.2.2, 3.2.3, 3.2.11, 3.2.13 etc..)
<Apr 7, 2020 6:19:54,850 PM EEST> <Error> <HTTP> <BEA-101216> <Servlet: "JAX-RS/Jersey#1" failed to preload on startup in Web application: "webservices.war".
A MultiException has 3 exceptions. They are:
1. java.lang.InstantiationException
2. java.lang.IllegalStateException: Unable to perform operation: create on org.apache.cxf.jaxrs.provider.AbstractResponseViewProvider
3. java.lang.IllegalStateException: Unable to perform operation: create on org.glassfish.jersey.message.internal.MessageBodyFactory
I tried the following approaches:
Adding a shared library as described here:
https://docs.oracle.com/middleware/1213/wls/RESTF/use-jersey20-ri.htm#RESTF296
Modifying the schema location
https://www.oracle.com/webfolder/technetwork/weblogic/weblogic-web-app/index.html
Setting prefer-web-inf-classes to true so all
libraries are taken from the deployed application(not from the
server)
Adding local copy of Jax-RS in my lib folder and trying to use it with prefer-application-packages
Do you have any idea what could cause the problem?
What might be the difference between Apache CXF 3.2.1 and 3.2.2 ?
Why is a minor version change breaking an application?

unboundid ldap upgraded version from 1.1.3 to 3.1.1. ClassNotFoundException being thrown.

I have recently upgraded our unboundid ldap jar version from 1.1.3 to 3.1.1. After the upgrade when I am deploying the app in weblogic, I am getting a ClassNotFoundException in the log. So far I have faced no issues in terms of functionality, but I am concerned is there any connection leakage is happeining underneath or not.
Caused by: java.lang.ClassNotFoundException: com.unboundid.ldap.sdk.DisconnectType
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:64)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179)
at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:43)
... 1 more
App package : WAR
Server : Weblogic 10.3.6
I experienced a similar issue, using unboundid ldap 2.2.0 and Tomcat 7, with reference to ProtocolMessages instead of DisconnectType:
java.lang.NoClassDefFoundError: com/unboundid/ldap/protocol/ProtocolMessages
The class was definitely present in the jar files. In my case, this error was a smokescreen. On initialization, the application experienced an error and failed to load; however, some ldap connection threads had already connected and did not get shut down properly. The orphaned threads continued to throw NoClassDefFoundError until I restarted the application server.

Unauthorized access was denied or security settings have expired javax.net.ssl.SSLException: certificate_unknown when creating MobileFirst runtime

I'm installing a v7.0.0 MobileFirst Server with Liberty 8.5.5.4 with Java 1.7.0 on RedHat in Nonadminstrator mode. Steps I have followed:
Successfully install Liberty, create a server and verify it starts with no errors in messages.log.
Install MFP Server.
Use the MFP Server Configuration Tool to create an MFP configuration using the Liberty server.
Bounce the Liberty server and verify it starts with no errors.
Create an MFP Runtime using the Server Configuration Tool.
Bounce the server and observe SSL errors in the log.
The SSL errors seem to be related to Liberty trying to talk to the JMX REST client - at least that is my assumption since I haven't even invoked an adapter yet.
The WAR file I am using for the Runtime comes from a project that builds and runs fine in the MFP Studio Liberty development server.
The full log can be found at https://www.dropbox.com/s/o1frf7pjszm46n6/messages.log?dl=0, but here's the relevant error:
[8/4/15 18:23:09:400 CDT] 00000050 com.ibm.ws.channel.ssl.internal.SSLHandshakeErrorTracker E CWWKO0801E: Unable to initialize SSL connection. Unauthorized access was denied or security settings have expired. Exception is javax.net.ssl.SSLException: Received fatal alert: certificate_unknown
at com.ibm.jsse2.o.a(o.java:6)
at com.ibm.jsse2.SSLEngineImpl.a(SSLEngineImpl.java:409)
at com.ibm.jsse2.SSLEngineImpl.a(SSLEngineImpl.java:469)
at com.ibm.jsse2.SSLEngineImpl.j(SSLEngineImpl.java:181)
at com.ibm.jsse2.SSLEngineImpl.b(SSLEngineImpl.java:176)
at com.ibm.jsse2.SSLEngineImpl.a(SSLEngineImpl.java:495)
at com.ibm.jsse2.SSLEngineImpl.unwrap(SSLEngineImpl.java:66)
at javax.net.ssl.SSLEngine.unwrap(SSLEngine.java:23)
at com.ibm.ws.channel.ssl.internal.SSLUtils.handleHandshake(SSLUtils.java:870)
at com.ibm.ws.channel.ssl.internal.SSLConnectionLink.readyInbound(SSLConnectionLink.java:531)
at com.ibm.ws.channel.ssl.internal.SSLConnectionLink.ready(SSLConnectionLink.java:304)
at com.ibm.ws.tcpchannel.internal.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:174)
at com.ibm.ws.tcpchannel.internal.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:83)
at com.ibm.ws.tcpchannel.internal.WorkQueueManager.requestComplete(WorkQueueManager.java:504)
at com.ibm.ws.tcpchannel.internal.WorkQueueManager.attemptIO(WorkQueueManager.java:574)
at com.ibm.ws.tcpchannel.internal.WorkQueueManager.workerRun(WorkQueueManager.java:929)
at com.ibm.ws.tcpchannel.internal.WorkQueueManager$Worker.run(WorkQueueManager.java:1018)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:906)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:929)
at java.lang.Thread.run(Thread.java:796)
Solved it. I went back to a system I knew worked and started looking for differences. The configuration was all the same, but I noticed the working system used
java version "1.7.0"
Java(TM) SE Runtime Environment (build pxa6470sr7fp1-20140708_01(SR7 FP1))
IBM J9 VM (build 2.6, JRE 1.7.0 Linux amd64-64 Compressed References 20140627_204598 (JIT enabled, AOT enabled)
J9VM - R26_Java726_SR7_20140627_0924_B204598
JIT - r11.b06_20140409_61252.04
GC - R26_Java726_SR7_20140627_0924_B204598_CMPRSS
J9CL - 20140627_204598)
JCL - 20140707_01 based on Oracle **7u65-b16**
The system that was throwing the SSL errors was running
java version "1.7.0"
Java(TM) SE Runtime Environment (build pxa6470sr6fp1ifix-20140220_01(SR6 FP1+IX90136+IX90137))
IBM J9 VM (build 2.6, JRE 1.7.0 Linux amd64-64 Compressed References 20140106_181350 (JIT enabled, AOT enabled)
J9VM - R26_Java726_SR6_20140106_1601_B181350
JIT - r11.b05_20131003_47443.02
GC - R26_Java726_SR6_20140106_1601_B181350_CMPRSS
J9CL - 20140106_181350)
JCL - 20140103_01 based on Oracle **7u51-b11**
I installed 7u65-b16 on the new system, restarted Liberty under that version of Java and all seems to be well now.

An error occurred while worklight installation?

An error occurred while collecting items to be installed
session context was:(profile=SDKProfile, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
Unable to read repository at http://public.dhe.ibm.com/ibmdl/export/pub/software/mobile-solutions/worklight/wdeupdate/plugins/com.ibm.imp.worklight.simulation.ui_6.1.0.00-20131219-1900.jar.
Read timed out
How to resolve this error?
It took longer than usual, but I managed to install Worklight Developer Edition from the Eclipse Marketplace in Eclipse Java EE 4.3.1 ("Kepler" SR1).
I think the connection to the repository is just especially slow right now.
There is nothing to do other than waiting and retrying...

IBM Mobile Application Platform Pattern Type 5.0: Error when deploying an SQL Adapter

I instantiate the "IBM Mobile Application Platform Pattern Type 5.0" with my worklight project ( 2 wlapp and 4 adapters ). One of my adapter is not deployed on the worklight console even if all is green in the VAP.
Here is the error I can found in the log files:
deploy_wl_adapter:
[echo] worklight_context=d-ae4e9b49-478a-4f0e-99e1-e6ad4886c1d9/CustomerCentricity/
[echo] adapter=/opt/IBM/worklight/artifact/DBAdapter.adapter
[adapter-deployer] Mar 29, 2013 12:32:48 PM com.worklight.ant.deployers.AbstractDeployerTask logDeployResponse
[adapter-deployer] SEVERE: ERROR
BUILD SUCCESSFUL
Total time: 4 seconds
If I try to deploy the adapter directly on the worklight console, I have the same error.
I guess your adapter use a realm which do not define in the authentication.xml
Can you deploy your adapter in the local worklight console?
Such as locahost:8080/console