I've installed Mule CE runtime on an AWS EC2 Lynx server and dropped my Anypoint Studio project into into the app folder, Mule starts fine and says my app is deployed but it appears Mule is not listening on port 80 as expected, what am I missing?
Mule CE runtime default port is not 80. Hope you have configured port 80 for mule soft CE.
For port configuration you can check configuration Here.
To check which port is being used by mule CE :
On Unix machine : netstat -tulpn | grep <port> (i.e 80 in your case, check for 7777 as well.)
On Windows machine :
Open Run prompt on Windows
Type perfmon /res ,press OK
On Resource Monitor, on Network tab, search for the port under Listening Ports
Great I can see port 80 & 8081 in use by Java now, my issue was two fold I was dropping my project folder onto apps once I changed to drop the Anypoint zip deployment file I saw a Java version error, rebuilt on 1.7, redeployed and it's working, thanks for your help
Related
I had made an EC2 instance on my AWS and also established the connection with RDC in my local system.
Installed my required modules and set up the environment for the Laravel successfully.
Xampp is also installed and the database connection is established
And my project is running perfectly in that RDC system's Localhost on port 8000
My problem I am not able to run my solution on port 8000 when I am hitting the server with my IP.
Basically, no port other than port 80 is opening via IP
How can I open my project on port 8000 via my IPv4 or IP?
I have got the solution to this.
Instead of deploying the project on localhost:{my_ip} to deploy it at 0.0.0.0:{my_ip}
In Laravel run this command in the workspace ok the project, it will be reflected on the respective domain as well.
php artisan serve --host 0.0.0.0 --port 8000
--host defines the hostname of the project and port defines the port on which you are planning to deploy your source.
it solved my problem hope it will help !!!
I have a Linux VM running with a Jenkins, Nexus and SonarQube server on it. The IP for the VM is 192.168.56.2 and I have no trouble accessing both Jenkins and Nexus on ports 8080 and 8081 respectively. However, when I try to access 192.168.56.2:9000 for SonarQube it just says 192.168.56.2 refused to connect.
When I run systemctl status sonar in the terminal it shows that SonarQube is active and running. I have opened the firewall to port 9000 and I have not changed any of the default settings. Does anyone have any idea what might be the issue?
SonarQube will only be listening on 'loopback' rather than on all inbound IP addresses. In your server's sonar.properties file, you'll need to set the Web information in order to access the server remotely, specifically the following values:
sonar.web.host: 192.168.56.2
sonar.web.port: 80 # if you want to use a port other than 9000
Also, in the web UI's Settings, under the "General" section, set the "Server base URL" value so that links and redirects issued by SonarQube target the correct location.
Spring Boot app is configured (default) to run Tomcat on port 8080. This application gets deployed on AWS via BoxFuse tool and exposed at port 8080 (as expected/configured).
I have tried setting server port to 80 in boot application properties but it causes permission denied issue and the solution seems to be modifying iptables or reverse proxy. ipTables modification is not possible due to boxFuse image/env not being editable.
Question: Is there a way in BoxFuse to setup the spring boot application on port 80 without actually setting up another instance for reverse proxy? It is an overhead to setup an instance just for port correction since can't change the iptables.
Also, Is it possible that this application is run with root privileges on the AWS instance so that I do not need to modify iptables or set up reverse proxy?
There is a -ports.Name option available when deploying the application with BoxFuse.
Docs: https://cloudcaptain.sh/docs/gradle/run
Example:
boxfuse -ports.http=80 -env=test run myapprepo/myapp:0.1
Verified on local dev environment. For Mac, it should be run as a privileged command via sudo
sudo boxfuse -ports.http=80 run myapprepo/myapp:0.1
To add, works for 443 too.
I have a EJB project build from IntelliJ 14, there are a lots of EJBs (include session Beans and JPA entity Beans) in the ear. This project is business services layer in my project.
My development and staging environments are both as Mac OS X Yosemite (10.10.3), JDK version is 1.8.0.x.
I deployed it in my development environment (WebLogic 12c -12.1.3, downloaded and installed at end of 2015) by using install it on administration console which is working fine, every time I reboot my development machine, it will start deploy it properly and provide services to EJB clients. But when I tried to deploy it in my staging environment (WebLogic 12c -12.1.3, downloaded and installed last week).
I found there is some different between two packages, early 12c was installed folder ~/mywls/wls12130 but the newly downloaded installed in ~/Oracle/Middleware/Oracle_Home. I believe there must have some different, but oracle name it as same version. I don't know why?
The two WebLogics have some different behaviour too, early version works IPv4 address on 7001 port, newer version works in IPv6 address on 7001.
Use same .ear package to deploy it in two machine, early WebLogic shows it works fine after a little and newer version too.
After reboot servers, early version can restart it self, every thing works well, but the newer version some time administration console waiting on 7001 on localhost and nowhere, if I run lsof I got such result:
macmini16g:~ cidylong$ sudo lsof -nP | grep TCP |grep 7001
java 284 xxxx 354u IPv6 0x43c511fce2ab4ac3 0t0 TCP 127.0.0.1:7001 (LISTEN)
java 284 xxxx 355u IPv6 0x43c511fce5646bc3 0t0 TCP [::1]:7001 (LISTEN)
In this situation, we can't connect to administration console from LAN as it only waiting for localhost.
If you restart server again, and run lost again, you may get different result, you probably see three rows as:
macmini16g:~ cidylong$ sudo lsof -nP | grep TCP |grep 7001
java 277 xxxx 354u IPv6 0x20915e23819739 0t0 TCP [::1]:7001 (LISTEN)
java 277 xxxx 355u IPv6 0x20915e263bd239 0t0 TCP 127.0.0.1:7001 (LISTEN)
java 277 xxxx 356u IPv6 0x20915e263bcd39 0t0 TCP [fe80:4::ca2a:14ff:fe58:cd42]:7001 (LISTEN)
This time you can connect through IPv6 in LAN, it is very funny.
There is an other issue with newer version, the same web application .ear not start properly after server reboot.
After we login to administration console, click in my domain -> deployments -> shows a table in the content section with all deployed applications. But the application State column shows Admin instead of Active, no thing shows in Health column instead of a green tick symbol and OK. Which means. If click in Admin linkage in State column, you was brought over to other page shows the detailed status, in last column (Target-Specific State), shows information as: "AdminServer=Failed".
If you tick the application in the list and click start button from the dropdown select, for example, servicing all requests selected, then the application will start and the State shows Active and Health column shows green tick and Ok.
Such means, every time server reboot, the application has to be manually started. Quite annoy!!
Any idea and advice are welcome.
Edit:
I configured in my domain/config/config.xml. but seems not works. nothing different.
<listen-address></listen-address>
I leave it empty or I put
<listen-address>10.0.1.1/24</listen-address>
no different.
I'm setting up Hudson as an integration server that I expect other developers and stackholders to access. Rather than have to pass around urls with a specific port, I'd like to configure Hudson to listen on port 80.
The default port from installing Hudson as a service is 8080. I'd like to change this to 80, on a Server 2008 R2 or windows 7 machine that isn't running IIS or Apache.
Do the following to reconfigure the port :
Edit hudson.xml (found in your hudson installation directory)
change the parameter string on line 44 to reference port 80 (--httpPort=8080 to --httpPort 80)
Depending on what plugins you may have set up, there may be other references to the hudson url. Find these by doing a text search in the hudson directory on ':8080' and removing the port number.
Disable the 'World Wide Web Publishing Service' service. By default, this service consumes port 80, which is the port we want to use.
Verify that your machine is configured to accept an external connection on port 80 (ie, open a firewall port)
Restart the Hudson service.