We Keep Coding

Apache Karaf - missing dependencies (DataSources as it seems)

I get the error below when I startup Karaf. A colleague of mine has the exact same features, bundles, etc. but does not get the error. We both use Windows 10 and Karaf 4.0.7.
If fact he just compressed his Karaf folder and gave it to me. So our Karaf installations are identical. Now I am trying to get it working on my machine.
So how could it not work on my local machine?
I don't know Karaf well, so I have no idea how to troubleshoot further. What could be the reason?
Could it be that some jar file in my local Maven repo is missing
(which my co-worker has but I don't have)? I heard this is where Karaf is looking for some components.
data-access (2381)
------------------
Status: Failure
Blueprint
10/15/19 4:51 PM
Exception:
null
java.util.concurrent.TimeoutException
at org.apache.aries.blueprint.container.BlueprintContainerImpl$1.run(BlueprintContainerImpl.java:371)
at org.apache.aries.blueprint.utils.threading.impl.DiscardableRunnable.run(DiscardableRunnable.java:48)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Missing dependencies:
(&(osgi.unit.name=ybkDS)(objectClass=javax.persistence.EntityManager)) (&(osgi.unit.name=ybDS)(objectClass=javax.persistence.EntityManagerFactory))
In fact when I startup Karaf I first get this for a few mins and then I get the error I posted above.
karaf#root()> bundle:diag
Bundle 53
---------
Status: Installed
Unsatisfied Requirements:
data-access (2384)
------------------
Status: GracePeriod
Blueprint
10/15/19 6:36 PM
Missing dependencies:
(&(osgi.unit.name=ybDS)(objectClass=javax.persistence.EntityManagerFactory)) (&(osgi.unit.name=ybkDS)(objectClass=javax.persistence.EntityManager))
website-performance (2385)
--------------------------
Status: GracePeriod
Blueprint
10/15/19 6:36 PM
Missing dependencies:
(&(osgi.unit.name=ybDS)(objectClass=javax.persistence.EntityManagerFactory)) (&(osgi.unit.name=ybkDS)(objectClass=javax.persistence.EntityManager))
What is it looking for that I don't have?

You have a dependency to OSGi services for EntityManager and EntityManagerFactory both with property osgi.unit.name=ybkDS. These services are not coming up. You can first observe this in diag. After 5 minutes the blueprint container gives up to wait for these services and logs an error.
So you have to debug why these services are not coming up. Can you provide more information on how you instantiate the EntityManager?
I guess you are using Apache Aries JPA and maybe ops4j pax-jdbc.
In this case you to check that the DataSource comes up (should also be an OSGi service) and that you have installed the correct jpa impl (like hibernate).
It would also help if you could upload the log (especially everything from aries and pax-jdbc).

LeanFT null pointer at start

I have a problem with LeanFT. When i try to start it from intellij idea (LeanFT> Enable LeanFT) i have error:
null
java.lang.NullPointerException
at com.hp.lft.sdk.internal.ServerLauncher.runLauncherProcess(ServerLauncher.java:66)
at com.hp.lft.sdk.internal.ServerLauncher.launch(ServerLauncher.java:44)
at com.hpe.lft.sdkUtilities.serverLaunch.ServerLaunchUtils.launchIfNeeded(ServerLaunchUtils.java:24)
at com.hpe.lft.sdkUtilities.PluginServiceBase.launchServer(PluginServiceBase.java:129)
at com.hpe.lft.sdkUtilities.PluginServiceBase.enableOrDisablePlugin(PluginServiceBase.java:105)
at com.hpe.lft.actions.EnableLeanFTAction$1.run(EnableLeanFTAction.java:20)
at com.intellij.openapi.application.impl.ApplicationImpl$1.run(ApplicationImpl.java:305)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Even if runtime engine start manually.
What can cause this problem?

I recently came across this same problem and it was to do with the LeanFT runtime unable to load NodeJS. Looking into it further my npm path was missing from the Windows environment variables. After adding the path to my npm installation it worked fine.
You may have a similar problem, but to find out the actual cause, I advise you to check the LeanFT runtime log file, which can be found here:
Configuration file:
<LeanFT installation folder>\bin\LFTRuntime.log.config.xml
Path to the log level:
log4net > root
(Change from "INFO" to "debug")
Log output:
%localappdata%\Hewlett-Packard\LeanFT\Logs\HP.LeanFT.log
More details on LeanFT logs can be found on this HP support page.

This could be multiple reasons...
1) Mostly LeanFT runtime agent issue. If you start LeanFT and disconnect from net, then LeanFT will not work properly as licensee server unavailability even after you connect net. Manually initiating LeanFT runtime also will not work. Either restarting Eclipse/intellij and restarting LeanFT run time will solve. Or restarting laptop/system while connected to net will solve this problem.
2) This problem arises when incompatible versions between LeanFT SDK's are used in script, IE/Chrome add-ons and Lean FT Runtime agent versions. Make sure everything is same version, like 14.0.2... Including minor versions.

