I am using ActiveMQ 5.5.1 version. But I am not able to access the web console in this version using http://127.0.0.1:8161/admin. But the same can work in ActiveMQ 5.3.0 version. Also, I see that jetty.xml file (which exists in ActiveMQ 5.3.0) does not exists under conf folder.
Does anyone know how to access web console in ActiveMQ 5.5.1?
Thanks in advance.
Just downloaded AMQ 5.5.1, started the activemq.bat file and successfully accessed localhost:8161/admin/
conf/jetty.xml does exist, for that matter.
Seems like your installation is corrupted. Consider download a fresh copy.
Related
We currently have a Glassfish Server 4.0 hosting our webpage, with Apache 2.2 as our Digital Certificate Holder in Ubuntu Server. One of our clients did a Vulnerability testing and discovered that a font (specifically, the glyphicons-halflings-regular.ttf) could be downloaded by using the URL:
http://<URL>/<War>/faces/resources/fonts/glyphicons-halflings-regular.ttf
Is there any way that we can avoid that download and instead redirect that Link to a error page when people try to access any link of that type?
Thanks in advance
Well, the solution I found was this
I opened the Glassfish Console, went to Configurations –> server-config -> virtual servers -> server and then I clicked on the Add Property button
the name was: Redirect1
The code was:
from=/<war>/faces/resources/fonts/glyphicons-halflings-regular.ttf url-prefix=https://<URL>/<war>/
I did it with all of the Cluster and configuration instances of Glassfish Cluster
After a Glassfish and Cluster restart everything was working fine.
Regards!
When I try to deploy saiku-ui-2.4.war to Glassfish I get
"There is no installed container capable of handling this application
ROOT. Please see server.log for more details."
The server.log shows:
[#|2013-08-16T17:50:36.595-0400|SEVERE|oracle-glassfish3.1.2|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=24;_ThreadName=Thread-2;|There
is no installed container capable of handling this application ROOT|#]
[#|2013-08-16T17:50:36.610-0400|INFO|oracle-glassfish3.1.2|org.glassfish.admingui|_ThreadID=23;_ThreadName=Thread-2;|Exception Occurred :Error occurred during deployment: There is no installed container capable of handling this application ROOT. Please see server.log for more details.|#]
Any idea how to get around this? I searched Saiku's own forum with no luck. I even have a post on there.
Saiku has a prepared package that comes with Tomcat. Saiku UI is deployed as Tomcat ROOT application. This package works fine but I want to try to deploy it on Glassfish.
What's interesting is Saiku has a download saiku-ui-master. This is a separate UI package that needs node.js installed. I've gotten this to work but I want to run it on Glassfish.
Solved it! Added WEB-INF and web.xml then it deployed with no issue!
Actually you need to unpack content of the saiku-ui.war in docroot of your domain as there is static content only.
When I deploy my apache cxf web service using eclipse I have to include the apache cxf library in the Web Deployment Assembly in order for it to work when I deploy it on my production apache web server. This is a problem because it makes the war file very large because the cxf library is included. If I exclude the library the war file is much smaller but the web service does not work when it is deployed on the live server even though the apache cxf library is on the live server.
My assumption is I need some kind of classpath reference so the live server can see the apache cxf installation but I am not familiar with how to do this as I am new to apache.
Thanks, Jesse
Put the cxf jars on folder tomcat/lib.
Ok, this workaround worked for me:
We can set the CXF lib path on the common.loader variable which is in $CATALINA_HOME/conf/catalina.properties file. You can add (after the comma) something like this:
common.loader=....,/path/to/cxf/home/lib/*.jar
I couldn't find a way to set an enviroment variable on tomcat in order to have something like: ${cxf.home}/lib/*.jar. I tried to put -Dcxf.home=$CXF_HOME in several places in catalina.sh but it never picked it up :( - hope someone can help on this later.
Restart tomcat and it will take cxf jars
Does anyone have a solution to this... Running RHEL 5.6, with Apache httpd 2.2.3-65.el5_8 and get this error when trying to start the webserver:
httpd: Syntax error on line 445 of /etc/httpd/conf/httpd.conf: Syntax error on line 2 of /etc/httpd/conf/mod_jk.conf: Cannot load /data/cf10/config/wsconfig/1/mod_jk.so into server: /data/cf10/config/wsconfig/1/mod_jk.so: undefined symbol: ap_get_server_description
I've looked all over Google, and there are some recommendations to compile my own connector, but I need the one from Adobe for CF10. Also the adobe site lists CF10 compatibility w/ Apache HTTPD 2.2.21, well with RedHat Enterprise they don't move the version number up, it gets reverse patched in the app repo.... ANY help would be awesome.
We are 50 days from going live with CF10 (or planning to), and really could use some help on getting this issue resolved.
In response to one of the posters here, I have indeed verified I'm using the x64 connector in my x64 OS based system.
Response from Adobe w/ SOLUTION!
Here's the response and resolution: You may download the connector from the following “RHEL_mod_jk.zip” web-link at:
http://helpx.adobe.com/coldfusion/kb/rhel-connector-configuration.html
Please note that you may proceed with the installation choosing not to configure the web server initially. Once CF is installed you may proceed to create the connector using the wsconfig tool at
\ColdFusion10\cfusion\runtime\bin
Find the instructions at http://help.adobe.com/en_US/ColdFusion/10.0/Admin/WSc3ff6d0ea77859461172e0811cbf364104-7fd9.html
Once the connector is in place you may simply navigate to \ColdFusion10\config\wsconfig\ folder and replace the mod_jk.so file with downloaded copy and restart Apache.
I wanted to add to the discussion my experience with install issues of CF. I've bumped up on two common issues with installing CF, the problems has been so consistent that I wrote a short "how to" blogpost so I wouldn't forget the next time I needed to deploy another server. While my blog post addresses CF 10 and Cent OS 6.4, this method has always worked as far back as I can remember (eg: CF 8)
http://www.greenvalleyconsulting.org/2013/05/16/installation-problem-coldfusion-10-and-centos-6-x/
Response from Adobe w/ SOLUTION!
Here's the response and resolution: You may download the connector from the following “RHEL_mod_jk.zip” web-link at: http://helpx.adobe.com/coldfusion/kb/rhel-connector-configuration.html
Please note that you may proceed with the installation choosing not to configure the web server initially. Once CF is installed you may proceed to create the connector using the wsconfig tool at \ColdFusion10\cfusion\runtime\bin
Find the instructions at http://help.adobe.com/en_US/ColdFusion/10.0/Admin/WSc3ff6d0ea77859461172e0811cbf364104-7fd9.html Once the connector is in place you may simply navigate to \ColdFusion10\config\wsconfig\ folder and replace the mod_jk.so file with downloaded copy and restart Apache.
I have downloaded the axis2.war file from the apache website.
I put it in the tomcat/webapps folder and it automatically creates a axis2 folder.
I open my web browser and navigate to http://127.0.0.0:8080/axis2/ and get the page that has services, validate and administration.
The problem is that if I click on any of the links a page with the apache logo is shown saying internal server error.
I have tried extracting the axis2.war my self and the file list is the same. the official apache website says that the axis2.war may not have unpacked correctly or it could be missing files. i have tries 1.6 and 1.5 of axis2 and still get the same error.
Can anyone explain what is causing this error and how to fix it ?
Please copy jstl-1.2.jar file in the %CATALINA_HOME%\lib folder. It will definitely solve the problem.
did you check weather tomcat is running.http://127.0.0.0:8080/.
please go through the following link to setup and test axis properly.
http://axis.apache.org/axis2/java/core/docs/userguide-installingtesting.html
turns out that it was the security settings blocking AXIS2
copy jstl-1.2.jar file in the Tomcat-Home\lib Folder, then your Problem Will Solve.
I had the same problem although i was not able to login on the axis2 administration on the localhost (http://localhost:8080/axis2/axis2-admin/) where i also got the "internal server error". After removing the old axis2 (axis2.1.7.5) and deploying an older version (axis2.1.7.0) it was possible for me to login with the default username and password (admin, axis2). It could be that the newer axis2 file was corrupted but i have not reinstalled the newer version yet.