I'm using JBoss AS 7.1 Final with mod_cluster 1.2.0.
I've configured HTTPD as follows: http://pastebin.com/C1rnWc1U
However when I try to reach the page http://10.0.0.6:10001/mod_cluster-manager/ it returns a blank page: http://imgur.com/idHmOjp
Answer
That is correct. Unless there are worker nodes connected, there is nothing to display.
Do not use vulnerable code
Please, do not use mod_cluster 1.2.0 with your Apache HTTP Server. The version is completely obsolete and it contains serious bugs, including a code injection CVE and severe performance issue. Download mod_cluster 1.3.1.Final for httpd 2.4.x or build your own from the sources, if you desire httpd 2.2.x support. If you happen to need any any help with that, ask.
Related
Trying to use this project: https://github.com/blueimp/jQuery-File-Upload/
Our application server is a FreeBSD 11.2 with Apache 2.4.39 and PHP 7.2.17. I've downloaded their demo and receive the error net::ERR_CONNECTION_RESET in the browser console when trying to upload anything large enough to exceed 22 seconds exactly. It does appear to be server related as I've downloaded the same demo to another CentOS7 server where same file upload succeeds.
Although I have checked all my PHP variables for max upload size and memory limit, etc., would this demo be subject to PHP variables? I found the RequestReadTimeout Apache setting in the server that fails, not present in the working server, so I thought it could be the culprit, but I changed this setting from...
RequestReadTimeout header=20-40,MinRate=500 body=20,MinRate=500
To this...
RequestReadTimeout header=60-120,MinRate=500 body=120,MinRate=500
...and restarted Apache, but the same result. The developers on this server believe this issue only started after recent updates to the server were done that included Apache 2.4.33 upgraded to Apache 2.4.39. The PHP version did not change, however, there were many other packages updated as well as security patches to the FreeBSD OS. Can someone suggest what could fix this issue?
--UPDATE--
Okay, this is easily duplicated. I spun up a VM with a fresh install of FreeBSD 11.2, installed Apache 2.4.39 and the demo of this project. I adjusted these settings in the demo app to allow a large mp4 video to be uploaded...
acceptFileTypes: /(\.|\/)(gif|jpe?g|png|mp4)$/i,
maxFileSize: 999000000,
...and receive the same Unknown error at exactly 22 seconds into the download progress of an mp4 file of ~493MB. There must be a setting in Apache that needs to allow more time or other limit. And perhaps a change to the FreeBSD Apache 2.4 port somewhere between 2.4.33 and 2.4.39. My developers say this all started after that update.
Well, the RequestReadTimeout setting in Apache was the culprit. I had to completely disable, now it works.
same issue here - to fix, on a Centos 7 system, comment out this line:
LoadModule reqtimeout_module modules/mod_reqtimeout.so
from the 00-base.conf file, then restart httpd
good day.
I am trying to enable hot deploy on my JBoss 4.0.
I have tried to access to localhost:9990, but it doesn't work.
Is there any alternative way to enable it?
Thanks in advance.
JBoss 4.0 contradicts to port 9990.
The port 9990 is the management console access for JBossAS7 and WildFly.
JBoss 4.0 might have a JMX console which is accessible via 8080.
You can simpel use localhost:8080 and navigate from the welcome page.
Note that hot deploy is not recommended for productional JBossAS4/5 instances because of class loading issues, OOM errors.
You might use it for development.
Also JBossAS4 does not have managed deployments, simple drop the file to server/yourProfile/deploy and it will be picked up and deployed.
We are upgrading JBOSS from (4.0.2) to latest Jboss (Wildfly 9.0.1) for our J2EE webApp. After upgrading we found that EJB calls are stop responding after 1 hour of load test.
Please note that the other areas of application is working fine where EJB is not used. The problem is only with remote EJB calls.
We have to restart Jboss to fix the issue.
Do we need to any configuration (threads/EJB pool) in Jboss (Wildfly 9.0.1)?
I'd just like to drop in and say that we're experiencing the same thing. What I recall reading is that this happens when the Wildfly has to wait to long to return an answer and suddenly the whole service becomes unresponsive.
We were running 8.2.0 Final and the only suggestion I could find was to upgrade. After performing an upgrade to 9.0.1 Final we're still seeing this. There was seemingly more people experiencing this but I have not been able to find any solution yet. The issues I found on the JBoss issue tracker on this have all been rejected and they're implying that it's more open for community discussion.
I have this lingering notion that toying around with timeouts might help though I haven't had time to try this yet.
P.S. I'm not privileged enough to simply comment which I would preferred.
I'm totally a newbie in Java Enterprise and I have a lot stuff yet to learn. Right now I'm working which involves JMS using JBoss and ActiveMQ. An application sends messages to queues in JBoss and my goal is to access those messages using any message broker (in this case I tried to use ActiveMQ). So I think it's better for me to embed ActiveMQ to JBoss. I used the link below as the guidance :
http://activemq.apache.org/integrating-apache-activemq-with-jboss.html
I followed every single steps in the guide except that I used JBoss 4.2.3 and ActiveMQ 5.1.1. If this problem results from the different version of the tools, I think I can't help it out because other versions seem does not work on my machine. When I run JBoss to test whether the embedding is working or not, I can't see anything running on port localhost:61616 which is the default port for ActiveMQ, although JBoss seems run well. My question is :
Is any one know how to fix this? Or has anyone ever experienced such problem?
Is there any way to access queue in Jboss?
If this question is pretty ambiguous or need more details, let me know. Thanks in advance for any help.
I'm quite sure the embedded broker is started (transport vm://localhost) which results in a working JMS broker for that VM. But this broker isn't reachable from outside (via tcp or anything else)
Do you see any error in the log when launching jboss? I managed to make it work with Jboss 4.2 and ActiveMQ 5.4, and once integrated it only gives you a small hint that is working correctly with some info message saying "broker started in port ..." .
Also you can try to use the sample producers and receivers in ActiveMQ to test if the queue is working correctly.
If you still have problems I can try to help
I need to use some EJBs which are deployed on JBoss version 4.x from another EJB deployed on JBoss version 3.2.x. Is this possible?
I ask because I have a third party application which uses some strange bridge's to do that and don't know why (though I haven't try to do this on my own).
This is unfortunately not possible. One of the major drawbacks of remote EJBs is that there is nothing in the specification that guarantees or even suggests any kind of interoperability between different vendors or between different EJB versions from the same vendor.
In practice I found that at least with JBoss AS it never works. Even minor upgrades break binary compatibility completely. There have been some very hacky attempts with special class loaders that are only been given access to the client libs of the target JBoss AS, but this is very tricky to get right.
I guess this "strange bridge" you are talking about is using such a trick. Kudos to whoever build that bridge for getting this to work at all.
See this topic I started on the JBoss community forum for some more details: http://community.jboss.org/message/587180