MyFirstPortlet-portlet-6.1.1.1.war does not support this version of Liferay

I'm learning portlets and at the moment I'm not able to run my portlet in Liferay.
When I want to deploy my portlet on Liferay, in my console I receive this messages:
com.liferay.portal.deploy.auto.PortletAutoDeployListener.deploy(PortletAutoDeployListener.java:88)
at com.liferay.portal.kernel.deploy.auto.AutoDeployDir.deploy(AutoDeployDir.java:50)
at com.liferay.portal.kernel.deploy.auto.AutoDeployDir.processFile(AutoDeployDir.java:211)
at com.liferay.portal.kernel.deploy.auto.AutoDeployDir.scanDirectory(AutoDeployDir.java:275)
at com.liferay.portal.kernel.deploy.auto.AutoDeployScanner.run(AutoDeployScanner.java:58)
Caused by: com.liferay.portal.kernel.deploy.auto.AutoDeployException: MyFirstPortlet-portlet-6.1.1.1.war does not support this version of Liferay
at com.liferay.portal.tools.deploy.BaseDeployer.deployFile(BaseDeployer.java:902)
at com.liferay.portal.tools.deploy.BaseDeployer.autoDeploy(BaseDeployer.java:213)
... 6 more
07:16:25,174 INFO [com.liferay.portal.kernel.deploy.auto.AutoDeployScanner][AutoDeployDir:224] Add MyFirstPortlet-portlet-6.1.1.1.war to the blacklist
I'm using the bundle liferay-portal-tomcat-6.2-ce-ga4
Do I need another version of Liferay?

Just remove "liferay-versions" property from "liferay-versions=6.1.20.xml" file and restart the server.It will solve your problem

Attempting to deploy an older Liferay Portal version

I have a really weird issue to solve. I'm getting following error line when trying to start Liferay Portal on Tomcat:
java.lang.IllegalStateException: Attempting to deploy an older Liferay Portal version. Current build version is 6201 and attempting to deploy version 6101.
at com.liferay.portal.tools.DBUpgrader.upgrade(DBUpgrader.java:105)
at com.liferay.portal.events.StartupAction.doRun(StartupAction.java:144)
at com.liferay.portal.events.StartupAction.run(StartupAction.java:52)
at com.liferay.portal.servlet.MainServlet.processStartupEvents(MainServlet.java:1306)
at com.liferay.portal.servlet.MainServlet.init(MainServlet.java:214)
at javax.servlet.GenericServlet.init(GenericServlet.java:160)
at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1266)
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1185)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1080)
at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5015)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5302)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:895)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:871)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:615)
at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:649)
at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1585)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
I've found only topics where people actually wanted to upgrade portal and got this message. What my workspace looks like is as this:
Windows, localhost,
Liferay 6.1 CE bundled with Tomcat, running on JRE 6, using PostgreSQL,
Liferay 6.2 CE bundled with Tomcat, running on JRE 7, using HSQL.
I don't want to upgrade, I just want to have both versions present.
Thanks guys!

In the Liferay installation directory you'll typically find a file named portal-ext.properties. This typically has the configuration for the database that Liferay shall use. Both versions that you are running should point to a different database, then you can have both installations in paralell.
If you want to run them at the same time, you'll also need to modify tomcat (assuming that's the appserver you use. Look for all port="xxxx" declarations in tomcat/conf/server.xml and change them to distinct values (OOTB there are three for every tomcat installation). In Eclipse/Liferay IDE you can also find the port declaration in the server information screen.

You can check this link as it helps me.
Click here
There is a table called release_ which contains a column build number.
This has build number.
I faced same issue so I deleted only this table and then restart server again.
I have back up for my db for version liferay 6.2 cega2.
I tried to install same version in different machine and I got this error.

This kind of error comes when you point Liferay of version X(6.2.0.1) with database of Liferay version Y(6.1.0.1).
You first have to migrate your database.
Refer link for 6.2 migration
EDIT====
You can have different database schema for different Liferay version. You can not run different version with same database schema.

Newrelic Install for WebSphere - ClassNotFoundException

