LMS released
November 12, 2006 – 10:30 am by Alessio SOLDANOJavalinux.it team (me and Stefano 
infact) is proud to announce the
first release of Lms.
What is Lms? Lms is an acronym for Logging Meta Service; Lms’ goal and
use are very similar to the axis’ tcp monitor ones: it logs any tcp communication
and gives developers the opportunity to review any request-response
communications.
Lms is a JBoss deployable application (an ear) and have a jmx mbean as application core and a seam user interface to make its use easy.
In the user interface you have to bind a symbolic name to a real http
address (in most cases a ws endpoint address):
You can start/stop the logging functionality (in stopped logging mode Lms acts just like a proxy), delete the binding, clean all
communication logs. After that, you should use the binding you’ve just defined: as a matter of fact Lms creates a virtual address given by your application server host & port followed by /Lms/servlet/auth/log/ and the name you choose for your binding.
Selecting a binding you will see all the logged communications:
Finally clicking on Show you’ll see request/response logged in this communication:
It’ s very simple but very very useful for debugging, as you can figure
out if you are a developer. If you like it or you are simply curious and want to give it a try, download it here.
To install it proceed as follows:
- add policy named
no-authto your login-config.xml:<application-policy name = "no-auth">
<authentication>
<login-module code = "org.jboss.security.ClientLoginModule"
flag = "required">
</login-module>
</authentication>
</application-policy> - deploy Lms.ear
- make sure your binding target addresses can by reached from your host
Finally, if you want to take a look at the code download it here.
7 Responses to “LMS released”
Could not deploy Lms.ear due to it having no ejb-jar.xml descriptor.
By Lars [Visitor] on Feb 1, 2007
Hi Lars,
ejb.jar.xml is provided with the beans jar contained in the ear file. Could you please give us some further informations about your configuration and the error you’re getting?
Thank You
Alessio Soldano
By Alessio SOLDANO [Member] on Feb 1, 2007
I was trying to deploy this on JBoss 4.2.1 GA. The deployment was successful. When I tried to access the URL, it failed with the following stack trace in the console.
Looks like its failing to connect from my proxy. Is there a way to overcome this issue?
Caused by: org.dom4j.DocumentException: Connection timed out: connect Nested exc
eption: Connection timed out: connect
at org.dom4j.io.SAXReader.read(SAXReader.java:484)
By Arul [Visitor] on Aug 26, 2007
Can the host pointed by the address you provided be reached from the machine you deployed Lms on? This is of course a requirement.
Anyway feel free to post the full stacktrace, just to double check where you’re getting the exception.
By Alessio SOLDANO [Member] on Aug 26, 2007
When I try accessing the following URL from browser from within my company network “http://localhost:8080/Lms/”, I see the page with the message
“HTTP Status 404 – /Lms/debug.seam”
Unfortunately I cannot provide the entire exception trace in this comment as this blog does not allow me to enter the full trace.
Partial exception trace on the console:
Nested exception:
java.net.ConnectException:
By Arul [Visitor] on Aug 27, 2007
OK, the missing /Lms/debug.seam page will be fixed in the next release; however this just doesn’t allow you to receive an error page, let’s understand what’s happening instead. I need more informations, thus please write me at alessio.soldano(at)javalinux(dot)it if the exception cannot fit into a comment.
By Alessio SOLDANO [Member] on Aug 27, 2007
Thank you! I added this page to bookmark)) I think would be useful …
By bmboy on Feb 4, 2010