[ 
https://issues.apache.org/jira/browse/GERONIMO-6083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067583#comment-13067583
 ] 

Shawn Jiang commented on GERONIMO-6083:
---------------------------------------

Repository      Revision        Date    User    Message
ASF     #1148231        Tue Jul 19 08:37:05 UTC 2011    genspring       
GERONIMO-6083 Annoying warn when shutdown geronimo server. The users don't care 
the portlet register/unregister info in log.
Files Changed
MODIFY 
/geronimo/server/trunk/framework/configs/karaf-framework/src/main/distribution/instance/var/log/server-log4j.properties


This only removed the portlet register/unregister message in server log.   I 
tried to add

log4j.logger.org.apache.aries.jpa.blueprint.aries.impl.NSHandler=ERROR
log4j.logger.org.apache.aries.jpa.container.context.transaction.impl.JTAPersistenceContextRegistry=ERROR

to remove the two warning in console when executing the shutdown command.   But 
it does not work at all. 

> Annoying warn when shutdown geronimo server.
> --------------------------------------------
>
>                 Key: GERONIMO-6083
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-6083
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: general
>    Affects Versions: 3.0
>            Reporter: Shawn Jiang
>            Assignee: Shawn Jiang
>
> geronimo> shutdown
> geronimo> 2011-07-18 16:05:46,027 WARN  [aries] Managed persistence context 
> support is no longer available for use with the Aries Blueprint container
> 2011-07-18 16:05:46,028 WARN  [context] The 
> TransactionSynchronizationRegistry used to manage persistence contexts is no 
> longer available. Managed per
> sistence contexts will no longer be able to integrate with JTA transactions, 
> and will behave as if no there is no transaction context at all times unt
> il a new TransactionSynchronizationRegistry is available. Applications using 
> managed persistence contexts may not work correctly until a new JTA Trans
> action services implementation is available.
> and 
> 2011-07-16 21:04:30,340 INFO  [PortletContextManager] Portlet Context 
> '/system-database' removed.
> 2011-07-16 21:04:30,340 INFO  [PortletContextManager] Portlet Context 
> '/system-database' removed.
> 2011-07-16 21:04:30,340 INFO  [PortletContextManager] Portlet Context 
> '/system-database' removed.
> 2011-07-16 21:04:30,340 INFO  [PortletContextManager] Portlet Context 
> '/system-database' removed.
> 2011-07-16 21:04:30,341 INFO  [PortletContextManager] Portlet Context 
> '/system-database' removed.
> 2011-07-16 21:04:30,341 INFO  [PortletContextManager] Portlet Context 
> '/system-database' removed.
> 2011-07-16 21:04:30,353 INFO  [PortletContextManager] Portlet Context 
> '/debug-views' removed.
> 2011-07-16 21:04:30,353 INFO  [PortletContextManager] Portlet Context 
> '/debug-views' removed.
> 2011-07-16 21:04:30,353 INFO  [PortletContextManager] Portlet Context 
> '/debug-views' removed.
> 2011-07-16 21:04:30,353 INFO  [PortletContextManager] Portlet Context 
> '/debug-views' removed.
> 2011-07-16 21:04:30,360 INFO  [PortletContextManager] Portlet Context 
> '/activemq' removed.
> 2011-07-16 21:04:30,360 INFO  [PortletContextManager] Portlet Context 
> '/activemq' removed.
> 2011-07-16 21:04:30,360 INFO  [PortletContextManager] Portlet Context 
> '/activemq' removed.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to