We've installed the NewRelic java agent on our WebSphere Application / WebSphere Commerce system and in the NewRelic logs we are seeing this:
Sep 3, 2013 22:47:53 -0400 NewRelic 14 INFO: The data collector is temporarily unavailable. This can happen periodically. In the event that availability of our servers is not restored after a period of time, then please report this to New Relic. java.net.SocketException: java.lang.ClassNotFoundException: Cannot find the specified class com.ibm.websphere.ssl.protocol.SSLSocketFactory
at javax.net.ssl.DefaultSSLSocketFactory.a(SSLSocketFactory.java:11)
at javax.net.ssl.DefaultSSLSocketFactory.createSocket(SSLSocketFactory.java:6)
at com.ibm.net.ssl.www2.protocol.https.c.afterConnect(c.java:161)
at com.ibm.net.ssl.www2.protocol.https.d.connect(d.java:36)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1184)
at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:390)
at com.ibm.net.ssl.www2.protocol.https.b.getResponseCode(b.java:75)
at com.newrelic.agent.transport.DataSenderImpl.connectAndSend(DataSenderImpl.java:550)
at com.newrelic.agent.transport.DataSenderImpl.send(DataSenderImpl.java:600)
at com.newrelic.agent.transport.DataSenderImpl.invoke(DataSenderImpl.java:480)
at com.newrelic.agent.transport.DataSenderImpl.invokeNoRunId(DataSenderImpl.java:475)
at com.newrelic.agent.transport.DataSenderImpl.getRedirectHost(DataSenderImpl.java:203)
at com.newrelic.agent.transport.DataSenderImpl.connect(DataSenderImpl.java:193)
at com.newrelic.agent.RPMService.launch(RPMService.java:194)
at com.newrelic.agent.rpm.RPMConnectionServiceImpl$RPMConnectionTask.attemptConnection(RPMConnectionServiceImpl.java:301)
at com.newrelic.agent.rpm.RPMConnectionServiceImpl$RPMConnectionTask.access$1100(RPMConnectionServiceImpl.java:101)
at com.newrelic.agent.rpm.RPMConnectionServiceImpl$RPMConnectionTask$3.run(RPMConnectionServiceImpl.java:235)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:452)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:328)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:161)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:109)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:191)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:215)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:897)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:919)
at java.lang.Thread.run(Thread.java:738)
Caused by: java.lang.ClassNotFoundException: Cannot find the specified class com.ibm.websphere.ssl.protocol.SSLSocketFactory
at javax.net.ssl.SSLJsseUtil.b(SSLJsseUtil.java:125)
at javax.net.ssl.SSLSocketFactory.getDefault(SSLSocketFactory.java:3)
at javax.net.ssl.HttpsURLConnection.getDefaultSSLSocketFactory(HttpsURLConnection.java:41)
at javax.net.ssl.HttpsURLConnection.<init>(HttpsURLConnection.java:46)
at com.ibm.net.ssl.www2.protocol.https.b.<init>(b.java:26)
at com.ibm.net.ssl.www2.protocol.https.Handler.openConnection(Handler.java:1)
at com.ibm.net.ssl.www2.protocol.https.Handler.openConnection(Handler.java:5)
at java.net.URL.openConnection(URL.java:957)
at com.newrelic.agent.transport.DataSenderImpl.createConnection(DataSenderImpl.java:676)
at com.newrelic.agent.transport.DataSenderImpl.connectAndSend(DataSenderImpl.java:540)
... 18 more
There seems to be some documentation about how to update an Eclipse based IDE environment to overcome this error in other situations, but nothing specific to NewRelic. Has anyone seen this before that can offer suggestions on how to fix the issue?

The next release of New Relics Java agent should make it possible to run without any configuration changes. With version 2.21.X and earlier please submit a request for support at support.newrelic.com

Read and see if this publication gives you a hint:
http://www-01.ibm.com/support/docview.wss?uid=swg21584437

I went through the same thing. As you might have gathered from the article liked by Robban WebSphere has some restriction in the SSLConnectionFactory, so a quit fix would be to just edit the newrelic.yml and configure:
# The agent communicates with New Relic via https by
# default. If you want to communicate with newrelic via http,
# then turn off SSL by setting this value to false.
# This work is done asynchronously to the threads that process your
# application code, so response times will not be directly affected
# by this change.
# Default is true.
ssl: false
Good luck.

Version 3.0.0 or later of New Relic's Java Agent should completely resolve this issue without any custom configuration, certainly without turning off SSL! Release notes.