I always go to the server location (for example, C:\jboss_lomboz_32\server\default\log) and look into the log file. I worked with Oracle App Server, used to have an Enterprise Manager Console, where I can see the log file contents and refresh them by a click...
Could anyone help me locating this.
Purpose: We are developing a immature J2EE product. QA team gets lots of issues. Sometimes, as you know, Log file content is so helpful to track the issue. QA does not want to send the outdated log file (since logfile has a size limit).
Thank you.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051496#4051496
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051496
"Lightguard" wrote : Probably shouldn't matter, but try cleaning out your tmp and work directories in Jboss then redeploying. Also check the JBOSS_HOME/server/which_server_name_you_use/jbossweb-tomcat55.sar/jsf-libs dir and see if there's a copy of facelets in there (if you haven't already).
Actually, tmp directory is locked in runtime and server cleans it up while shutdowning. There is only default jboss configuration in my server. There no other TagHandle.class files in my jboss, except one in web-inf/lib adn another in deploy/tmp
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051487#4051487
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051487
You should not duplicate your classes in separate jars. If ZenAS.jar contains EJB's then renaming it to ZenAS.jar.aop will cause the ejb-jar.xml to not get picked up. Likewise a META-INF/jboss-aop.xml file only gets picked up in archives ending with .aop :-)
If you download the distribution there is an "injboss" example which contains some packaging suggestions.
One of these is to deploy the jboss-aop.xml file on its own (in this case rename it to something like ZenAS-aop.xml) BEFORE you deploy the ZenAS.jar.
An alternative might be to deploy the jboss-aop.xml file in the *root* of your ZenAS.jar. It should work, but I cannot remember if it does!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051486#4051486
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051486
Hi Kabir,
Thanks once again for your help. I had not done enough excluding, and now it is starting with minimal delay.
I think I mentioned earlier that I had renamed my .jar file from ZenAS.jar to ZenAS.jar.aop. When I have the .aop extension, the loadtime weaving is happening, but the beans in the jar file are not getting deployed. Is this expected behavior? If I have two copies (one named .jar, one named .aop) the weaving happens and the jars get deployed and it all seems to be running ok. Is this right?
Thanks a million,
Jamie
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051479#4051479
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051479