I haven't tried the console and I was thinking it may be more useful than
a standard JMX based management console but it sounds like not.

I'm not using it now, so I wouldn't miss it if it were dropped from RC3.

 -John


-- 
John David Osborne

Research Associate
University of Alabama at Birmingham
Biomedical Informatics
Center for Clinical and Translational Science
1720 7th Avenue South
Sparks Building, Suite 175
Birmingham, AL, 35294





On 10/14/13 3:56 PM, "Jaroslaw Cwiklik" <[email protected]> wrote:

>Hi, the web console requires additional dependencies which will bloat
>uima-as tarball.
>
>Does anyone feel strongly about bundling AMQ Web Console with uima-as?
>
> For those who may not know it, this is a web based admin gui for managing
>AMQ via http. I rarely
>use it since I prefer JMX based management console like jConsole.
>
>If you need the web console you can install a full version of AMQ (say
>5.6.0) and set
>ACTIVEMQ_HOME environment variable to the location where AMQ is installed.
>
>At this point I plan for not including web console in the RC3.
>
>Jerry
>
>
>On Mon, Oct 14, 2013 at 9:47 AM, Jaroslaw Cwiklik <[email protected]>
>wrote:
>
>> Hi, I am working on RC3 and will make sure that this is working.
>> Thanks for bringing this up.
>>
>> Jerry
>>
>>
>> On Sun, Oct 13, 2013 at 12:41 AM, John David Osborne (Campus) <
>> [email protected]> wrote:
>>
>>> Hello,
>>>
>>> I ran into this problem in RC2 (although it has probably been around
>>> earlier). Basically I can't launch the web console because I don't
>>>have JSP
>>> support even after importing jetty.xml. I suspect this is because JSP
>>> support isn't explicitly built in - see:
>>>
>>> 
>>>http://stackoverflow.com/questions/3521654/missing-jsp-support-in-jetty-
>>>or-confusing-log-message
>>>
>>> I'm not sure where jetty actually gets instantiated from to add that
>>>JSP
>>> option - perhaps I should talk to the ActiveMQ people? Also do people
>>>find
>>> the web console useful?
>>>
>>>  -John
>>>
>>>
>>>
>>> INFO: Invoke the following command to create a configuration file
>>> /web/uima/apache-activemq/bin/activemq setup [ /etc/default/activemq |
>>> /home/monit/.activemqrc ]
>>>
>>> INFO: Using java '/web/java/bin/java'
>>> Java Runtime: Sun Microsystems Inc. 1.6.0_41 /web/jdk1.6.0_41/jre
>>>   Heap sizes: current=1004928k  free=999683k  max=1004928k
>>>     JVM args: -Xms1G -Xmx1G
>>> -Djava.util.logging.config.file=logging.properties
>>> -Dactivemq.classpath=/web/uima/amq/conf;
>>> -Dactivemq.home=/web/uima/apache-activemq -Dactivemq.base=/web/uima/amq
>>> -Dactivemq.conf=/web/uima/amq/conf -Dactivemq.data=/web/uima/amq/data
>>> ACTIVEMQ_HOME: /web/uima/apache-activemq
>>> ACTIVEMQ_BASE: /web/uima/amq
>>> ACTIVEMQ_CONF: /web/uima/amq/conf
>>> ACTIVEMQ_DATA: /web/uima/amq/data
>>> Loading message broker from:
>>> xbean:file:/web/uima/amq/conf/activemq-nojournal.xml
>>> INFO  XBeanBrokerFactory$1           - Refreshing
>>> org.apache.activemq.xbean.XBeanBrokerFactory$1@c832d2: startup date
>>>[Sat
>>> Oct 12 23:28:46 CDT 2013]; root of context hierarchy
>>> INFO  BrokerService                  - Using Persistence Adapter:
>>> MemoryPersistenceAdapter
>>> INFO  BrokerService                  - ActiveMQ 5.6.0 JMS Message
>>>Broker
>>> (localhost) is starting
>>> INFO  BrokerService                  - For help or more information
>>> please see: http://activemq.apache.org/
>>> INFO  ManagementContext              - JMX consoles can connect to
>>> service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi
>>> INFO  TransportServerThreadSupport   - Listening for connections at:
>>> tcp://walnut.hs.uab.edu:61616
>>> INFO  TransportConnector             - Connector openwire Started
>>> INFO  BrokerService                  - ActiveMQ JMS Message Broker
>>> (localhost, ID:walnut.hs.uab.edu-37413-1381638527824-0:1) started
>>> INFO  Server                         - jetty-7.6.7.v20120910
>>> INFO  StandardDescriptorProcessor    - NO JSP Support for /admin, did
>>>not
>>> find org.apache.jasper.servlet.JspServlet
>>> INFO  ContextHandler                 - started
>>> 
>>>o.e.j.w.WebAppContext{/admin,file:/web/apache-uima-as-2.4.2/apache-activ
>>>emq/webapps/admin}
>>> INFO  WebAppContext                  - WebApp@17649447 at
>>> http://0.0.0.0:8161/admin
>>> INFO  StandardDescriptorProcessor    - NO JSP Support for /demo, did
>>>not
>>> find org.apache.jasper.servlet.JspServlet
>>> INFO  ContextHandler                 - started
>>> 
>>>o.e.j.w.WebAppContext{/demo,file:/web/apache-uima-as-2.4.2/apache-active
>>>mq/webapps/demo}
>>> INFO  WebAppContext                  - WebApp@17649447 at
>>> http://0.0.0.0:8161/demo
>>> INFO  StandardDescriptorProcessor    - NO JSP Support for /fileserver,
>>> did not find org.apache.jasper.servlet.JspServlet
>>> INFO  ContextHandler                 - started
>>> 
>>>o.e.j.w.WebAppContext{/fileserver,file:/web/apache-uima-as-2.4.2/apache-
>>>activemq/webapps/fileserver}
>>> INFO  WebAppContext                  - WebApp@17649447 at
>>> http://0.0.0.0:8161/fileserver
>>> INFO  AbstractConnector              - Started
>>> [email protected]:8161
>>>
>>
>>

Reply via email to