[jboss-jira] [JBoss JIRA] (JBAS-9464) JBoss 4.3, server.log is not logging any log messages after restart
jaikiran pai (JIRA)
jira-events at lists.jboss.org
Wed Jan 18 00:13:18 EST 2012
[ https://issues.jboss.org/browse/JBAS-9464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660042#comment-12660042 ]
jaikiran pai commented on JBAS-9464:
------------------------------------
Please use the forums https://community.jboss.org/community/jbossas/config?view=discussions for questions like these.
> JBoss 4.3, server.log is not logging any log messages after restart
> -------------------------------------------------------------------
>
> Key: JBAS-9464
> URL: https://issues.jboss.org/browse/JBAS-9464
> Project: Application Server 3 4 5 and 6
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Logging
> Environment: Linux
> Reporter: shiva ram
>
> Hi,
> We r running jboss 4.3 on linux, its a development box, issue is the application logs are not getting updated from many days and server.log is not getting updated after restart. while restarting we r getting following error in server.log
> and after server start, nothing is updating in server.log after the last line of this message. (nothing is being logged anywhere, but all things r running fine, applications are accessible)
> SERVER.LOG:
> --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
> ObjectName: jboss:service=WebService
> State: FAILED
> Reason: java.lang.Exception: Port 8083 already in use.
> I Depend On:
> jboss.system:service=ThreadPool
> Depends On Me:
> jboss.ejb:service=EJBDeployer
> ObjectName: jboss.cache:service=EJB3SFSBClusteredCache
> State: FAILED
> Reason: org.jgroups.ChannelException: failed to start protocol stack
> ObjectName: jboss.messaging:service=Connector,transport=bisocket
> State: FAILED
> Reason: java.net.BindException: Cannot assign requested address
> Depends On Me:
> jboss.messaging.connectionfactory:service=ConnectionFactory
> jboss.messaging.connectionfactory:service=ClusteredConnectionFactory
> jboss.messaging.connectionfactory:service=ClusterPullConnectionFactory
> jboss.messaging:service=ServerPeer
> ObjectName: jboss:service=invoker,type=jrmp
> State: FAILED
> Reason: java.rmi.server.ExportException: Port already in use: 4444; nested exception is:
> java.net.BindException: Cannot assign requested address
> I Depend On:
> jboss:service=TransactionManager
> Depends On Me:
> jboss.jmx:type=adaptor,name=Invoker,protocol=jrmp,service=proxyFactory
> jboss.jca:service=DataSourceBinding,name=jdbc/globalVista
> ObjectName: jboss.remoting:type=Connector,name=DefaultEjb3Connector,handler=ejb3
> State: FAILED
> Reason: java.net.BindException: Cannot assign requested address
> I Depend On:
> jboss.aop:service=AspectDeployer
> ObjectName: jboss:service=Naming
> State: FAILED
> Reason: java.rmi.server.ExportException: Port already in use: 1098; nested exception is:
> java.net.BindException: Cannot assign requested address
> I Depend On:
> jboss.system:service=ThreadPool
> jboss:service=NamingBeanImpl
> Depends On Me:
> jboss.cache:service=TomcatClusteringCache
> jboss:service=MYAPPLICATION10
> jboss:service=HASessionState
> jboss:service=invoker,type=jrmpha
> jboss:service=invoker,type=pooledha
> jboss.cache:service=EJB3EntityTreeCache
> jboss.jmx:type=adaptor,name=Invoker,protocol=jrmp,service=proxyFactory
> jboss.jmx:alias=jmx/rmi/RMIAdaptor
> jboss:service=Mail
> ObjectName: jboss.remoting:service=Connector,transport=socket
> State: FAILED
> Reason: java.net.BindException: Cannot assign requested address
> I Depend On:
> jboss.remoting:service=NetworkRegistry
> Depends On Me:
> jboss:service=invoker,type=unified
> jboss:service=invoker,type=unifiedha
> ObjectName: jboss:service=invoker,type=pooled
> State: FAILED
> Reason: java.lang.Exception: Port 4445 is already in use
> I Depend On:
> jboss:service=TransactionManager
> at org.jboss.deployment.MainDeployer.checkIncompleteDeployments(MainDeployer.java:1385)
> at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:785)
> at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> at $Proxy5.deploy(Unknown Source)
> at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
> at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
> at org.jboss.Main.boot(Main.java:200)
> at org.jboss.Main$1.run(Main.java:513)
> at java.lang.Thread.run(Thread.java:619)
> INFO [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.3.0.GA_CP07 (build: SVNTag=JBPAPP_4_3_0_GA_CP07 date=200911251949)] Started in 17s:402ms
> -----------------------------------
> There are many transactions going on the applications yet nothing is being logged. Can anyone know of why this is happening
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list