I've a Wildfly 10 application server with an instance of Liferay 6.2 running on it and I've been trying to properly set the proxy settings. However all portlets requiring a external internet connection experience a time out
In the standalone.conf file I added the following line:
JAVA_OPTS="$JAVA_OPTS -Dhttp.proxyHost=[myhost]-Dhttp.proxyPort=[myport]"
and in then standalone.xml I've added the following two properties to the system-properties-attribute.
<property name="http.proxyHost" value="[myhost]"/>
<property name="http.proxyPort" value="[myport]"/>
I've also checked that the server's os is connected to the internet.
Does anyone know as to why this is not working?
Kind regards,
John
Related
Where can I find current instructions for how to set up Remote Debugging of Wildfly 20 from Eclipse 2020-06? My searches have found posts going back to 2014 they don't work. My most recent attempt is to follow https://tools.jboss.org/documentation/howto/configure_remote_server.html. This has no date on it and it is for connection to EAP 6.1 instead of Wildfly 20 but at least it is from tools.jboss.org and the instructions matched Eclipse 2020-06.
The problem is that when I right click on on the new Server just created with these instructions and select Debug I get the following error:
failed to copy to /opt/wildfly-20.0.1.Final/standalone/deployments/MyApp.war/META-INF/MANIFEST.MF on host 192.168.1.19
The requested path is not found on the remote system.
Here are what I think are important facts:
The path /opt/wildfly-20.0.1.Final/standalone/deployments DOES exist on the Wildfly 20 server # 192.168.1.19.
The Wildfly 20 server is started with /opt/wildfly-20.0.1.Final/standalone/deployments/MyApp.war in place. The Management console shows that MyApp is Deployed and I can access the app from a remote machine so Wildfly and the server are running.
I can connect from Eclipse to the Wildfly server using the Remote Systems item that creating the new Server created. In particular, I can use the root item to "roam around" the file system on the Wildfly server so that suggest to me that Eclipse can establish a connection to the Wildfly server.
The instructions in the URL above did not include this but in the Server's Properties the Web and Management ports were both 0. I manually set them to 8080 and 9990 respectively.
Thank you in advance.
Since your installation is on /opt I guess it was done with root privileges. I'm not sure your user has sufficient rights to be able to access those paths.
As far as I can tell /opt is the recommended installation location but I finally got the server to at least deploy so that problem is solved. See updated question at Attempt to debug a remote Wildfly 20 server failing.
How can i connect VisualVM to Wildfly 10?
I have put jboss-client jar in following folder and started visual vm:
Then i started visual vm
When i added jmx connection i get following:
Can anyone suggest what is wrong here? I have not put any authentication (not sure what authentication will it have as console have admin/pass but no password set anywhere else).
Can anyone suggest what is wrong here?
(I have multiple server groups and not sure where to add "remoting-connector use-management-endpoint="true" in domain.xml. I have added in 1 server group only.)
You need to extend VisualVM classpath (using "--cp:ad") with JBoss client jar, eg:
jvisualvm --cp:a $WF_HOME/bin/client/jboss-cli-client.jar
Then connect to your wildfly on admin port (usually 9990)
service:jmx:http-remoting-jmx://localhost:9990
See interesting article here:
https://nozaki.me/roller/kyle/entry/articles-wildfly-visualvm
I'm trying to migrate a web app from Websphere to JBoss.
I believe the first step is to port the configurations of the server. The main configuration file in Jboss is standalone.xml (or domain.xml for running multiple instances of a server).
Could you tell me what the equivalent of standalone.xml is in websphere ?
Thank you for your time.
There is no direct equivalent. WebSphere is administered via the administration console. If you run WebSphere Express you can connect directly to the app. server's administration port. If you run Network Deployment, you connect to the deployment manager console (DMGR).
The console has all the configuration. They are stored in many XML files, that can be a pain to use directly. Much easier with the console.
The default console port is 9060 (http) or 9043 (https).
URL:
http://yourserver:9060/ibm/console
https://yourserver:9043/ibm/console
See this technote: http://www-01.ibm.com/support/docview.wss?uid=swg21155098
for a bit more information.
You can look at this migration guide for JBoss AS 7.
https://docs.jboss.org/author/display/AS72/How+do+I+migrate+my+application+from+WebSphere+to+AS+7?_sscc=t
I have a question about the proxy configuration for Liferay Portal 7 CE. I have searched for quite a while, but haven’t found anything really helpful on the subject. There is already a question here on stackoverflow related to Liferay’s proxy configuration in Wildfly, but it has not been answered yet: Proxy Settings Wildfly
We use a squid proxy server for internet access (no authentication, just a proxy port and a host for HTTP and HTTPs). I would like to run Liferay portal on my local machine and therefore need to tell the portal to use the proxy for web access.
How do I do this? Do I make changes to
a) Liferay’s configuration files (i.e., the portal-ext.properties, I guess) or do I change
b) the configuration files of the application server, on which the portal is running on, or
c) change the configuration for the portlets (e.g. for the marketplace portlet)?
What options would I have to set in the respective configuration files?
Best regards,
Felix
Proxy configuration is splitted in two configuration files: system-ext.properties and portal-ext.properties.
In system-ext.properties you have to configure the proxy environment configuration settings that affects to whole JVM process:
http.proxyHost=192.168.0.200
http.proxyPort=4480
You have to create system-ext.properties file inside webapps/ROOT/WEB-INF/classes. (inside Liferay application classloader)
You have more information about system-ext proxy settings in following link: https://docs.liferay.com/portal/7.0/propertiesdoc/system.properties.html#HTTP
In portal-ext.properties you have to configure the proxy environment configuration settings that affects only to Liferay portal:
com.liferay.portal.util.HttpImpl.proxy.username=
com.liferay.portal.util.HttpImpl.proxy.password=
You have more information about portal-ext proxy settings in following link: https://docs.liferay.com/portal/7.0/propertiesdoc/portal.properties.html#HTTP
If your proxy has no authentication, only system-ext.properties settings are necessary
atm I'm facing some problems when I'm trying to connect to my JBoss AS 7.1.1 (on a Linux-Server) via JMX remotely and monitor my Java-Apps from a Win-7 client. I can only see the standard JVM settings but no app-specific ones.
I learned that I have to include the jars in the Classpath while starting jvisualvm on my Windows 7 client.
that looks like this:
"C:\Program Files (x86)\Java\jdk1.7.0_07\bin\jvisualvm.exe" -cp:a C:\Users\myuser\jboss-as-7.1.1.Final\modules
But still it is not working...when I try to connect via:
service:jmx:remoting-jmx://:9999
Is there any special configuration I have to change in my JBoss server besides enabling jmx-management in standalone.xml?
Thanks in advance!