While deploying Btop portlet, an error rises in the logs even if it seems to be complete.
09:34:31,588 ERROR [stderr] (JMX connector) Exception in thread "JMX connector" java.lang.UnsupportedOperationException: JBAS011859: Naming context is read-only
09:34:31,588 ERROR [stderr] (JMX connector) at org.jboss.as.naming.WritableServiceBasedNamingStore.requireOwner(WritableServiceBasedNamingStore.java:126)
09:34:31,589 ERROR [stderr] (JMX connector) at org.jboss.as.naming.WritableServiceBasedNamingStore.bind(WritableServiceBasedNamingStore.java:56)
09:34:31,675 ERROR [stderr] (JMX connector) at org.jboss.as.naming.NamingContext.bind(NamingContext.java:221)
09:34:31,676 ERROR [stderr] (JMX connector) at org.jboss.as.naming.InitialContext.bind(InitialContext.java:161)
09:34:31,676 ERROR [stderr] (JMX connector) at org.jboss.as.naming.NamingContext.bind(NamingContext.java:230)
09:34:31,676 ERROR [stderr] (JMX connector) at com.liferay.portal.security.pacl.jndi.SchemeAwareContextWrapper.bind(SchemeAwareContextWrapper.java:57)
09:34:31,677 ERROR [stderr] (JMX connector) at javax.naming.InitialContext.bind(InitialContext.java:417)
09:34:31,677 ERROR [stderr] (JMX connector) at javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:639)
09:34:31,677 ERROR [stderr] (JMX connector) at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:426)
09:34:31,678 ERROR [stderr] (JMX connector) at org.apache.activemq.broker.jmx.ManagementContext$1.run(ManagementContext.java:131)09:34:34,007 ERROR [stderr] (JMX connector) Exception in thread "JMX connector" java.lang.UnsupportedOperationException: JBAS011859: Naming context is read-only09:34:34,051 ERROR [stderr] (JMX connector) at org.jboss.as.naming.WritableServiceBasedNamingStore.requireOwner(WritableServiceBasedNamingStore.java:126)09:34:34,055 ERROR [stderr] (JMX connector) at org.jboss.as.naming.WritableServiceBasedNamingStore.bind(WritableServiceBasedNamingStore.java:56)
09:34:34,057 ERROR [org.apache.activemq.broker.BrokerService] (MSC service thread 1-2) Temporary Store limit is 51200 mb, whilst the temporary data directory: /srv/jboss/liferay-portal-6.1.2-ce-ga3/jboss-7.1.1/bin/amq/data/btop/tmp_storage only has 3848 mb of usable space
09:34:34,064 ERROR [stderr] (JMX connector) at org.jboss.as.naming.NamingContext.bind(NamingContext.java:221)
09:34:34,065 ERROR [stderr] (JMX connector) at org.jboss.as.naming.InitialContext.bind(InitialContext.java:161)
09:34:34,066 ERROR [stderr] (JMX connector) at org.jboss.as.naming.NamingContext.bind(NamingContext.java:230)
09:34:34,067 ERROR [stderr] (JMX connector) at com.liferay.portal.security.pacl.jndi.SchemeAwareContextWrapper.bind(SchemeAwareContextWrapper.java:57)
09:34:34,076 ERROR [stderr] (JMX connector) at javax.naming.InitialContext.bind(InitialContext.java:417)
09:34:34,077 ERROR [stderr] (JMX connector) at javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:639)
09:34:34,078 ERROR [stderr] (JMX connector) at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:426)
09:34:34,079 ERROR [stderr] (JMX connector) at org.apache.activemq.broker.jmx.ManagementContext$1.run(ManagementContext.java:131)
Here is the full deployment trace:
09:34:18,936 INFO [stdout] (com.liferay.portal.kernel.deploy.auto.AutoDeployScanner) 09:34:18,936 INFO [com.liferay.portal.kernel.deploy.auto.AutoDeployScanner][AutoDeployDir:215] Processing btop-portlet-6.1.1.1.war
09:34:18,951 INFO [stdout] (com.liferay.portal.kernel.deploy.auto.AutoDeployScanner) 09:34:18,945 INFO [com.liferay.portal.kernel.deploy.auto.AutoDeployScanner][PortletAutoDeployListener:79] Copying portlets for /srv/jboss/liferay-portal-6.1.2-ce-ga3/deploy/btop-portlet-6.1.1.1.war
09:34:18,954 INFO [stdout] (com.liferay.portal.kernel.deploy.auto.AutoDeployScanner) 09:34:18,954 INFO [com.liferay.portal.kernel.deploy.auto.AutoDeployScanner][BaseDeployer:820] Deploying btop-portlet-6.1.1.1.war
09:34:18,955 INFO [stdout] (com.liferay.portal.kernel.deploy.auto.AutoDeployScanner) Expanding: /srv/jboss/liferay-portal-6.1.2-ce-ga3/deploy/btop-portlet-6.1.1.1.war into /tmp/20130910093418955
09:34:19,826 INFO [stdout] (com.liferay.portal.kernel.deploy.auto.AutoDeployScanner) Copying 1 file to /tmp/20130910093418955/WEB-INF
09:34:19,862 INFO [stdout] (com.liferay.portal.kernel.deploy.auto.AutoDeployScanner) Copying 1 file to /tmp/20130910093418955/WEB-INF/classes
09:34:19,863 INFO [stdout] (com.liferay.portal.kernel.deploy.auto.AutoDeployScanner) Copying 1 file to /tmp/20130910093418955/WEB-INF/classes
09:34:19,875 INFO [stdout] (com.liferay.portal.kernel.deploy.auto.AutoDeployScanner) Copying 1 file to /tmp/20130910093418955/WEB-INF
09:34:19,876 INFO [stdout] (com.liferay.portal.kernel.deploy.auto.AutoDeployScanner) Copying 1 file to /tmp/20130910093418955/WEB-INF/jsp
09:34:20,882 INFO [stdout] (com.liferay.portal.kernel.deploy.auto.AutoDeployScanner) 09:34:20,882 INFO [com.liferay.portal.kernel.deploy.auto.AutoDeployScanner][BaseDeployer:2233] Modifying Servlet 3.0 /tmp/20130910093418955/WEB-INF/web.xml
09:34:21,260 INFO [stdout] (com.liferay.portal.kernel.deploy.auto.AutoDeployScanner) Copying 750 files to /srv/jboss/liferay-portal-6.1.2-ce-ga3/jboss-7.1.1/standalone/deployments/btop-portlet.war
09:34:21,963 INFO [stdout] (com.liferay.portal.kernel.deploy.auto.AutoDeployScanner) Copying 1 file to /srv/jboss/liferay-portal-6.1.2-ce-ga3/jboss-7.1.1/standalone/deployments/btop-portlet.war
09:34:21,964 INFO [stdout] (com.liferay.portal.kernel.deploy.auto.AutoDeployScanner) Deleting directory /tmp/20130910093418955
09:34:22,092 INFO [stdout] (com.liferay.portal.kernel.deploy.auto.AutoDeployScanner) 09:34:22,092 INFO [com.liferay.portal.kernel.deploy.auto.AutoDeployScanner][PortletAutoDeployListener:89] Portlets for /srv/jboss/liferay-portal-6.1.2-ce-ga3/deploy/btop-portlet-6.1.1.1.war copied successfully. Deployment will start in a few seconds.
09:34:25,430 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) JBAS015003: Found btop-portlet.war in deployment directory. To trigger deployment create a file called btop-portlet.war.dodeploy
09:34:25,437 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "btop-portlet.war"
09:34:26,905 INFO [stdout] (MSC service thread 1-2) 09:34:26,904 INFO [MSC service thread 1-2][HotDeployImpl:185] Deploying btop-portlet from queue
09:34:26,906 INFO [stdout] (MSC service thread 1-2) 09:34:26,906 INFO [MSC service thread 1-2][PluginPackageUtil:1049] Reading plugin package for btop-portlet
09:34:26,986 INFO [stdout] (MSC service thread 1-2) Loading vfs:/srv/jboss/liferay-portal-6.1.2-ce-ga3/jboss-7.1.1/standalone/deployments/btop-portlet.war/WEB-INF/classes/portlet.properties
09:34:26,987 INFO [stdout] (MSC service thread 1-2) Loading vfs:/srv/jboss/liferay-portal-6.1.2-ce-ga3/jboss-7.1.1/standalone/deployments/btop-portlet.war/WEB-INF/classes/service.properties
09:34:27,023 INFO [stdout] (MSC service thread 1-2) 09:34:27,022 INFO [MSC service thread 1-2][ServiceComponentLocalServiceImpl:280] Running Payment SQL scripts
09:34:27,805 INFO [stdout] (MSC service thread 1-2) Loading vfs:/srv/jboss/liferay-portal-6.1.2-ce-ga3/jboss-7.1.1/standalone/deployments/btop-portlet.war/WEB-INF/classes/portlet.properties
09:34:27,806 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/btop-portlet]] (MSC service thread 1-2) Initializing Spring root WebApplicationContext
09:34:27,813 INFO [stdout] (MSC service thread 1-2) Loading vfs:/srv/jboss/liferay-portal-6.1.2-ce-ga3/jboss-7.1.1/standalone/deployments/btop-portlet.war/WEB-INF/classes/service.properties
09:34:30,521 INFO [stdout] (MSC service thread 1-2) Loading vfs:/srv/jboss/liferay-portal-6.1.2-ce-ga3/jboss-7.1.1/standalone/deployments/btop-portlet.war/WEB-INF/classes/service.properties
09:34:31,080 INFO [stdout] (MSC service thread 1-2) 09:34:31,074 INFO [MSC service thread 1-2][MessageBroker:30] Starting message broker
09:34:31,588 ERROR [stderr] (JMX connector) Exception in thread "JMX connector" java.lang.UnsupportedOperationException: JBAS011859: Naming context is read-only
09:34:31,588 ERROR [stderr] (JMX connector) at org.jboss.as.naming.WritableServiceBasedNamingStore.requireOwner(WritableServiceBasedNamingStore.java:126)
09:34:31,589 ERROR [stderr] (JMX connector) at org.jboss.as.naming.WritableServiceBasedNamingStore.bind(WritableServiceBasedNamingStore.java:56)
09:34:31,675 ERROR [stderr] (JMX connector) at org.jboss.as.naming.NamingContext.bind(NamingContext.java:221)
09:34:31,676 ERROR [stderr] (JMX connector) at org.jboss.as.naming.InitialContext.bind(InitialContext.java:161)
09:34:31,676 ERROR [stderr] (JMX connector) at org.jboss.as.naming.NamingContext.bind(NamingContext.java:230)
09:34:31,676 ERROR [stderr] (JMX connector) at com.liferay.portal.security.pacl.jndi.SchemeAwareContextWrapper.bind(SchemeAwareContextWrapper.java:57)
09:34:31,677 ERROR [stderr] (JMX connector) at javax.naming.InitialContext.bind(InitialContext.java:417)
09:34:31,677 ERROR [stderr] (JMX connector) at javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:639)
09:34:31,677 ERROR [stderr] (JMX connector) at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:426)
09:34:31,678 ERROR [stderr] (JMX connector) at org.apache.activemq.broker.jmx.ManagementContext$1.run(ManagementContext.java:131)
09:34:31,783 INFO [org.apache.activemq.store.kahadb.plist.PListStoreImpl] (MSC service thread 1-2) PListStore:[/srv/jboss/liferay-portal-6.1.2-ce-ga3/jboss-7.1.1/bin/amq/data/btop/tmp_storage] started
09:34:31,801 INFO [org.apache.activemq.broker.BrokerService] (MSC service thread 1-2) Using Persistence Adapter: KahaDBPersistenceAdapter[/srv/jboss/liferay-portal-6.1.2-ce-ga3/jboss-7.1.1/bin/amq/data/btop/KahaDB]
09:34:33,974 INFO [org.apache.activemq.broker.BrokerService] (MSC service thread 1-2) Apache ActiveMQ 5.8.0 (btop, ID:btop-re7-61864-1378805673826-0:1) is starting
09:34:33,998 INFO [org.apache.activemq.transport.TransportServerThreadSupport] (MSC service thread 1-2) Listening for connections at: tcp://localhost:61616
09:34:33,999 INFO [org.apache.activemq.broker.TransportConnector] (MSC service thread 1-2) Connector tcp://localhost:61616 Started
09:34:34,006 INFO [org.apache.activemq.broker.BrokerService] (MSC service thread 1-2) Apache ActiveMQ 5.8.0 (btop, ID:btop-re7-61864-1378805673826-0:1) started
09:34:34,007 ERROR [stderr] (JMX connector) Exception in thread "JMX connector" java.lang.UnsupportedOperationException: JBAS011859: Naming context is read-only
09:34:34,049 INFO [org.apache.activemq.broker.BrokerService] (MSC service thread 1-2) For help or more information please see: http://activemq.apache.org
09:34:34,051 ERROR [stderr] (JMX connector) at org.jboss.as.naming.WritableServiceBasedNamingStore.requireOwner(WritableServiceBasedNamingStore.java:126)
09:34:34,054 WARN [org.apache.activemq.broker.BrokerService] (MSC service thread 1-2) Store limit is 102400 mb, whilst the data directory: /srv/jboss/liferay-portal-6.1.2-ce-ga3/jboss-7.1.1/bin/amq/data/btop/KahaDB only has 3848 mb of usable space
09:34:34,055 ERROR [stderr] (JMX connector) at org.jboss.as.naming.WritableServiceBasedNamingStore.bind(WritableServiceBasedNamingStore.java:56)
09:34:34,057 ERROR [org.apache.activemq.broker.BrokerService] (MSC service thread 1-2) Temporary Store limit is 51200 mb, whilst the temporary data directory: /srv/jboss/liferay-portal-6.1.2-ce-ga3/jboss-7.1.1/bin/amq/data/btop/tmp_storage only has 3848 mb of usable space
09:34:34,064 ERROR [stderr] (JMX connector) at org.jboss.as.naming.NamingContext.bind(NamingContext.java:221)
09:34:34,065 ERROR [stderr] (JMX connector) at org.jboss.as.naming.InitialContext.bind(InitialContext.java:161)
09:34:34,066 ERROR [stderr] (JMX connector) at org.jboss.as.naming.NamingContext.bind(NamingContext.java:230)
09:34:34,067 ERROR [stderr] (JMX connector) at com.liferay.portal.security.pacl.jndi.SchemeAwareContextWrapper.bind(SchemeAwareContextWrapper.java:57)
09:34:34,076 ERROR [stderr] (JMX connector) at javax.naming.InitialContext.bind(InitialContext.java:417)
09:34:34,077 ERROR [stderr] (JMX connector) at javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:639)
09:34:34,078 ERROR [stderr] (JMX connector) at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:426)
09:34:34,079 ERROR [stderr] (JMX connector) at org.apache.activemq.broker.jmx.ManagementContext$1.run(ManagementContext.java:131)
09:34:34,157 INFO [stdout] (MSC service thread 1-2) 09:34:34,156 INFO [MSC service thread 1-2][HookHotDeployListener:584] Registering hook for btop-portlet
09:34:34,170 INFO [stdout] (MSC service thread 1-2) Loading vfs:/srv/jboss/liferay-portal-6.1.2-ce-ga3/jboss-7.1.1/standalone/deployments/btop-portlet.war/WEB-INF/classes/portal.properties
09:34:34,199 INFO [stdout] (pool-13-thread-1) 09:34:34,198 INFO [pool-13-thread-1][BaseMessageListener:90] Starting message listener for btop-portlet, destination Beorn.Payment.System.Plugins
09:34:34,232 INFO [stdout] (pool-14-thread-1) 09:34:34,203 INFO [pool-14-thread-1][BaseMessageListener:90] Starting message listener for btop-portlet, destination Beorn.Payment.App.btop-portlet
09:34:34,386 INFO [stdout] (MSC service thread 1-2) 09:34:34,385 INFO [MSC service thread 1-2][HookHotDeployListener:711] Hook for btop-portlet is available for use
09:34:34,394 INFO [stdout] (MSC service thread 1-2) 09:34:34,393 INFO [MSC service thread 1-2][PortletHotDeployListener:295] Registering portlets for btop-portlet
09:34:34,493 INFO [org.apache.activemq.transport.failover.FailoverTransport] (ActiveMQ Task-1) Successfully connected to tcp://localhost:61616
09:34:34,494 INFO [org.apache.activemq.transport.failover.FailoverTransport] (ActiveMQ Task-1) Successfully connected to tcp://localhost:61616
09:34:34,751 INFO [stdout] (MSC service thread 1-2) Loading vfs:/srv/jboss/liferay-portal-6.1.2-ce-ga3/jboss-7.1.1/standalone/deployments/btop-portlet.war/WEB-INF/classes/portlet.properties
09:34:35,076 INFO [stdout] (MSC service thread 1-2) 09:34:35,076 INFO [MSC service thread 1-2][PortletHotDeployListener:454] 1 portlet for btop-portlet is available for use
09:34:35,148 INFO [stdout] (pool-14-thread-1) 09:34:35,148 INFO [pool-14-thread-1][BaseMessageSender:74] Starting message sender for btop-portlet
09:34:35,221 INFO [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-2) Initialisation de Mojarra 2.1.7-jbossorg-1 (20120227-1401) pour le contexte «/btop-portlet»
09:34:35,223 INFO [org.apache.activemq.transport.failover.FailoverTransport] (ActiveMQ Task-1) Successfully connected to tcp://localhost:61616
09:34:35,306 INFO [stdout] (pool-13-thread-1) 09:34:35,304 INFO [pool-13-thread-1][BaseMessageSender:74] Starting message sender for btop-portlet
09:34:35,362 INFO [org.apache.activemq.transport.failover.FailoverTransport] (ActiveMQ Task-1) Successfully connected to tcp://localhost:61616
09:34:35,571 INFO [stdout] (pool-13-thread-1) 09:34:35,571 INFO [pool-13-thread-1][BaseMessageListener:90] Starting message listener for btop-portlet, destination Beorn.Payment.System.Apps
09:34:35,635 INFO [org.apache.activemq.transport.failover.FailoverTransport] (ActiveMQ Task-1) Successfully connected to tcp://localhost:61616
09:34:35,772 INFO [stdout] (pool-13-thread-1) 09:34:35,772 INFO [pool-13-thread-1][BaseMessageSender:74] Starting message sender for btop-portlet
09:34:35,806 INFO [org.apache.activemq.transport.failover.FailoverTransport] (ActiveMQ Task-1) Successfully connected to tcp://localhost:61616
09:34:35,862 INFO [org.jboss.web] (MSC service thread 1-2) JBAS018210: Registering web context: /btop-portlet
09:34:35,906 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS018559: Deployed "btop-portlet.war"
09:34:41,347 INFO [org.apache.activemq.transport.failover.FailoverTransport] (ActiveMQ Task-1) Successfully connected to tcp://localhost:61616
09:34:41,489 INFO [stdout] (pool-12-thread-1) 09:34:41,488 INFO [pool-12-thread-1][BaseMessageSender:74] Starting message sender for demo-payment-plugin-portlet
09:34:41,532 INFO [org.apache.activemq.transport.failover.FailoverTransport] (ActiveMQ Task-1) Successfully connected to tcp://localhost:61616
09:34:41,721 INFO [stdout] (ActiveMQ Session Task-1) 09:34:41,720 WARN [ActiveMQ Session Task-1][PaymentPluginPersistenceImpl:1601] No PaymentPlugin exists with the key {applicationId=demo-payment-plugin-portlet}
09:34:41,815 INFO [stdout] (ActiveMQ Session Task-1) 09:34:41,814 WARN [ActiveMQ Session Task-1][PaymentMethodPersistenceImpl:1594] No PaymentMethod exists with the key {key=demo}
09:34:47,529 INFO [org.apache.activemq.transport.failover.FailoverTransport] (ActiveMQ Task-1) Successfully connected to tcp://localhost:61616
09:34:47,724 INFO [stdout] (pool-11-thread-1) 09:34:47,723 INFO [pool-11-thread-1][BaseMessageSender:74] Starting message sender for paypal-payment-plugin-portlet
09:34:47,778 INFO [org.apache.activemq.transport.failover.FailoverTransport] (ActiveMQ Task-1) Successfully connected to tcp://localhost:61616
09:34:48,326 INFO [stdout] (ActiveMQ Session Task-1) 09:34:48,325 WARN [ActiveMQ Session Task-1][PaymentPluginPersistenceImpl:1601] No PaymentPlugin exists with the key {applicationId=paypal-payment-plugin-portlet}
09:34:48,362 INFO [stdout] (ActiveMQ Session Task-1) 09:34:48,362 WARN [ActiveMQ Session Task-1][PaymentMethodPersistenceImpl:1594] No PaymentMethod exists with the key {key=paypal}
Release: Liferay 6.1.1 ga2 bundled with JBoss
While deploying Btop portlet, an error rises in the logs even if it seems to be complete.
Here is the full deployment trace: