[Beginners Corner] - Re: Help with JBOSS Log Configuration
by johnloo
"PeterJ" wrote : The boot.log is configured via the log4j.properties file located within bin.run.jar. Once the app sever has been bootstrapped, that configuration is dropped and the conf/log4j.xml configuration used for logging instead.
|
| I pasted your RollingFileAppender configuration into my log4j.xml file and it worked just fine. But I used 4.0.2, not 4.0.1.SP1.
|
| The last two lines in my boot.log file are:
|
| 12:52:57,788 DEBUG [Log4jService] Creating jboss.system:type=Log4jService,service=Logging
| 12:52:57,788 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml
|
| Do you have anything like this in your boot.log file? Or is there an error?
|
Those lines appear about 1.4 seconds after the first record in the boot.log file. But the system continues to append additional lines into boot.log. Here are the next few lines after the ones you noted:
10:12:53,983 DEBUG [Log4jService] Installed System.out adapter
10:12:53,983 DEBUG [Log4jService] Installed System.err adapter
10:12:53,999 DEBUG [Log4jService] Added ThrowableListener: org.jboss.logging.Log4jService$ThrowableListenerLoggingAdapter@e35bb7
10:12:53,999 DEBUG [Log4jService] Created jboss.system:type=Log4jService,service=Logging
10:12:53,999 DEBUG [LocalJBossServerDomain] handleNotification: javax.management.Notification[source=jboss.system:service=ServiceController][type= org.jboss.system.ServiceMBean.create][message=]
10:12:53,999 DEBUG [DefaultManagedObjectFactoryMap] Failed to find factory for event: javax.management.Notification[source=jboss.system:service=ServiceController][type= org.jboss.system.ServiceMBean.create][message=]
10:12:53,999 DEBUG [ServiceController] Creating dependent components for: jboss.system:type=Log4jService,service=Logging dependents are: []
10:12:53,999 DEBUG [ServiceController] Creating service jboss.rmi:type=RMIClassLoader
10:12:53,999 DEBUG [LocalJBossServerDomain] handleNotification: javax.management.Notification[source=jboss.system:service=ServiceController][type= org.jboss.system.ServiceMBean.create][message=]
10:12:53,999 DEBUG [DefaultManagedObjectFactoryMap] Failed to find factory for event: javax.management.Notification[source=jboss.system:service=ServiceController][type= org.jboss.system.ServiceMBean.create][message=]
10:12:53,999 DEBUG [ServiceController] Creating dependent components for: jboss.rmi:type=RMIClassLoader dependents are: []
10:12:53,999 DEBUG [ServiceController] Creating service jboss:service=WebService
10:12:53,999 DEBUG [WebService] Creating jboss:service=WebService
10:12:53,999 INFO [WebService] Using RMI server codebase: http://cgusrd11:8083/
10:12:53,999 DEBUG [WebService] Created jboss:service=WebService
It continues on and on...
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4212447#4212447
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4212447
17 years, 1 month
[JBoss Messaging] - JBoss messaging client timeout
by pratimkm
Hi,
I am using JBoss 4.2.2GA and Messaging 1.4.2 with remoting version 2.2.2.SP10. We have setup JBM cluster with oracle as database. The jboss server is accessed by a remote client located beyond a firewall with a one hour timeout for any idle client. We have a JMS listener which listnes for messages on JBM through the firewall with remoting bisocket configured for 4458 secondary port.To get over the idle timeout issue we are refreshing the message listener connection every half an hour.But even after doing that, after 12 hours of idle time we are seeing that the messages coming on JBM queues are getting stuck for a few messages. Do I need to change any paramater in remoting bisocket to get over this issue ? Any help would be appreciated.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4212435#4212435
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4212435
17 years, 1 month