This question is mainly for the GridGain support team.
We are trying to access the GridGain 6.0 repository but our corporate firewall is blocking it because it is using a non-standard port number:
<repository>
<id>GridGain External Repository</id>
<url>http://www.gridgainsystems.com:8085/nexus/content/repositories/external</url>
</repository>
Is there a reason why port 8085 is used instead of port 80? Is there another URL we can use which has the standard port number?
Thanks in advance.
GridGain has been moved to Maven Central. You don't need to specify repository anymore.
Related
We are currently using OpenSSO in some of our legacy applications and for few applications we want to use either web/jee policy agents with opensso.
Since OpenSSO is a dead project do we have any support for Apache 2.4 or Tomcat 7 or 8?
I know we can migrate to OpenAM, but currently we are not allowed to do so.
I don't believe that there are supported OpenSSO agents for those containers. You should really try to switch to OpenAM, the agents for AM does support Apache 2.4, and Tomcat 7/8.
Alternatively you can attempt to use the AM agents with your OpenSSO, but such setups were certainly never tested by ForgeRock.
I need to install these environment in the same machine.
Jira : ( installer, port: 8080, tomcat-jira)
Tomcat : ( tomcat for other applications, port: 8084 )
JBoss : ( port: 8086 )
Apache2: (as a proxy, mod_proxy, port: 80)
First I´d install Jira as a service, with their installer, so, It came with a tomcat embed, port 8080.
Then I installed apache as a proxy, It worked, I can now acces the jira like this: debian.local/jira intead of debian.local:8080.
But when I put tomcat in the same server the problems began:
I changed the tomcat ports on connectors and shutdown, but when I start it, the Tomcat from Jira goes down, both-ways.
The question is, how "un-recommended" is to install jira as a WAR deployed on my tomcat, intead of tomcat-jira?
What´s the best way to configure this environment? How must to be declared the CATALINA_HOME and CATALINA_BASE for this?
That´s all... thanks!
I think your installer-created CATALINA_HOME/CATALINA_BASE will probably be fine.
I would also not suggest trying to share one Tomcat instance with other applications due to potential conflicts between library versions (and also because you won't be able to shut down one application without shutting down the other).
The immediate problem is likely that you are trying to use the same shutdown port on both Tomcat instances. In JIRA's conf/server.xml, you will find a line like this:
<Server port="8004" shutdown="SHUTDOWN">
The configured port must be unique for each Tomcat instance, so you need to pick something that is not in use. (This is in addition to having a unique connector port declared in <Connector port="8080" ...).
If you use the same shutdown port, you will find that (say) your shutdown script for one instance ends up accidentally shutting down the other instance.
I'm managing a PLESK server and got this error from a client after they did a PCI scan on their site. What is ProFTP and is this really an issue? How would I go about fixing this issue?
Proftpd version 1.3.5 is used in latest version of Plesk. Please, consider upgrade possibility.
I don't mean to sound harsh but you are managing a Plesk server and you don't know what ProFTPd is? Its an FTP server. FTP is File Transfer Protocol and is the protocol used to upload web pages to websites. The version you are using is out of date and has more than one known vulnerability which could mean your server gets compromised. I'd recommend you upgrade.
Does anybody know of a way to do http session replication between web apps running in distributed apache karaf OSGi containers?
In this post, http://karaf.922171.n3.nabble.com/Pax-web-failover-LoadBalancing-td4029552.html, Jean-Baptiste Onofré says it's not available in apache cellar yet. Is this capability available anywhere yet?
I've been googling all day and haven't found any options -- Thanks for any help.
Steve
Karaf does not have it for pax-web as confirmed by JB in the above post. I am also waiting for him to provide us.
If you are in a hurry
You can use Hazelcast (already with Cellar) for session replication.
Hazelcast supports it and provide HazelcastWM for the same purpose.
Jetty does provide session replication and we use jetty as
servlet-container.You have to check possibility with it.
Try on forum for putting Tomcat instead of Jetty.
IIS does not work when I start applications like Skype since it also uses port 80.
Which port can I use to run IIS other than 80? (8080 does not work)
You can run IIS on any port you like, as long as it does not conflict with other applications. I am using 88, 8888 and other easy to remember ports.
You can find the common used port here: PORT NUMBERS, and it is safer to choose an unassigned TCP port.
Quote:
The Dynamic and/or Private Ports are those from 49152 through 65535
If IIS is working and you have troubles with an ASP.NET applications, those links might be helpful:
How to: Configure ASP.NET Applications for an ASP.NET Version
ASP.NET and IIS Configuration
ASP.NET IIS Registration Tool (Aspnet_regiis.exe)
IIS and ASP.NET: The Application Pool
If you are still having troubles, it would be helpful to provide more information about your environment, the steps taken so far to solve the problem, and retagging the question (append asp.net for example)
Well you can disable skype to use port 80. Click tools --> Options --> Advanced --> Connection and uncheck the appropriate checkbox.
Port 8080 might have been used by another process in your computer.
Do netstat in command prompt to find out which server/process is using it.
Have a look at this page (http://en.wikipedia.org/wiki/Port_number) it gives you full explanation on how to use port number
Also remember, when running on alternate ports, you need to specify the port on the URL:
http://www.example.com:8080
There may be firewalls or proxy servers to consider depending on your environment.
you can configure IIS in IIS Mgr to use EVERY port between 1 and 65535 as long it is not used by any other application
Stopping Skype from using port 80: http://forum.skype.com/lofiversion/index.php/t15582.html
I'm going to make a few assumptions and come at the problem from a different angle... in that because you have skype installed and running on the same machine, that it is not a production machine and instead used for testing / development?
If so, you may wish to look at alternatives to IIS completely to alleviate your issue. If you use IISExpress or the web server built into recent versions of Visual Studio, they will automatically pick a port for you.
Of course this does mean that it's not particularly useful for giving other people access, but is fine for local development for personal use.
I think the other answers probably offer a better alternative in most situations, but this may offer a different insight.
Here is an intro to IIS Express: http://learn.iis.net/page.aspx/860/iis-express/
You have to configure the port first for example 127.0.0.1:91 then you need to allow access to port 91
from windows firewall->>advance setting->>inbound rules->> new rule.
then check port->> assign new port (91). then next to finished.
After this 127.0.0.1:91 should be accessible from the web.