MobileFirst Platform foundation 6.3.0.00-20141127-1357
WebSphere Application Server 8.5.5.0 (1.0.3.20130510-0831) on Java HotSpot(TM) 64-Bit Server VM, version 1.7.0_75-b13 (en_US)
hosted on softlayer
Project WAR version: 6.3.0.00.20150214-1702
Follow up on this post
Was unable to to deploy a runtime because I was using a different MFP-WASLP server version. Able to do so now. However can't deploy -wlapps.
I got a "Is not managed by this context" error, could that be referring to the MFP context? Found a few posts on here but they all point to max_allowed_packet. I was able to set my.ini files and confirm with show variables. so I don't think that's it.
I get the following error:
[4/6/15 7:24:55:845 CEST] 000000fc com.ibm.worklight.admin.actions.BaseTransaction E internalRun() Exception
<openjpa-1.2.2-r422266:898935 nonfatal user error> org.apache.openjpa.persistence.ArgumentException: Object "com.ibm.worklight.dataaccess.jpa.entity.ProjectEntity-com.ibm.worklight.dataaccess.jpa.entity.ProjectEntity-1" is not managed by this context.
FailedObject: com.ibm.worklight.dataaccess.jpa.entity.ProjectEntity-com.ibm.worklight.dataaccess.jpa.entity.ProjectEntity-1
at org.apache.openjpa.persistence.EntityManagerImpl.processArgument(EntityManagerImpl.java:1216)
at org.apache.openjpa.kernel.BrokerImpl.processArgument(BrokerImpl.java:2149)
at org.apache.openjpa.kernel.BrokerImpl.gatherCascadeRefresh(BrokerImpl.java:2816)
at org.apache.openjpa.kernel.BrokerImpl.refresh(BrokerImpl.java:2793)
at org.apache.openjpa.kernel.DelegatingBroker.refresh(DelegatingBroker.java:1078)
at org.apache.openjpa.persistence.EntityManagerImpl.refresh(EntityManagerImpl.java:688)
at com.ibm.worklight.admin.actions.BaseTransaction.setNewProjectTransactionID(BaseTransaction.java:618)
at com.ibm.worklight.admin.actions.BaseTransaction.internalRun(BaseTransaction.java:315)
at com.ibm.worklight.admin.actions.BaseTransaction$1.run(BaseTransaction.java:222)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Any ideas what I could be doing wrong?
Just curious, although I doubt it, is there an error reference anywhere?(I could use that instead of always asking on so).
P.S my project war version and MFP are bot 6.3 but slight different versions(couldn't be the issue right?):
MobileFirst Platform foundation 6.3.0.00-20141127-1357
Project WAR version: 6.3.0.00.20150214-1702
Turns out something was up with the DB, reproduced the issue by adding mfp server, adding a config, adding a runtime, removing them and trying to add new ones or renamed ones failed to deploy. Was able to deploy the apps when removed runtimes, configs, dropped the db tables and deleted the mfp server folder in usr/servers/servernameFolder. After that had no issues whatsoever. Thank you for helping sort out the initial mfp-liberty srv mismatches. And all the links to manual config helped me understand MFP better –
Related
I had to develop an app with Flutter for my dissertation. The app was an update and an extension of an old app devepoled by another student of my university, 2 years ago.
He developed also the backend that was written in Java using Spring and Maven.
Developing my app, I had to do some changes and additions in his code.
Some days ago I tried to export the backend project as a war file compiling with the JDK 15 (during the developing I used the Intellij's build-in Tomcat to test the new features) and I did the deploy on my Tomcat and I got error 404.
After reading many posts about this error on this site I found the solution by simply installing and compiling with java 12.
At that point, excited by the idea of finally being able to use my application and start the tests necessary for my thesis, I deployed the same war file to the Tomcat running on university server and I got error 404 again:
"HTTP Status 404 - /backend-api/
type Status report
message /backend-api/
description The requested resource is not available.
Apache Tomcat/7.0.52 (Ubuntu)"
I tried to install the same JDK (1:7:0 79) that was used by the developer of the backend during his dissertation, but the problem wasn't solved.
In the second anwser of this thread it seems that they are talking about a similar problem, the point is that I can't modify any setting of the server of my univeristy and, right now, I can not even access to the logs of Tomcat.
I think the problem may be an outdated version of the JDK or Tomcat running on the university server.
But what seems strange to me is that the old version of the backedn is still running on that server and working without problems, and I have not made any changes to the configuration files, but only added a couple of functions.
Do you have any suggestions for me to solve the problem or understand what the cause is?
In a few days I should graduate and without my backend the application is not usable.
On my PC i deployed the war file on Tomcat 7.0.107 with JVM version 1.8.0_271-b09, while the university is running Apache Tomcat / 7.0.52 (Ubuntu) with JVM version 1.7.0_79-b14.
Thanks a lot to anyone who takes their time for trying to help me.
I am trying to install and configure Umbraco 8.
The NuGet installs umbracoCms well then I run the app to configure the database (custom DB).
And it crashes displaying:
Error during installation
See the log for full details (logs can typically be found in the App_Data\Logs folder)
The log doesn't tell e much:
{"#t":"2019-04-24T04:04:00.1230739Z","#mt":"An error occurred in InstallStatus trying to check upgrades","#l":"Error","#x":"System.NullReferenceException: Object reference not set to an instance of an object.\r\n at Umbraco.Web.Install.InstallHelper.GetDbProviderString(ISqlContext sqlContext)\r\n at Umbraco.Web.Install.InstallHelper.InstallStatus(Boolean isCompleted, String errorMsg)","SourceContext":"Umbraco.Web.Install.InstallHelper","ProcessId":1180,"ProcessName":"iisexpress","ThreadId":13,"AppDomainId":3,"AppDomainAppId":"LMW3SVC2ROOT","MachineName":"Machine1","Log4NetLevel":"ERROR","HttpRequestNumber":4,"HttpRequestId":"{requestguid}"}
The DB connestring is correct, the database tables are getting created although from the error message I am not able to figure out it's a problem with DB or the app.
The same things happened with Umbraco 7.10.
I am running the project on .NET 4.7.2, in VS 15.9.11 and MSSQL 2016
I installed sonar-3.7.2 without issue. I have it working properly with oracle. I can analyze maven-3 projects from a client machine on the same network as the sonarqube server.
The docs says it supports maven-3.x and maven-2.2.x. We are in the process of upgrading projects to maven-3 but many of our projects still use maven-2.0.9. I was hoping that the 2.2.x condition was merely due to what people were testing with and not a real limitation but some newly downloaded poms in my artifactory contain the property maven.min.version set to 2.2.1.
I need a version that will work with maven-2.0.9.
I saw a log from one of my coworkers also trying out sonar and it showed maven-2.0.9 was being used successfully. He is using defaults. I am setting up for production.
The error that I get (cleaned up of course):
Caused by: org.sonar.api.utils.HttpDownloader$HttpException: Fail to download [http://myhost:myport/batch_bootstrap/properties?project=mygroupid:myartifactid]. Response code: 400
I have tried sonar 3.7.2, 3.6.3 and 3.5.1 and get the same error in each case. In each case
analyzing a maven-3 project works (to prove everything else is ok)
I have tried adding the webcontext /sonar instead of just /.
I have tried setting the Server base url in the sonarqube server even though I have not tested anything yet related to sending emails.
I saw something about corruption in the local .m2 on another thread. Removing it did not help either.
Any and all suggestions appreciated.
Best Regards, Gord Cody
I think the documentation is quite clear : http://docs.codehaus.org/display/SONAR/Installing+and+Configuring+Maven
SonarQube supports only Maven 2.2.x and 3.x
But my question is : What's the problem to upgrade from maven 2.0.9 to 2.2.x?
I am trying to get started with Azure and am trying to use the Caching feature. I created a cloud service project and added a Cache worker role and a web role. I installed "Windows Azure Caching" nuget into projects for both the roles and added the name of cache worker role as identifier in DataCacheClients element in web.config of the web role.
I added the following code into the web role:
DataCacheFactory cf = new DataCacheFactory();
DataCache c = cf.GetDefaultCache();
When I try to run this locally on the emulator, I get the following exception:
ErrorCode<ERRCA0017>:SubStatus<ES0006>:There is a temporary failure.
Please retry later. (One or more specified cache servers are unavailable,
which could be caused by busy network or servers. For on-premises cache clusters,
also verify the following conditions. Ensure that security permission has been granted
for this client account, and check that the AppFabric Caching Service is allowed through
the firewall on all cache hosts. Also the MaxBufferSize on the server must be greater
than or equal to the serialized object size sent from the client.).
Additional Information : The client was trying to communicate with the server: net.tcp://MvcWebRole1:24233.
Inner Exception : No such host is known
Can you please tell me what I am missing here?
Azure SDK used : v2.0
Timing of your question couldn't be better. We also faced exactly the same issue and were scrathing our head as to what the problem could be. We had one project where everything worked perfectly fine and in one we were getting the same error. Based on our research, we have identified the problem with the Nuget package for caching. It seems a new version (2.1.0.0) was released yesterday and we found that if we install that package, we get this error. Can you check the package version in your case? The documentation states that this new version can only be used with the latest SDK (2.1) released today.
One solution would be to uninstall version 2.1.0.0 and install version 2.0.0.0. To install version 2.0.0.0, open Package Manager Console (View --> Other Windows --> Package Manager Console) and type following command there:
Install-Package Microsoft.WindowsAzure.Caching -Version 2.0.0.0
This fixed our problem. Hopefully it should fix yours too.
Here is a link to the Windows Azure Cloud Integration Engineering blog on how to deal with this same issue. They recommend upgrading to Azure SDK v 2.1 or rolling back as the accepted answer states.
http://blogs.msdn.com/b/cie/archive/2013/08/08/windows-azure-caching-2-1-0-0-no-such-host-is-known.aspx
This exception could also occur under compute emulator if for the role in the client library configuration there is no cache configured. In my case this happened on purpose, since the cache emulator has some problems that can slow down the test and debugging on the service.
In previous version of Windows Azure Caching, in this scenario the construction of DataCacheFactory would fail with an exception (handled by my code); with Windows Azure Caching 2.1 (and Azure SDK 2.1) in this same scenario the code would consider the role name as a server address and thus on DataCache construction would try to communicate with the non existing cache -- this leads to a 3 minute wait and the exception reported in the question.
I have changed my code to detect the new situation for this scenario -- you can find more detail in this SO question.
I installed a java web service on a machine that accesses an Oracle DB via JDBC on the same network. The service was functioning fine for several months until this morning when I installed another applicaiton that access the database using ODP.NET. I'm trying to figure out what went wronge to cause the ORA-01017 exceptions that I'm getting. This generally means that the login credentials are invalid, but the login credentials haven't changed. I also verified it the service's log4j output that it is indeed still trying to connect to the DB correctly.
I realize I don't have much to go off of here, but I'm trying to figure out what other dependencies that. The web service came packaged with ojdbc14.jar, so that tells me that it targets java1.4, but presumably would work fine in later java versions. Not too sure about it working with later java versions, however, it was working fine until today.
Does OJDBC rely on tnsnames.ora. If it depends on how the service uses OJDBC, then I'm not sure which it is doing. I suppose it's possible I deleted the tnsnames.ora, but that is a bit of a longshot. I also tried manging Apache Tomcat (running on Win Server 2003 x64) to target different java jvm versions, but to no avail. It was initially targeting the default jvm.
Are there other dependencies that I've missed here, or any diagnostic measures I could try? THe same web service is running on another machine on the same network which I am pretty sure is configured exactly the same. Again, it was working on both machines until today, and is now just working on the one.
Tomcat targets JDK 7.
Looks like replacing ojdbc14.jar with ojdbc6_g.jar did the trick. No idea why it was the case only for 1 of the 2 machines. ojdbc6 targets JDK 6, but ojdbc14 did, and should have continued to work. If anyone has any additional insight here, let me know.