[JBoss Messaging] - Re: killing messaging server shutsdown my app?
by ccfellows
Ok, more details then:
Java1.5 application running on Tomcat 5.0, using log4j1.2.14 JMSAppender with JBoss 1.2.0.GA messaging jars. We'll say its running on serverA:8080.
MDB running on JBossAS 4.0.5 with JBoss Messaging 1.2.0.GA. We'll say running on serverB:2020 and jndi on serverB:1099.
Both servers are linux.
if I start both the messaging and java app, the MDB picks up logs successfully and as expected. The problem I'm experiencing is that if I run the following script on serverB .../jboss/bin/shutdown.sh --server=serverB:1099, it not only kills my messaging application but also the associated tomcat java app.
On shutdown, will the JMS' topics send messages to their clients' that its shutting down? I was under the assumption that communication was one-way only, from client to jms topic.
Here's the log4j.xml from my tomcat java app:
| <?xml version="1.0" encoding="UTF-8" ?>
| <!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">
| <log4j:configuration xmlns:log4j='http://jakarta.apache.org/log4j/'>
|
| <appender name="CONSOLE" class="org.apache.log4j.ConsoleAppender">
| <layout class="org.apache.log4j.PatternLayout" >
| <param name="ConversionPattern" value="%d{ISO8601} %-5p %c %m%n" />
| </layout>
| </appender>
|
| <appender name="FILE" class="org.apache.log4j.DailyRollingFileAppender">
| <param name="File" value="mylog.log" />
| <param name="DatePattern" value="'.'yyyy-MM-dd" />
| <param name="Append" value="false" />
|
| <layout class="org.apache.log4j.PatternLayout" >
| <param name="ConversionPattern" value="%d{ISO8601} %-5p %c %m%n" />
| </layout>
| </appender>
|
| <appender name="JMS" class="org.apache.log4j.net.JMSAppender">
| <errorHandler class="org.apache.log4j.varia.FallbackErrorHandler">
| <root-ref/>
| <appender-ref ref="FILE" />
| </errorHandler>
|
| <param name="InitialContextFactoryName"
| value="org.jnp.interfaces.NamingContextFactory" />
| <param name="ProviderURL" value="jnp://serverB:1099" />
| <param name="URLPkgPrefixes"
| value="org.jboss.naming:org.jnp.interfaces" />
| <param name="TopicConnectionFactoryBindingName"
| value="ConnectionFactory" />
| <param name="TopicBindingName" value="/topic/myLoggingTopic" />
| <param name="LocationInfo" value="true" />
| </appender>
|
| <logger name="com.myapp">
| <level value="DEBUG" />
| </logger>
|
| <logger name="net.sf.hibernate">
| <level value="INFO" />
| </logger>
|
| <logger name="net.sf.ehcache">
| <level value="INFO" />
| </logger>
|
| <logger name="org.apache">
| <level value="INFO" />
| </logger>
|
| <logger name="org.apache.struts">
| <level value="WARN" />
| </logger>
|
| <logger name="org.jboss">
| <level value="WARN" />
| </logger>
|
| <logger name="org.logicalcobwebs">
| <level value="INFO" />
| </logger>
|
| <logger name="org.springframework">
| <level value="INFO" />
| </logger>
|
| <root>
| <level value="DEBUG" />
| <appender-ref ref="JMS" />
| <appender-ref ref="CONSOLE" />
| </root>
|
| </log4j:configuration>
|
Also, here's my messaging-service.xml from the messaging/deploy folder:
| <?xml version="1.0" encoding="UTF-8"?>
| <server>
| <loader-repository>jboss.messaging:loader=ScopedLoaderRepository
| <loader-repository-config>java2ParentDelegation=false</loader-repository-config>
| </loader-repository>
|
| <mbean code="org.jboss.jms.server.destination.TopicService" name="jboss.messaging.destination:service=Topic,name=myLoggingTopic" xmbean-dd="xmdesc/Topic-xmbean.xml">
| <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
| <depends>jboss.messaging:service=PostOffice</depends>
| <attribute name="SecurityConfig">
| <security>
| <role name="guest" read="true" write="true"/>
| <role name="publisher" read="true" write="true" create="false"/>
| <role name="durpublisher" read="true" write="true" create="true"/>
| </security>
| </attribute>
| </mbean>
|
| </server>
|
Thanks,
Chris
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4034795#4034795
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4034795
19 years
[JBoss Seam] - Re: Anybody else experience a4j:support *not* calling action
by gzoller
Ok, this might be a bug...
Everything on the page was always rendered, so that wasn't it. By process of elimination I identified the code causing the problem.
This worked: (action method app.setTimecardWorker was called when item changed)
| <h:outputLabel styleClass="textLabel2" for="worker">Worker</h:outputLabel>
| <s:decorate>
| <h:selectOneMenu id="worker"
| value="#{timecardHome.instance.workerName}">
| <f:selectItems value="#{app.activeWorkers}" />
| <a4j:support event="onchange"
| action="#{app.setTimecardWorker(timecardHome.instance)}"
| reRender="rate"
| ajaxSingle="true"/>
| </h:selectOneMenu>
| </s:decorate>
| <h:outputLabel styleclass="textLabel2" for="rate">Rate $</h:outputLabel>
| <s:decorate>
| <h:inputText id="rate"
| required="true"
| size="3"
| value="#{timecardHome.instance.hourlyRate}"/>
| </s:decorate>
| <h:outputLabel styleClass="textLabel2" for="hours">Hours</h:outputLabel>
| <s:decorate>
| <h:inputText id="hours"
| required="true"
| size="3"
| value="#{timecardHome.instance.hours}"/>
| </s:decorate>
| <h:outputLabel styleclass="textLabel2" for="description">Description</h:outputLabel>
| <s:decorate>
| <h:inputText id="description"
| required="true"
| size="40"
| value="#{timecardHome.instance.description}"/>
| </s:decorate>
|
This didn't (no action method was called when same item was changed)
| <h:outputLabel styleClass="textLabel2" for="worker">Worker</h:outputLabel>
| <s:decorate>
| <h:selectOneMenu id="worker"
| value="#{timecardHome.instance.workerName}">
| <f:selectItems value="#{app.activeWorkers}" />
| <a:support event="onchange"
| action="#{app.setTimecardWorker(timecardHome.instance)}"
| reRender="rate"
| ajaxSingle="true"/>
| </h:selectOneMenu>
| </s:decorate>
| <h:outputLabel styleclass="textLabel2" for="rate">Rate $</h:outputLabel>
| <s:decorate>
| <h:inputText id="rate"
| required="true"
| size="3"
| value="#{timecardHome.instance.hourlyRate}"/>
| </s:decorate>
| <h:outputLabel styleClass="textLabel2" for="month">Month</h:outputLabel>
| <s:decorate>
| <h:selectOneMenu id="month"
| converter="#{monthconverter}"
| value="#{timecardHome.instance.month}">
| <f:selectItems value="#{app.months}" />
| </h:selectOneMenu>
| </s:decorate>
| <h:outputLabel styleClass="textLabel2" for="hours">Hours</h:outputLabel>
| <s:decorate>
| <h:inputText id="hours"
| required="true"
| size="3"
| value="#{timecardHome.instance.hours}"/>
| </s:decorate>
| <h:outputLabel styleclass="textLabel2" for="description">Description</h:outputLabel>
| <s:decorate>
| <h:inputText id="description"
| required="true"
| size="40"
| value="#{timecardHome.instance.description}"/>
| </s:decorate>
|
It seems adding the second select list did something to interfere with a4j:support calling the action method on the first select list. Bizarre!
Any clues?
Greg
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4034787#4034787
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4034787
19 years