[JBoss AOP Users] - Problem load balancing JMS
by vickirk
Hi,
I'm having a bit of trouble load balancing my message producing SSBs and my MDBs under jboss 4.2.1. I have got a singleton JMS successfully switching between nodes when I shut the active one down so hopefully I'm almost there.
However, my SSBs fail when trying to get the connection factory for the queue if they are not on the node running the jms instance. These a re EJB3 beans, the connection factory for my SSB is injected via
@Resource(mappedName="ConnectionFactory")
| private QueueConnectionFactory connectionFactory;
and the code that fails is
InitialContext ctx = new InitialContext();
| QueueConnection qu = connectionFactory.createQueueConnection();
| QueueSession session = qu.createQueueSession(false,
| Session.AUTO_ACKNOWLEDGE);
| Queue queue = (Queue) ctx.lookup("queue/SystemLogQueue")
Presumably I need to make this refer to the HAJNDI?
Can anyone recommended the best way to make this maintainable so it can be deployed under a clustered/non-clustered environment with the least effort?
Kind Regards, Vic
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4257338#4257338
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4257338
16 years, 7 months
[JBoss Portal Users] - css with multiple portlets
by Gamba
Hi,
I'm working with
richfaces 3.3.1.GA
portletbridge 1.0.0.CR1
facelets 1.1.14
jsf 1.2_13
jboss 4.2.3.GA
I have a problem using own css-statements and showing more than one portlet with a html-table-element on a portal-page.
First portlet defines a series of *.xhtml-sites for a panel-bar subnavigation (with ui:include) and one of the included xhtml sites defines own css-elements, for a table-layout:
| <?xml version="1.0" encoding="utf-8"?>
| <ui:composition xmlns="http://www.w3.org/1999/xhtml"
| xmlns:h="http://java.sun.com/jsf/html"
| xmlns:f="http://java.sun.com/jsf/core"
| xmlns:ui="http://java.sun.com/jsf/facelets"
| xmlns:a4j="http://richfaces.org/a4j"
| xmlns:rich="http://richfaces.org/rich">
|
| <style type="text/css">
| .pisTableClass {
| width: 295px;
| border-top: 0px;
| border-left: 0px;
| border-bottom: 0px;
| border-right: 0px;
| margin: 0px 0px 0px 0px;
| padding: 0px 0px 0px 0px;
| empty-cells: hide;
| }
|
| .pisColumnClass {
| border-top: 0px;
| border-left: 0px;
| border-bottom: 0px;
| border-right: 0px;
| margin: 0px 0px 0px 0px;
| padding: 1px 1px 1px 1px;
| white-space: nowrap;
| empty-cells: hide;
| }
| ...
| </style>
|
|
| <h:form id="pisFormClassifyPanel">
| <a4j:outputPanel id="pisClassifyPanel" styleClass="pisTableClass">
|
| <rich:dataGrid value="#{classifyBean.klassenProperties}"
| var="props" id="pisClassifyTable" styleClass="pisTableClass"
| columnClasses="pisColumnClass" columns="1">
| ...
| </rich:dataGrid>
| </h:form>
|
Above styles should hide the border of the table and this is what happens.
But with a second portlet on the same portal-page and a second html-table-element ...
| <h:form>
| <rich:dataTable id="testTableForCSS">
| </rich:dataTable>
| </h:form>
|
... the border is available again. Without the second portlet on the page everything works as expected.
Some not acceptable workaorund: With integrating the same CSS inside the *.xhtml of the second portlet the border disappears. It seems that the table-css is overwritten in the other portlet on the portal-page. No render option works me ...
Here are the parts of my web.xml:
| <context-param>
| <param-name>org.richfaces.LoadStyleStrategy</param-name>
| <param-value>ALL</param-value>
| </context-param>
|
| <context-param>
| <param-name>org.richfaces.LoadScriptStrategy</param-name>
| <param-value>ALL</param-value>
| </context-param>
|
| <context-param>
| <param-name>javax.portlet.faces.renderPolicy</param-name>
| <param-value>DEFAULT</param-value>
| </context-param>
|
| <context-param>
| <param-name>org.ajax4jsf.RESOURCE_URI_PREFIX</param-name>
| <param-value>rfRes</param-value>
| </context-param>
|
.. and the jboss-portlet.xml ...
| <portlet>
| <portlet-name>DPA...</portlet-name>
| <header-content>
| <script src="/faces/rfRes/org/ajax4jsf/framework.pack.js" type="text/javascript"></script>
| <script src="/faces/rfRes/org/richfaces/ui.pack.js" type="text/javascript"></script>
| <link rel="stylesheet" type="text/css" href="/faces/rfRes/org/richfaces/skin.xcss"/>
| </header-content>
| </portlet>
|
Any hints?
Thx,
Gamba
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4257336#4257336
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4257336
16 years, 7 months
[EJB 3.0 Users] - @Resource and systemproperties-service.xml
by jprio
Hi all,
I have a SLSB with a @Resource annotation :
import org.jboss.ejb3.annotation.Depends;
@Stateless(name = "SimpleSLSBResource", mappedName = "SimpleEJB30SLSBResource")
@Remote({com.jp.ejb3.ISimpleSLSB.class})
@Depends({"jboss:type=Service,name=SystemProperties"})
public class SimpleSLSBResource implements ISimpleSLSB {
@Resource(name = "serverName")
String = "testserver";
and i also have a ejb-jar.xml to define the resource :
<ejb-name>SimpleSLSBResource</ejb-name>
<env-entry>
<env-entry-name>serverName</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>${serverName}</env-entry-value>
</env-entry>
and finally a systemProperties-service.xml to set the value of the resource :
serverName=production
When i start my JBoss AND THEN deploy my EJB, "serverName" is resolved to "production" => OK
When i start my JBoss with my EJB in the deploy directory, "serverName" is not resolved (= ${serverName}) => KO
I'm working on JBoss 5.1.0GA, jdk6.
Have I made a mistake with the @Depends tag ?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4257332#4257332
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4257332
16 years, 7 months
[Beginner's Corner] - There are too many DEBUG written to the
by thomas2008ch
I have a problem: There are too many DEBUG messages written to the "server.log" file so the hard disc gets full every several days. The DEBUG message looks as follow.
|
| 2009-09-25 16:18:54,204 DEBUG [org.jboss.system.ServiceController] Creating service jboss:service=Naming
| 2009-09-25 16:18:54,205 DEBUG [org.jboss.naming.NamingService] Creating jboss:service=Naming
| 2009-09-25 16:18:54,205 DEBUG [org.jboss.naming.NamingService] Created jboss:service=Naming
| 2009-09-25 16:18:54,225 DEBUG [org.jboss.system.ServiceController] Creating dependent components for: jboss:service=Naming dependents are: []
| 2009-09-25 16:18:54,225 DEBUG [org.jboss.system.ServiceController] Creating service jboss:service=Naming
| 2009-09-25 16:18:54,225 DEBUG [org.jboss.system.ServiceController] Ignoring create request for service: jboss:service=Naming
| 2009-09-25 16:18:54,225 DEBUG [org.jboss.system.ServiceController] Creating service jboss:service=JNDIView
| 2009-09-25 16:18:54,225 DEBUG [org.jboss.naming.JNDIView] Creating jboss:service=JNDIView
| 2009-09-25 16:18:54,225 DEBUG [org.jboss.naming.JNDIView] Created jboss:service=JNDIView
| 2009-09-25 16:18:54,226 DEBUG [org.jboss.system.ServiceController] Creating dependent components for: jboss:service=JNDIView dependents are: []
| 2009-09-25 16:18:54,226 DEBUG [org.jboss.system.ServiceController] Creating service jboss.security:service=SecurityConfig
| 2009-09-25 16:18:54,226 DEBUG [org.jboss.security.plugins.SecurityConfig] Creating jboss.security:service=SecurityConfig
| 2009-09-25 16:18:54,226 DEBUG [org.jboss.security.plugins.SecurityConfig] Created jboss.security:service=SecurityConfig
| 2009-09-25 16:18:54,226 DEBUG [org.jboss.system.ServiceController] Creating dependent components for: jboss.security:service=SecurityConfig dependents are: []
| 2009-09-25 16:18:54,226 DEBUG [org.jboss.system.ServiceController] Creating service jboss.security:service=XMLLoginConfig
| 2009-09-25 16:18:54,226 DEBUG [org.jboss.security.auth.login.XMLLoginConfig] Creating jboss.security:service=XMLLoginConfig
| 2009-09-25 16:18:54,226 DEBUG [org.jboss.security.auth.login.XMLLoginConfig] Created jboss.security:service=XMLLoginConfig
| 2009-09-25 16:18:54,227 DEBUG [org.jboss.system.ServiceController] Creating dependent components for: jboss.security:service=XMLLoginConfig dependents are: []
| 2009-09-25 16:18:54,227 DEBUG [org.jboss.system.ServiceController] Creating service jboss.security:service=JaasSecurityManager
| 2009-09-25 16:18:54,227 DEBUG [org.jboss.security.plugins.JaasSecurityManagerService] Creating jboss.security:service=JaasSecurityManager
|
I've set the option everywhere in jboss-log4j.xml to INFO but it doesn't help. Can someone help?
Here is my "jboss-log4j.xml":
| <?xml version="1.0" encoding="UTF-8"?>
| <!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">
|
| <!-- ===================================================================== -->
| <!-- -->
| <!-- Log4j Configuration -->
| <!-- -->
| <!-- ===================================================================== -->
|
| <!-- $Id: jboss-log4j.xml 75507 2008-07-08 20:15:07Z stan.silvert(a)jboss.com $ -->
|
| <!--
| | For more configuration infromation and examples see the Jakarta Log4j
| | owebsite: http://jakarta.apache.org/log4j
| -->
|
| <log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/" debug="false">
|
| <!-- ================================= -->
| <!-- Preserve messages in a local file -->
| <!-- ================================= -->
|
| <!-- A time/date based rolling appender -->
| <appender name="FILE" class="org.jboss.logging.appender.DailyRollingFileAppender">
| <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
| <param name="File" value="${jboss.server.log.dir}/server.log"/>
| <param name="Append" value="false"/>
|
| <!-- Rollover at midnight each day -->
| <param name="DatePattern" value="'.'yyyy-MM-dd"/>
|
| <!-- Rollover at the top of each hour
| <param name="DatePattern" value="'.'yyyy-MM-dd-HH"/>
| -->
|
| <layout class="org.apache.log4j.PatternLayout">
| <!-- The default pattern: Date Priority [Category] Message\n -->
| <param name="ConversionPattern" value="%d %-5p [%c] %m%n"/>
|
| <!-- The full pattern: Date MS Priority [Category] (Thread:NDC) Message\n
| <param name="ConversionPattern" value="%d %-5r %-5p [%c] (%t:%x) %m%n"/>
| -->
| </layout>
| </appender>
|
| <!-- A size based file rolling appender
| <appender name="FILE" class="org.jboss.logging.appender.RollingFileAppender">
| <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
| <param name="File" value="${jboss.server.log.dir}/server.log"/>
| <param name="Append" value="false"/>
| <param name="MaxFileSize" value="500KB"/>
| <param name="MaxBackupIndex" value="1"/>
|
| <layout class="org.apache.log4j.PatternLayout">
| <param name="ConversionPattern" value="%d %-5p [%c] %m%n"/>
| </layout>
| </appender>
| -->
|
| <!-- ============================== -->
| <!-- Append messages to the console -->
| <!-- ============================== -->
|
| <appender name="CONSOLE" class="org.apache.log4j.ConsoleAppender">
| <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
| <param name="Target" value="System.out"/>
| <param name="Threshold" value="INFO"/>
|
| <layout class="org.apache.log4j.PatternLayout">
| <!-- The default pattern: Date Priority [Category] Message\n -->
| <param name="ConversionPattern" value="%d{ABSOLUTE} %-5p [%c{1}] %m%n"/>
| </layout>
| </appender>
|
| <!-- ====================== -->
| <!-- More Appender examples -->
| <!-- ====================== -->
|
| <!-- Buffer events and log them asynchronously
| <appender name="ASYNC" class="org.apache.log4j.AsyncAppender">
| <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
| <appender-ref ref="FILE"/>
| <appender-ref ref="CONSOLE"/>
| <appender-ref ref="SMTP"/>
| </appender>
| -->
|
| <!-- EMail events to an administrator
| <appender name="SMTP" class="org.apache.log4j.net.SMTPAppender">
| <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
| <param name="Threshold" value="ERROR"/>
| <param name="To" value="admin(a)myhost.domain.com"/>
| <param name="From" value="nobody(a)myhost.domain.com"/>
| <param name="Subject" value="JBoss Sever Errors"/>
| <param name="SMTPHost" value="localhost"/>
| <param name="BufferSize" value="10"/>
| <layout class="org.apache.log4j.PatternLayout">
| <param name="ConversionPattern" value="[%d{ABSOLUTE},%c{1}] %m%n"/>
| </layout>
| </appender>
| -->
|
| <!-- Syslog events
| <appender name="SYSLOG" class="org.apache.log4j.net.SyslogAppender">
| <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
| <param name="Facility" value="LOCAL7"/>
| <param name="FacilityPrinting" value="true"/>
| <param name="SyslogHost" value="localhost"/>
| <layout class="org.apache.log4j.PatternLayout">
| <param name="ConversionPattern" value="[%d{ABSOLUTE},%c{1}] %m%n"/>
| </layout>
| </appender>
| -->
|
| <!-- Log events to JMS (requires a topic to be created)
| <appender name="JMS" class="org.apache.log4j.net.JMSAppender">
| <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
| <param name="Threshold" value="ERROR"/>
| <param name="TopicConnectionFactoryBindingName" value="java:/ConnectionFactory"/>
| <param name="TopicBindingName" value="topic/MyErrorsTopic"/>
| </appender>
| -->
|
| <!-- Log events through SNMP
| <appender name="TRAP_LOG" class="org.apache.log4j.ext.SNMPTrapAppender">
| <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
| <param name="ImplementationClassName" value="org.apache.log4j.ext.JoeSNMPTrapSender"/>
| <param name="ManagementHost" value="127.0.0.1"/>
| <param name="ManagementHostTrapListenPort" value="162"/>
| <param name="EnterpriseOID" value="1.3.6.1.4.1.24.0"/>
| <param name="LocalIPAddress" value="127.0.0.1"/>
| <param name="LocalTrapSendPort" value="161"/>
| <param name="GenericTrapType" value="6"/>
| <param name="SpecificTrapType" value="12345678"/>
| <param name="CommunityString" value="public"/>
| <param name="ForwardStackTraceWithTrap" value="true"/>
| <param name="Threshold" value="INFO"/>
| <param name="ApplicationTrapOID" value="1.3.6.1.4.1.24.12.10.22.64"/>
| <layout class="org.apache.log4j.PatternLayout">
| <param name="ConversionPattern" value="%d,%p,[%t],[%c],%m%n"/>
| </layout>
| </appender>
| -->
|
| <!-- Emit events as JMX notifications
| <appender name="JMX" class="org.jboss.monitor.services.JMXNotificationAppender">
| <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
|
| <param name="Threshold" value="WARN"/>
| <param name="ObjectName" value="jboss.system:service=Logging,type=JMXNotificationAppender"/>
|
| <layout class="org.apache.log4j.PatternLayout">
| <param name="ConversionPattern" value="%d %-5p [%c] %m"/>
| </layout>
| </appender>
| -->
|
| <!-- ================ -->
| <!-- Limit categories -->
| <!-- ================ -->
|
| <!-- Limit the org.apache category to INFO as its DEBUG is verbose -->
| <category name="org.apache">
| <priority value="INFO"/>
| </category>
|
| <!-- Limit the jacorb category to WARN as its INFO is verbose -->
| <category name="jacorb">
| <priority value="WARN"/>
| </category>
|
| <!-- Limit the org.jgroups category to WARN as its INFO is verbose -->
| <category name="org.jgroups">
| <priority value="WARN"/>
| </category>
|
| <!-- Limit the org.quartz category to INFO as its DEBUG is verbose -->
| <category name="org.quartz">
| <priority value="INFO"/>
| </category>
|
| <!-- Limit JSF logging to DEBUG. FINER and FINEST will not be logged -->
| <category name="javax.enterprise.resource.webcontainer.jsf">
| <priority value="INFO" />
| </category>
|
| <!-- Limit JBoss categories
| <category name="org.jboss">
| <priority value="INFO"/>
| </category>
| -->
|
| <!-- Limit the JSR77 categories -->
| <category name="org.jboss.management">
| <priority value="INFO"/>
| </category>
|
| <!-- Show the evolution of the DataSource pool in the logs [inUse/Available/Max]
| <category name="org.jboss.resource.connectionmanager.JBossManagedConnectionPool">
| <priority value="TRACE"/>
| </category>
| -->
|
| <!-- Limit the org.jboss.serial (jboss-serialization) to INFO as its DEBUG is verbose -->
| <category name="org.jboss.serial">
| <priority value="INFO"/>
| </category>
|
| <!-- Decrease the priority threshold for the org.jboss.varia category
| <category name="org.jboss.varia">
| <priority value="INFO"/>
| </category>
| -->
|
| <!-- Enable JBossWS message tracing
| <category name="org.jboss.ws.core.MessageTrace">
| <priority value="TRACE"/>
| </category>
| -->
|
| <!--
| | An example of enabling the custom TRACE level priority that is used
| | by the JBoss internals to diagnose low level details. This example
| | turns on TRACE level msgs for the org.jboss.ejb.plugins package and its
| | subpackages. This will produce A LOT of logging output.
| |
| | Note: since jboss AS 4.2.x, the trace level is supported natively by
| | log4j, so although the custom org.jboss.logging.XLevel priority will
| | still work, there is no need to use it. The two examples that follow
| | will both enable trace logging.
| <category name="org.jboss.system">
| <priority value="TRACE" class="org.jboss.logging.XLevel"/>
| </category>
| <category name="org.jboss.ejb.plugins">
| <priority value="TRACE"/>
| </category>
| -->
|
| <!--
| | Logs these events to SNMP:
| - server starts/stops
| - cluster evolution (node death/startup)
| - When an EJB archive is deployed (and associated verified messages)
| - When an EAR archive is deployed
|
| <category name="org.jboss.system.server.Server">
| <priority value="INFO" />
| <appender-ref ref="TRAP_LOG"/>
| </category>
|
| <category name="org.jboss.ha.framework.interfaces.HAPartition.lifecycle">
| <priority value="INFO" />
| <appender-ref ref="TRAP_LOG"/>
| </category>
|
| <category name="org.jboss.deployment.MainDeployer">
| <priority value="ERROR" />
| <appender-ref ref="TRAP_LOG"/>
| </category>
|
| <category name="org.jboss.ejb.EJBDeployer">
| <priority value="INFO" />
| <appender-ref ref="TRAP_LOG"/>
| </category>
|
| <category name="org.jboss.deployment.EARDeployer">
| <priority value="INFO" />
| <appender-ref ref="TRAP_LOG"/>
| </category>
| -->
|
| <!-- Clustering logging -->
| <!-- Uncomment the following to redirect the org.jgroups and
| org.jboss.ha categories to a cluster.log file.
|
| <appender name="CLUSTER" class="org.jboss.logging.appender.RollingFileAppender">
| <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
| <param name="File" value="${jboss.server.log.dir}/cluster.log"/>
| <param name="Append" value="false"/>
| <param name="MaxFileSize" value="500KB"/>
| <param name="MaxBackupIndex" value="1"/>
|
| <layout class="org.apache.log4j.PatternLayout">
| <param name="ConversionPattern" value="%d %-5p [%c] %m%n"/>
| </layout>
| </appender>
| <category name="org.jgroups">
| <priority value="INFO" />
| <appender-ref ref="CLUSTER"/>
| </category>
| <category name="org.jboss.ha">
| <priority value="INFO" />
| <appender-ref ref="CLUSTER"/>
| </category>
| -->
|
| <!-- ======================= -->
| <!-- Setup the Root category -->
| <!-- ======================= -->
|
| <root>
| <appender-ref ref="CONSOLE"/>
| <appender-ref ref="FILE"/>
| </root>
|
| </log4j:configuration>
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4257327#4257327
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4257327
16 years, 7 months