I would want to connect my Laravel application to an SQL Server. Locally, it's all fine and perfect.
However following same steps on AWS EC2 does not give the required result.
Instead I am stuck with 'Could not find driver' exception on launching the application. Here are a few parameters to be considered.
And yes, have tried all solutions I could find.
Using yum for the EC2 environment
nginx and not apache is used
PHP version is 5.6.11
RHEL version is 7.1
Need your help please
Related
My goal is to confirm that one can use a Hawtio instance to monitor an instance running on a different machine.
I am using this example https://github.com/hawtio/hawtio-camel-wiki .
right now i have it running on my local machine in OSX and on a remote Ubuntu 18 machine. I try to connect them however i cant seem to monitor the instance on the other machine.
I then tried to just use the hawtIO jar to connect to that example running on the remote machine.
I first set my hawtio.proxyWhitelist or hawtio.proxyAllowList (i also tried using the hawtio JAR on my local machine) to whitelist the endpoints. (2.10 uses the former)
java -Dhawtio.proxyAllowlist=* -jar hawtio-app.jar
My issue is i am not sure what to put in the connection tabs. I have been trying port 61613 and the path as /api/jolokia but i cant seem to figure out where its running to connect to it.
hawtio-camel-wiki is an outdated project which was archived quite a while ago and is not relevant any longer. As to what info you need to put in the Connection tab, it depends on what remote JVMs you'd like to connect to. Generally speaking, they should provide a Jolokia endpoint with a specific port (e.g. 8080) and path (e.g. /jolokia) which you should input to the connection info.
For how to incorporate a Jolokia endpoint into your application, you can check https://jolokia.org/reference/html/agents.html. If you already have something to run, the JVM agent should be the easiest option.
You can also check some Spring Boot examples here:
https://github.com/hawtio/hawtio/tree/hawtio-2.10.1/examples
I was working on my project that was using remote heroku postgresql database, that was working fine. Actually, I was using the sqlalchemy library to connect to remote database and I was also used to queries that remote database through my Ubuntu terminal by using psql name_of_remote_database_url command. But after sometime it is giving me a bundle of errors.
And my project was on flask web application now, I am getting errors from this also.
enter image description here
I tried so much but I failed so, that's why I am posting my question here! If anyone knows then plz explain!
pg_hba.config something looks like this
Please read following Heroku support information:
FATAL: no pg_hba.conf entry for host "…”, user “u…”, database “d…”,
SSL off
You are attempting to establish a database connection without SSL. SSL
is required for all connections. Please see the documentation for your
postgres driver on how to establish encrypted connections.
Recommended solution:
Heroku Postgres & SSL
Actually, I was using remote heroku database url. After sometime, heroku did maintenance of my database and changed the url and I was considering the problem related to my system, but it was not related to that.
When I visited my gmail there was written in the heroku gmail that we changed the url of your remote database during maintenance.
Now, it's working fine!
I have installed OPDG using below document (https://learn.microsoft.com/en-us/azure/logic-apps/logic-apps-gateway-install). I could able to successfully install on my machine , But when I tried to create the gateway connection on Azure I couldn't find the instance. Here I have attached the screenshot. Appreciate if you can support.
Note : I am using the same email address to install and Azure Access and both region are same
I can't say for sure what your issue is but I would try troubleshooting it further with the help of Powershell, I had a similar issue where I could not install a new gateway. The issue for me was that a gateway was previously installed on the same machine. By using the PowerShell OnPremisesDataGatewayMgmt module I could remove what seemed to block me.
https://www.powershellgallery.com/packages/OnPremisesDataGatewayMgmt/1.0.0-beta1
I am using Tomcat 8.0.45 to deploy java based web application. I am using IIS 8.5 and BonCode connector. The App uses MS SQL db located on different server and IIS on another. Both are not on the same machine.
Issue:
- I followed steps for integratedSecurity=true, then copying sqljdbc_auth.dll in jre/bin.
- I also followed the steps to configure tag inside web.config along with userName (AD user) and password.
- I also mapped the user (AD user ) to SQL server db.
- But still I am not able to make it work. On Tomcat startup, I get error.
"Login failed for User 'MyDomain\ServerName$. ClientConnectionId:3b1161.....'.
My above steps could not wrong or incomplete. I can share logs but the above error is what I get in log file.
Can some one please direct me to any link or provide help here. Please note that mine in java based web app. I found lot of examples but they were all dot net based.
Thanks in advance.
I created a web application through the NetBeans IDE running a glassfish server and a Java Database.
I want to now have this be standalone and run on the startup of my physical machine.
I am having trouble figuring out how to get the database set up on the server though.
On my server machine, I've got Glassfish running and I figured out where to put my war file so that it will run on the server. However I can't figure out how to get the database setup that the application needs to run.
I don't know if it has to do specifically with the glassfish server ?
Or do I need to have a separate database program along with the server ?
I believe glassfish comes with a JavaDB but i can't figure out how to actually create and configure a database. All I can do is create connection pools and resources...
According to Oracle's javadb page, it's an implementation of Apache Derby.
You should be able to download and run Derby directly on your machine. The connection strings may be different than what they were when using the embedded version, but once you figure that out it should work fine. Good luck!