[EJB/JBoss] - How to trace remote calls client-side
by alessandro_rizzi
I have a client-server application (developed with JWS, but this is not meaningfull) and I would like to trace, for debug pourpose each remote method invocation (from client to server, not from server to server) ... just to know how many remote calls are made in each client event.
The application is very big and developed by many programmers, so I cannot do something at code level, but I'm looking for something at configurarion level.
I've tried to add something like:
org.jboss.ejb.Container.level = FINEST
org.jboss.ejb.level = FINEST
org.jboss.level = FINEST
org.jboss.proxy.ClientContainer.level = FINEST
org.jnp.level = FINEST
in logging.properties of my JRE, but I see nothing on log files.
I'm using JBoss 3.2.5 (but I can try also JBoss 4.0.4).
Any suggestion will be greatly appreciated
Regards
Alessandro Rizzi
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4073935#4073935
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4073935
18Â years, 11Â months
[JBossCache] - Instrumentation - preparing an object for POJO Cache 2.0?
by BruceSpringfield
Can someone clarify instrumentation of objects for POJO Cache 2.0
The documentation continually emphasizes the need for instrumentation of Objects before using these objects with POJO Cache.
But I ran some tests with POJO Cache and did not instrument the objects at all in the tests and POJO Cache appeared to work. The documentation also says, "But depends on the JDK and instrumentation mode that you are using, you may not need to pre-process your POJO at all." Can I have it clarified when I need to instrument and when not?
For my tests I used the Student and Course objects from the /examples/PojoCache/ directory. I also used java.util.Date and StringBuffer as objects. All these objects seemed to work fine without instrumentation for a local PojoCache. With replication, I'm pretty sure I will have to instrumentent the objects with annotation. But how would I instrument a Date object or a StringBuffer?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4073926#4073926
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4073926
18Â years, 11Â months
[Installation, Configuration & DEPLOYMENT] - JBoss Installation with only JMX Console and Tomcat.
by vdimitr
Hello everybody. I'm trying to get an up 'n' running JBoss installation with
only the JMX Console and Tomcat Web Server.
After reading the JBoss Wiki about Slimming and Service Dependencies and tried a few experiments myself, I have come to the following jboss-service.xml
| <?xml version="1.0" encoding="UTF-8"?>
|
| <server>
|
| <!-- Load all jars from the JBOSS_DIST/server/<config>/lib directory. This
| can be restricted to specific jars by specifying them in the archives
| attribute.
| -->
| <classpath codebase="${jboss.server.lib.url:lib}" archives="*"/>
|
| <!-- ==================================================================== -->
| <!-- Log4j Initialization -->
| <!-- ==================================================================== -->
| <mbean code="org.jboss.logging.Log4jService"
| name="jboss.system:type=Log4jService,service=Logging">
| <attribute name="ConfigurationURL">resource:log4j.xml</attribute>
| </mbean>
|
| <!-- ==================================================================== -->
| <!-- Thread Pool -->
| <!-- ==================================================================== -->
|
| <!-- A Thread pool service -->
| <mbean code="org.jboss.util.threadpool.BasicThreadPool"
| name="jboss.system:service=ThreadPool">
| <attribute name="Name">JBoss System Threads</attribute>
| <attribute name="ThreadGroupName">System Threads</attribute>
| <!-- How long a thread will live without any tasks in MS -->
| <attribute name="KeepAliveTime">60000</attribute>
| <!-- The max number of threads in the pool -->
| <attribute name="MaximumPoolSize">10</attribute>
| <!-- The max number of tasks before the queue is full -->
| <attribute name="MaximumQueueSize">1000</attribute>
| <!-- The behavior of the pool when a task is added and the queue is full.
| abort - a RuntimeException is thrown
| run - the calling thread executes the task
| wait - the calling thread blocks until the queue has room
| discard - the task is silently discarded without being run
| discardOldest - check to see if a task is about to complete and enque
| the new task if possible, else run the task in the calling thread
| -->
| <attribute name="BlockingMode">run</attribute>
| </mbean>
|
| <!-- ==================================================================== -->
| <!-- JNDI -->
| <!-- ==================================================================== -->
|
| <!-- A simple mbean wrapper around the jndi Naming object. This
| only handles an in memory instance. The NamingService uses this
| as the JNDI store and exposes it remotely.
| -->
| <mbean code="org.jnp.server.NamingBeanImpl"
| name="jboss:service=NamingBeanImpl"
| xmbean-dd="resource:xmdesc/NamingBean-xmbean.xml">
| </mbean>
|
| <mbean code="org.jboss.naming.NamingService"
| name="jboss:service=Naming"
| xmbean-dd="resource:xmdesc/NamingService-xmbean.xml">
| <!-- The call by value mode. true if all lookups are unmarshalled using
| the caller's TCL, false if in VM lookups return the value by reference.
| -->
| <attribute name="CallByValue">false</attribute>
| <!-- The listening port for the bootstrap JNP service. Set this to -1
| to run the NamingService without the JNP invoker listening port.
| -->
| <attribute name="Port">-1</attribute>
| <!-- The bootstrap JNP server bind address. This also sets the default
| RMI service bind address. Empty == all addresses
| -->
| <attribute name="BindAddress">${jboss.bind.address}</attribute>
| <!-- The port of the RMI naming service, 0 == anonymous -->
| <attribute name="RmiPort">0</attribute>
| <!-- The RMI service bind address. Empty == all addresses
| -->
| <attribute name="RmiBindAddress">${jboss.bind.address}</attribute>
| <!-- The thread pool service used to control the bootstrap lookups -->
| <!--<depends optional-attribute-name="LookupPool"
| proxy-type="attribute">jboss.system:service=ThreadPool</depends>-->
| <!-- An example of using the unifed invoker as the transport.
| <depends optional-attribute-name="InvokerProxyFactory"
| proxy-type="attribute">jboss:service=proxyFactory,type=unified,target=Naming</depends>
| -->
| <depends optional-attribute-name="Naming"
| proxy-type="attribute">jboss:service=NamingBeanImpl</depends>
| </mbean>
|
| <!-- ==================================================================== -->
| <!-- Transactions -->
| <!-- ==================================================================== -->
|
| <!-- The configurable Xid factory. For use with Oracle, set pad to true -->
| <mbean code="org.jboss.tm.XidFactory"
| name="jboss:service=XidFactory">
| <!--attribute name="Pad">true</attribute-->
| </mbean>
|
| <!-- JBoss Transactions JTA -->
| <mbean code="com.arjuna.ats.jbossatx.jta.TransactionManagerService"
| name="jboss:service=TransactionManager">
| <attribute name="TransactionTimeout">300</attribute>
| <attribute name="ObjectStoreDir">${jboss.server.data.dir}/tx-object-store</attribute>
| </mbean>
|
| <!--
| | UserTransaction support.
| -->
| <mbean code="org.jboss.tm.usertx.server.ClientUserTransactionService"
| name="jboss:service=ClientUserTransaction"
| xmbean-dd="resource:xmdesc/ClientUserTransaction-xmbean.xml">
| <depends>
| <mbean code="org.jboss.invocation.jrmp.server.JRMPProxyFactory"
| name="jboss:service=proxyFactory,target=ClientUserTransactionFactory">
| <attribute name="InvokerName">jboss:service=invoker,type=jrmp</attribute>
| <attribute name="TargetName">jboss:service=ClientUserTransaction</attribute>
| <attribute name="JndiName">UserTransactionSessionFactory</attribute>
| <attribute name="ExportedInterface">org.jboss.tm.usertx.interfaces.UserTransactionSessionFactory</attribute>
| <attribute name="ClientInterceptors">
| <interceptors>
| <interceptor>org.jboss.proxy.ClientMethodInterceptor</interceptor>
| <interceptor>org.jboss.invocation.InvokerInterceptor</interceptor>
| </interceptors>
| </attribute>
| <depends>jboss:service=invoker,type=jrmp</depends>
| </mbean>
| </depends>
| <depends optional-attribute-name="TxProxyName">
| <mbean code="org.jboss.invocation.jrmp.server.JRMPProxyFactory"
| name="jboss:service=proxyFactory,target=ClientUserTransaction">
| <attribute name="InvokerName">jboss:service=invoker,type=jrmp</attribute>
| <attribute name="TargetName">jboss:service=ClientUserTransaction</attribute>
| <attribute name="JndiName"></attribute>
| <attribute name="ExportedInterface">org.jboss.tm.usertx.interfaces.UserTransactionSession</attribute>
| <attribute name="ClientInterceptors">
| <interceptors>
| <interceptor>org.jboss.proxy.ClientMethodInterceptor</interceptor>
| <interceptor>org.jboss.invocation.InvokerInterceptor</interceptor>
| </interceptors>
| </attribute>
| <depends>jboss:service=invoker,type=jrmp</depends>
| </mbean>
| </depends>
| </mbean>
|
| <!-- ==================================================================== -->
| <!-- Invokers to the JMX node -->
| <!-- ==================================================================== -->
|
| <!-- RMI/JRMP invoker -->
| <mbean code="org.jboss.invocation.jrmp.server.JRMPInvoker"
| name="jboss:service=invoker,type=jrmp">
| <attribute name="RMIObjectPort">4444</attribute>
| <attribute name="ServerAddress">${jboss.bind.address}</attribute>
| <!--
| <attribute name="RMIClientSocketFactory">custom</attribute>
| <attribute name="RMIServerSocketFactory">custom</attribute>
| <attribute name="RMIServerSocketAddr">custom</attribute>
| <attribute name="SecurityDomain">ssl-domain-name</attribute>
| -->
| <depends>jboss:service=TransactionManager</depends>
| </mbean>
|
| <!-- JACC security manager and realm mapping -->
| <mbean code="org.jboss.security.jacc.SecurityService"
| name="jboss.security:service=JACCSecurityService" xmbean-dd="">
| <xmbean>
| <description>The JACC security Policy service</description>
| <operation>
| <description>The start lifecycle operation</description>
| <name>start</name>
| </operation>
| <operation>
| <description>The stop lifecycle operation</description>
| <name>stop</name>
| </operation>
| </xmbean>
| </mbean>
|
| <!-- ==================================================================== -->
| <!-- Deployment Scanning -->
| <!-- ==================================================================== -->
|
| <!-- An mbean for hot deployment/undeployment of archives.
| -->
| <mbean code="org.jboss.deployment.scanner.URLDeploymentScanner"
| name="jboss.deployment:type=DeploymentScanner,flavor=URL">
|
| <depends optional-attribute-name="Deployer">jboss.system:service=MainDeployer</depends>
|
| <!-- The URLComparator can be used to specify a deployment ordering
| for deployments found in a scanned directory. The class specified
| must be an implementation of java.util.Comparator, it must be able
| to compare two URL objects, and it must have a no-arg constructor.
| Two deployment comparators are shipped with JBoss:
| - org.jboss.deployment.DeploymentSorter
| Sorts by file extension, as follows:
| "sar", "service.xml", "rar", "jar", "war", "wsr", "ear", "zip",
| "*"
| - org.jboss.deployment.scanner.PrefixDeploymentSorter
| If the name portion of the url begins with 1 or more digits, those
| digits are converted to an int (ignoring leading zeroes), and
| files are deployed in that order. Files that do not start with
| any digits will be deployed last, and they will be sorted by
| extension as above with DeploymentSorter.
| -->
| <attribute name="URLComparator">org.jboss.deployment.DeploymentSorter</attribute>
|
| <!-- The Filter specifies a java.io.FileFilter for scanned
| directories. Any file not accepted by this filter will not be
| deployed. The org.jboss.deployment.scanner.DeploymentFilter
| rejects the following patterns:
| "#*", "%*", ",*", ".*", "_$*", "*#", "*$", "*%", "*.BAK",
| "*.old", "*.orig", "*.rej", "*.bak", "*,v", "*~", ".make.state",
| ".nse_depinfo", "CVS", "CVS.admin", "RCS", "RCSLOG", "SCCS",
| "TAGS", "core", "tags"
| -->
| <attribute name="Filter">org.jboss.deployment.scanner.DeploymentFilter</attribute>
|
| <attribute name="ScanPeriod">5000</attribute>
|
| <!-- URLs are comma seperated and unprefixed arguments are considered
| file URLs and resolve relative to server home(JBOSS_DIST/server/default)
| unless the given path is absolute. Any referenced directories cannot
| be unpackaged archives, use the parent directory of the unpacked
| archive.
| -->
| <attribute name="URLs">
| deploy/
| </attribute>
|
| </mbean>
|
| </server>
|
|
Since I'm a bit of a noob, and I don't want to take much time and series of
endless configuration snipsets, for the time being I wish to know the jar files
that are required for running the jmx console and tomcat.
Thanx in advance
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4073922#4073922
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4073922
18Â years, 11Â months