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.
Related
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
I have installed wakanda server on an Amazon EC2 server running ubuntu by following this utube video: https://www.youtube.com/watch?v=uSQODnB7wRU .
Now the video is for an older version but I have followed along successfully until I actually launch wakanda on the server. This is what I get in the console:
Welcome to Wakanda Server 10 build 10.187175
Publishing "DefaultSolution" solution
The solution's log file will be stored in the "/home/ubuntu/.Wakanda Server/UserCache/Wakanda Server/DefaultSolution-1882/Logs/" folder
The Administration Web Server cannot listen for connections on port 8080 or secure port 4433 on all IP addresses
You can customize the Administration Web Server's ports with the "--admin-port" and "--admin-ssl-port" options
, then when I try to log into it via the browser it says the connection dropped! Any help would be much appreciated, it seams I need to restrict the IP addresses which can access, but how?
Your wakanda server tried and failed to listen on 8080 and/or 4433
Check the following things:
Are the ports 8080 and/or 4433 used by other processes? (sudo netstat -tapen | grep :8080, if a result is found, then yes another process uses 8080. Check 4433 also)
You may found that wakanda server is already running as a service:
yes you should use this service (create and edit /etc/default/wakanda, add WAKANDA_SOLUTION_AT_STARTUP=your_path and restart with sudo /etc/init.d/wakanda restart)
or to continue starting it manually, stop the service first (sudo /etc/init.d/wakanda stop)
Has the current user the right to listen on those ports? (try running the server with sudo just to check, then use authbind or equivalent)
Can you use alternative ports? (use --admin-port and --admin-ssl-port wakanda server options)
wakanda-server --help will give you the list of options available, especially --solution=VALUE to provide the path to your solution.
We have to use port 80 for our server. But when I was trying to use it in Mac, it always said that the 80 is used, but I don't know which program uses it.
I searched it in Google, and someone said it's about apache, but I tried, which is not working. I found this: https://gist.github.com/kujohn/7209628 , but seems it's not working visiting our server by IP address.
I really don't know what's going on and how can I find out which program using port 80 and stop it.
Many thanks if anyone can help, I'm new using Mac. Thanks.
To find out what process is using port 80
go to Applications
open utilities.
open Activity Monitor.
click on the Memory tab,
look at the ports and the processes using them. Find port 80 and select it
go to the view on the menu bar and choose Quit process.
This will just kill the process, it will not stop a server instance that is already running from continuing to run.
(Correction: the Ports column shows the number of open ports (and files?), not the port number)
It is not clear if you are using a database management system or not and which one but one method that has worked for me using MAMP is as follows.
stop the server by using sudo apachectl stop command.
then change the port to port 80.
then restart your servers.
type the following in Terminal
sudo lsof -i -n -P | grep TCP
you will get a list - e.g. dropbox listens on 80
you can copy the output to a text editor, etc to search
On Mac ports below 1024 can only be bound by the root user.
Try launching your server as root user (with sudo), or try to use a port above 1024.
You can also try to add root permissions to your user in /etc/sudoers
# root and users in group wheel can run anything on any machine as any user
root ALL = (ALL) ALL
%admin ALL = (ALL) ALL
your_user_here ALL = (ALL) ALL
I was having this issue, apache was disabled via launchctl, but was still tying up port 80 after launch, I could start up apache and it would work, but after unloading it, I couldn't start up anything on port 80. I was using the built in web server for Python as an easy test. It would work on port 81, but not on port 80.
sudo python -m SimpleHTTPServer 80 -- wouldn't work
sudo python -m SimpleHTTPServer 81 -- would work
Here are the symptoms:
$ launchctl unload -w /System/Library/LaunchDaemons/org.apache.httpd.plist
/System/Library/LaunchDaemons/org.apache.httpd.plist: Could not find specified service
$ sudo lsof -i ':80'
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
Python 3353 root 3u IPv4 0xe455777a82799f05 0t0 TCP *:http (LISTEN)
The fix for me (after way too much searching) was simple:
sudo pfctl -F all
This flushed the packet filter, releasing port 80 (and others I assume 8080, 443, whatever ports apache might be tying up)
After that, and relaunching the python server, it came right up.
Might be Skype that is using port 80. If you have Skype installed and running try to change to a different port in the settings.
Port numbers in the range from 0 to 1023 are classified as 'well-known' and port number 80 is reserved for HTTP. Typically you have servers listening on port 80 to handle HTTP requests.
Source:
http://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers
I am trying to setup CI on an Xcode Server. I have a Mac running OSX Server with Xcode Services up and running (seems to be working). The Mac is hosted in the cloud.
When I try to add the server to Xcode on my local Mac dev machine, it says "Xcode Server is unavailable". What "server address" do I use. I tried the IP address as well as the machinename.companyname.com address.
Note I have enabled the "file sharing" service and this works fine using machinename.companyname.com.
I configured my router to forward the relevant traffic to the server. This process is called port forwarding.
Opening these ports worked for me
Protocol Port Range ---- Comment
TCP 22 ---- ssh
TCP 80 ---- http
TCP 443 ---- https
TCP+UDP 3690 ---- svn
TCP+UDP 9418 ---- git
TCP+UDP 20300 ---- xcode1
TCP+UDP 20343-20345 ---- xcode2
reference: https://support.apple.com/en-ae/HT202944
I am having the same problem you are. My server is not in the cloud, but it is setup to be accessible outside of my network. I am able to add my server because it is seen by Bonjour. Everything works fine that way. However, I can't add the server by using the IP or the www address.
I've verified that TCP ports 22, 80, and 443 are forwarding correctly. I also have TCP/UDP 3690 and 9418 forwarded correctly.
One thing I wanted to add is that I can add repositories that exist on the server without issue. It is just adding the server that is causing a problem.
I have filed a bug report with Apple and will comment back here as soon as I get a response.
I think I solved my own problem. After upgrading to Xcode6, need to upgrade to Yosemite too. Don't know why but this seemed to fix the issue.
I'm attempting to debug the startup of a service using the IFEO method (which I've successfully done on server versions prior to Windows 2012 on scenarios other than startup). The Debugger reg value is c:\debuggers-x64\cdb.exe -server tcp:port=1234. I then start the service and verify that cdb.exe is listening using netstat -na | findstr 1234 (I verified nothing was listening on this port prior to starting the service). Then I attempt to connect to the debugging server like this windbg.exe -remote tcp:server=localhost,port=1234 but it hangs for maybe 15-30 seconds and then fails. I try again and while it's hanging I run netstat -na | findstr 1234 again and it shows cdb.exe listening on port 1234 and it also shows a SYN_SENT to 127.0.0.1 on port 1234 (presumably sent by windbg.exe). It remains in the SYN_SENT state until windbg.exe reports a failure to connect.
So TCP connection establishment never completes. I checked the firewall and it's turned off. I also tried using the IP address of the network adapter (as opposed to localhost) but I get the same behavior. I also tried having cdb.exe listen on a port > 5000 but that also has the same behavior.
Does anyone know if there's new security introduced in Server 2012 for accessing TCP ports?
thanks