[JBoss JIRA] (RTGOV-595) List of services can't be refreshed on EAP
by Andrej Vano (JIRA)
Andrej Vano created RTGOV-595:
---------------------------------
Summary: List of services can't be refreshed on EAP
Key: RTGOV-595
URL: https://issues.jboss.org/browse/RTGOV-595
Project: RTGov (Run Time Governance)
Issue Type: Bug
Components: User Interface
Affects Versions: 2.0.0.Final
Environment: EAP 6.3 + switchyard 2.0.0.Alpha2 + rtgov 2.0.0.Final
Reporter: Andrej Vano
Assignee: Gary Brown
Fix For: 2.1.0.Final
If you access the services page, the deployed services are immediately listed correctly. When you hit the refresh button, the list of services can't be refreshed - it will hang on Finding services, please wait... (no result even after 2 mins)
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 3 months
[JBoss JIRA] (SRAMP-591) Default EAP 6.3 Installation throws ERROR:Naming context is read-only
by Sebastian Goschin (JIRA)
[ https://issues.jboss.org/browse/SRAMP-591?page=com.atlassian.jira.plugin.... ]
Sebastian Goschin commented on SRAMP-591:
-----------------------------------------
Thanks for this info. It worked for me as well.
> Default EAP 6.3 Installation throws ERROR:Naming context is read-only
> ---------------------------------------------------------------------
>
> Key: SRAMP-591
> URL: https://issues.jboss.org/browse/SRAMP-591
> Project: S-RAMP
> Issue Type: Bug
> Environment: CentOs 7 (3.10.0-123.el7.x86_64),
> JAVA: java version "1.7.0_65"; OpenJDK Runtime Environment (rhel-2.5.1.2.el7_0-x86_64 u65-b17); OpenJDK 64-Bit Server VM (build 24.65-b04, mixed mode)
> Apache Ant 1.9.2
> The whole system runs inside of a virtual box with 4GB RAM, 2 CPUs and 50GB Harddrive.
> Reporter: Sebastian Goschin
> Assignee: Brett Meyer
>
> After installing DTgov and S-RAMP at EAP 6.3 and before installing workflows and ontologies of DTgov 1.4 by "ant seed", the EAP 6.3 throws errors during startup.
> 18:18:49,657 WARN [org.overlord.sramp.events.jms.JMSEventProducer] (ServerService Thread Pool -- 58) Could not discover "ConnectionFactory" and/or the configured topics/queues over JNDI. Assuming a non-EE environment or that JMS/JNDI isnt configured. Falling back on an embedded ActiveMQ broker, available on {0}
> 18:18:50,196 INFO [org.apache.activemq.store.kahadb.plist.PListStoreImpl] (ServerService Thread Pool -- 58) PListStore:[/home/admin/activemq-data/localhost/tmp_storage] started
> 18:18:50,201 INFO [org.apache.activemq.broker.BrokerService] (ServerService Thread Pool -- 58) Using Persistence Adapter: KahaDBPersistenceAdapter[/home/admin/activemq-data/localhost/KahaDB]
> 18:18:50,234 INFO [org.jboss.solder.exception.control.extension] (MSC service thread 1-4) Adding handler Qualifiers: [@javax.enterprise.inject.Any()] TraversalMode: BREADTH_FIRST Handles Type: class java.lang.Throwable Precedence: -100 [method] public org.jboss.seam.transaction.SimpleTransactionExceptionHandler.markTransactionRollback(CaughtException<Throwable>) to known handlers
> 18:18:50,248 ERROR [stderr] (JMX connector) Exception in thread "JMX connector" java.lang.UnsupportedOperationException: JBAS011859: Naming context is read-only
> 18:18:50,279 ERROR [stderr] (JMX connector) at org.jboss.as.naming.WritableServiceBasedNamingStore.requireOwner(WritableServiceBasedNamingStore.java:155)
> 18:18:50,279 ERROR [stderr] (JMX connector) at org.jboss.as.naming.WritableServiceBasedNamingStore.bind(WritableServiceBasedNamingStore.java:63)
> 18:18:50,280 ERROR [stderr] (JMX connector) at org.jboss.as.naming.NamingContext.bind(NamingContext.java:248)
> 18:18:50,280 ERROR [stderr] (JMX connector) at org.jboss.as.naming.InitialContext$DefaultInitialContext.bind(InitialContext.java:268)
> 18:18:50,280 ERROR [stderr] (JMX connector) at org.jboss.as.naming.NamingContext.bind(NamingContext.java:257)
> 18:18:50,281 ERROR [stderr] (JMX connector) at javax.naming.InitialContext.bind(InitialContext.java:419)
> 18:18:50,281 ERROR [stderr] (JMX connector) at javax.naming.InitialContext.bind(InitialContext.java:419)
> 18:18:50,281 ERROR [stderr] (JMX connector) at javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:643)
> 18:18:50,281 ERROR [stderr] (JMX connector) at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:426)
> 18:18:50,282 ERROR [stderr] (JMX connector) at org.apache.activemq.broker.jmx.ManagementContext$1.run(ManagementContext.java:131)
> 18:18:50,556 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-001440 Scope type @javax.enterprise.context.ApplicationScoped() used on injection point [field] @ApplicationScoped @Inject private org.overlord.sramp.governance.workflow.jbpm.ProcessService.processBean
> 18:18:50,560 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-001440 Scope type @javax.enterprise.context.ApplicationScoped() used on injection point [field] @ApplicationScoped @Inject private org.overlord.dtgov.jbpm.ProcessBean.processEngineService
> 18:18:50,581 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-001440 Scope type @javax.enterprise.context.ApplicationScoped() used on injection point [field] @ApplicationScoped @Inject private org.overlord.dtgov.taskapi.TaskApi.processEngineService
> 18:18:50,799 INFO [org.jboss.web] (ServerService Thread Pool -- 68) JBAS018210: Register web context: /dtgov
> 18:18:51,107 INFO [solder-servlet] (ServerService Thread Pool -- 68) Catch Integration for Servlets enabled
> 18:18:57,085 INFO [org.apache.activemq.store.kahadb.MessageDatabase] (ServerService Thread Pool -- 58) KahaDB is version 4
> 18:18:57,110 INFO [org.apache.activemq.store.kahadb.MessageDatabase] (ServerService Thread Pool -- 58) Recovering from the journal ...
> 18:18:57,111 INFO [org.apache.activemq.store.kahadb.MessageDatabase] (ServerService Thread Pool -- 58) Recovery replayed 2 operations from the journal in 0.008 seconds.
> 18:18:57,162 INFO [org.apache.activemq.broker.BrokerService] (ServerService Thread Pool -- 58) Apache ActiveMQ 5.8.0 (localhost, ID:overlordtestserver-38457-1412871529503-2:1) is starting
> 18:18:57,176 INFO [org.apache.activemq.transport.TransportServerThreadSupport] (ServerService Thread Pool -- 58) Listening for connections at: tcp://localhost:61616
> 18:18:57,177 INFO [org.apache.activemq.broker.TransportConnector] (ServerService Thread Pool -- 58) Connector tcp://localhost:61616 Started
> 18:18:57,178 INFO [org.apache.activemq.broker.BrokerService] (ServerService Thread Pool -- 58) Apache ActiveMQ 5.8.0 (localhost, ID:overlordtestserver-38457-1412871529503-2:1) started
> 18:18:57,178 INFO [org.apache.activemq.broker.BrokerService] (ServerService Thread Pool -- 58) For help or more information please see: http://activemq.apache.org
> 18:18:57,178 WARN [org.apache.activemq.broker.BrokerService] (ServerService Thread Pool -- 58) Store limit is 102400 mb, whilst the data directory: /home/admin/activemq-data/localhost/KahaDB only has 44079 mb of usable space
> 18:18:57,179 ERROR [org.apache.activemq.broker.BrokerService] (ServerService Thread Pool -- 58) Temporary Store limit is 51200 mb, whilst the temporary data directory: /home/admin/activemq-data/localhost/tmp_storage only has 44079 mb of usable space
> 18:18:57,211 ERROR [stderr] (JMX connector) Exception in thread "JMX connector" java.lang.UnsupportedOperationException: JBAS011859: Naming context is read-only
> 18:18:57,211 ERROR [stderr] (JMX connector) at org.jboss.as.naming.WritableServiceBasedNamingStore.requireOwner(WritableServiceBasedNamingStore.java:155)
> 18:18:57,213 ERROR [stderr] (JMX connector) at org.jboss.as.naming.WritableServiceBasedNamingStore.bind(WritableServiceBasedNamingStore.java:63)
> 18:18:57,213 ERROR [stderr] (JMX connector) at org.jboss.as.naming.NamingContext.bind(NamingContext.java:248)
> 18:18:57,213 ERROR [stderr] (JMX connector) at org.jboss.as.naming.InitialContext$DefaultInitialContext.bind(InitialContext.java:268)
> 18:18:57,213 ERROR [stderr] (JMX connector) at org.jboss.as.naming.NamingContext.bind(NamingContext.java:257)
> 18:18:57,213 ERROR [stderr] (JMX connector) at javax.naming.InitialContext.bind(InitialContext.java:419)
> 18:18:57,213 ERROR [stderr] (JMX connector) at javax.naming.InitialContext.bind(InitialContext.java:419)
> 18:18:57,214 ERROR [stderr] (JMX connector) at javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:643)
> 18:18:57,214 ERROR [stderr] (JMX connector) at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:426)
> 18:18:57,214 ERROR [stderr] (JMX connector) at org.apache.activemq.broker.jmx.ManagementContext$1.run(ManagementContext.java:131)
> 18:18:57,218 INFO [org.apache.activemq.broker.TransportConnector] (ServerService Thread Pool -- 58) Connector vm://localhost Started
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 3 months
[JBoss JIRA] (SRAMP-591) Default EAP 6.3 Installation throws ERROR:Naming context is read-only
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/SRAMP-591?page=com.atlassian.jira.plugin.... ]
Brett Meyer commented on SRAMP-591:
-----------------------------------
I was able to reproduce what you're seeing when using standalone, but it appears to work perfectly with standalone-full. I'm seeing a few suggestions here and there that there may have been a problem with ActiveMQ within EAP that may have caused the specific errors, but supposedly that was already fixed. Unfortunately, I can't find much more info about it.
For now, we'll need to require standalone-full:
{code}bin/standalone.sh -c standalone-full.xml{code}
That may be a good idea, considering some of the things coming up on the roadmap.
I've added more info to the docs.
> Default EAP 6.3 Installation throws ERROR:Naming context is read-only
> ---------------------------------------------------------------------
>
> Key: SRAMP-591
> URL: https://issues.jboss.org/browse/SRAMP-591
> Project: S-RAMP
> Issue Type: Bug
> Environment: CentOs 7 (3.10.0-123.el7.x86_64),
> JAVA: java version "1.7.0_65"; OpenJDK Runtime Environment (rhel-2.5.1.2.el7_0-x86_64 u65-b17); OpenJDK 64-Bit Server VM (build 24.65-b04, mixed mode)
> Apache Ant 1.9.2
> The whole system runs inside of a virtual box with 4GB RAM, 2 CPUs and 50GB Harddrive.
> Reporter: Sebastian Goschin
> Assignee: Brett Meyer
>
> After installing DTgov and S-RAMP at EAP 6.3 and before installing workflows and ontologies of DTgov 1.4 by "ant seed", the EAP 6.3 throws errors during startup.
> 18:18:49,657 WARN [org.overlord.sramp.events.jms.JMSEventProducer] (ServerService Thread Pool -- 58) Could not discover "ConnectionFactory" and/or the configured topics/queues over JNDI. Assuming a non-EE environment or that JMS/JNDI isnt configured. Falling back on an embedded ActiveMQ broker, available on {0}
> 18:18:50,196 INFO [org.apache.activemq.store.kahadb.plist.PListStoreImpl] (ServerService Thread Pool -- 58) PListStore:[/home/admin/activemq-data/localhost/tmp_storage] started
> 18:18:50,201 INFO [org.apache.activemq.broker.BrokerService] (ServerService Thread Pool -- 58) Using Persistence Adapter: KahaDBPersistenceAdapter[/home/admin/activemq-data/localhost/KahaDB]
> 18:18:50,234 INFO [org.jboss.solder.exception.control.extension] (MSC service thread 1-4) Adding handler Qualifiers: [@javax.enterprise.inject.Any()] TraversalMode: BREADTH_FIRST Handles Type: class java.lang.Throwable Precedence: -100 [method] public org.jboss.seam.transaction.SimpleTransactionExceptionHandler.markTransactionRollback(CaughtException<Throwable>) to known handlers
> 18:18:50,248 ERROR [stderr] (JMX connector) Exception in thread "JMX connector" java.lang.UnsupportedOperationException: JBAS011859: Naming context is read-only
> 18:18:50,279 ERROR [stderr] (JMX connector) at org.jboss.as.naming.WritableServiceBasedNamingStore.requireOwner(WritableServiceBasedNamingStore.java:155)
> 18:18:50,279 ERROR [stderr] (JMX connector) at org.jboss.as.naming.WritableServiceBasedNamingStore.bind(WritableServiceBasedNamingStore.java:63)
> 18:18:50,280 ERROR [stderr] (JMX connector) at org.jboss.as.naming.NamingContext.bind(NamingContext.java:248)
> 18:18:50,280 ERROR [stderr] (JMX connector) at org.jboss.as.naming.InitialContext$DefaultInitialContext.bind(InitialContext.java:268)
> 18:18:50,280 ERROR [stderr] (JMX connector) at org.jboss.as.naming.NamingContext.bind(NamingContext.java:257)
> 18:18:50,281 ERROR [stderr] (JMX connector) at javax.naming.InitialContext.bind(InitialContext.java:419)
> 18:18:50,281 ERROR [stderr] (JMX connector) at javax.naming.InitialContext.bind(InitialContext.java:419)
> 18:18:50,281 ERROR [stderr] (JMX connector) at javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:643)
> 18:18:50,281 ERROR [stderr] (JMX connector) at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:426)
> 18:18:50,282 ERROR [stderr] (JMX connector) at org.apache.activemq.broker.jmx.ManagementContext$1.run(ManagementContext.java:131)
> 18:18:50,556 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-001440 Scope type @javax.enterprise.context.ApplicationScoped() used on injection point [field] @ApplicationScoped @Inject private org.overlord.sramp.governance.workflow.jbpm.ProcessService.processBean
> 18:18:50,560 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-001440 Scope type @javax.enterprise.context.ApplicationScoped() used on injection point [field] @ApplicationScoped @Inject private org.overlord.dtgov.jbpm.ProcessBean.processEngineService
> 18:18:50,581 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-001440 Scope type @javax.enterprise.context.ApplicationScoped() used on injection point [field] @ApplicationScoped @Inject private org.overlord.dtgov.taskapi.TaskApi.processEngineService
> 18:18:50,799 INFO [org.jboss.web] (ServerService Thread Pool -- 68) JBAS018210: Register web context: /dtgov
> 18:18:51,107 INFO [solder-servlet] (ServerService Thread Pool -- 68) Catch Integration for Servlets enabled
> 18:18:57,085 INFO [org.apache.activemq.store.kahadb.MessageDatabase] (ServerService Thread Pool -- 58) KahaDB is version 4
> 18:18:57,110 INFO [org.apache.activemq.store.kahadb.MessageDatabase] (ServerService Thread Pool -- 58) Recovering from the journal ...
> 18:18:57,111 INFO [org.apache.activemq.store.kahadb.MessageDatabase] (ServerService Thread Pool -- 58) Recovery replayed 2 operations from the journal in 0.008 seconds.
> 18:18:57,162 INFO [org.apache.activemq.broker.BrokerService] (ServerService Thread Pool -- 58) Apache ActiveMQ 5.8.0 (localhost, ID:overlordtestserver-38457-1412871529503-2:1) is starting
> 18:18:57,176 INFO [org.apache.activemq.transport.TransportServerThreadSupport] (ServerService Thread Pool -- 58) Listening for connections at: tcp://localhost:61616
> 18:18:57,177 INFO [org.apache.activemq.broker.TransportConnector] (ServerService Thread Pool -- 58) Connector tcp://localhost:61616 Started
> 18:18:57,178 INFO [org.apache.activemq.broker.BrokerService] (ServerService Thread Pool -- 58) Apache ActiveMQ 5.8.0 (localhost, ID:overlordtestserver-38457-1412871529503-2:1) started
> 18:18:57,178 INFO [org.apache.activemq.broker.BrokerService] (ServerService Thread Pool -- 58) For help or more information please see: http://activemq.apache.org
> 18:18:57,178 WARN [org.apache.activemq.broker.BrokerService] (ServerService Thread Pool -- 58) Store limit is 102400 mb, whilst the data directory: /home/admin/activemq-data/localhost/KahaDB only has 44079 mb of usable space
> 18:18:57,179 ERROR [org.apache.activemq.broker.BrokerService] (ServerService Thread Pool -- 58) Temporary Store limit is 51200 mb, whilst the temporary data directory: /home/admin/activemq-data/localhost/tmp_storage only has 44079 mb of usable space
> 18:18:57,211 ERROR [stderr] (JMX connector) Exception in thread "JMX connector" java.lang.UnsupportedOperationException: JBAS011859: Naming context is read-only
> 18:18:57,211 ERROR [stderr] (JMX connector) at org.jboss.as.naming.WritableServiceBasedNamingStore.requireOwner(WritableServiceBasedNamingStore.java:155)
> 18:18:57,213 ERROR [stderr] (JMX connector) at org.jboss.as.naming.WritableServiceBasedNamingStore.bind(WritableServiceBasedNamingStore.java:63)
> 18:18:57,213 ERROR [stderr] (JMX connector) at org.jboss.as.naming.NamingContext.bind(NamingContext.java:248)
> 18:18:57,213 ERROR [stderr] (JMX connector) at org.jboss.as.naming.InitialContext$DefaultInitialContext.bind(InitialContext.java:268)
> 18:18:57,213 ERROR [stderr] (JMX connector) at org.jboss.as.naming.NamingContext.bind(NamingContext.java:257)
> 18:18:57,213 ERROR [stderr] (JMX connector) at javax.naming.InitialContext.bind(InitialContext.java:419)
> 18:18:57,213 ERROR [stderr] (JMX connector) at javax.naming.InitialContext.bind(InitialContext.java:419)
> 18:18:57,214 ERROR [stderr] (JMX connector) at javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:643)
> 18:18:57,214 ERROR [stderr] (JMX connector) at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:426)
> 18:18:57,214 ERROR [stderr] (JMX connector) at org.apache.activemq.broker.jmx.ManagementContext$1.run(ManagementContext.java:131)
> 18:18:57,218 INFO [org.apache.activemq.broker.TransportConnector] (ServerService Thread Pool -- 58) Connector vm://localhost Started
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 3 months
[JBoss JIRA] (SRAMP-591) Default EAP 6.3 Installation throws ERROR:Naming context is read-only
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/SRAMP-591?page=com.atlassian.jira.plugin.... ]
Brett Meyer moved DTGOV-245 to SRAMP-591:
-----------------------------------------
Project: S-RAMP (was: DTGov (Design Time Governance))
Key: SRAMP-591 (was: DTGOV-245)
Affects Version/s: (was: 1.4)
Fix Version/s: (was: 1.5)
> Default EAP 6.3 Installation throws ERROR:Naming context is read-only
> ---------------------------------------------------------------------
>
> Key: SRAMP-591
> URL: https://issues.jboss.org/browse/SRAMP-591
> Project: S-RAMP
> Issue Type: Bug
> Environment: CentOs 7 (3.10.0-123.el7.x86_64),
> JAVA: java version "1.7.0_65"; OpenJDK Runtime Environment (rhel-2.5.1.2.el7_0-x86_64 u65-b17); OpenJDK 64-Bit Server VM (build 24.65-b04, mixed mode)
> Apache Ant 1.9.2
> The whole system runs inside of a virtual box with 4GB RAM, 2 CPUs and 50GB Harddrive.
> Reporter: Sebastian Goschin
> Assignee: Brett Meyer
>
> After installing DTgov and S-RAMP at EAP 6.3 and before installing workflows and ontologies of DTgov 1.4 by "ant seed", the EAP 6.3 throws errors during startup.
> 18:18:49,657 WARN [org.overlord.sramp.events.jms.JMSEventProducer] (ServerService Thread Pool -- 58) Could not discover "ConnectionFactory" and/or the configured topics/queues over JNDI. Assuming a non-EE environment or that JMS/JNDI isnt configured. Falling back on an embedded ActiveMQ broker, available on {0}
> 18:18:50,196 INFO [org.apache.activemq.store.kahadb.plist.PListStoreImpl] (ServerService Thread Pool -- 58) PListStore:[/home/admin/activemq-data/localhost/tmp_storage] started
> 18:18:50,201 INFO [org.apache.activemq.broker.BrokerService] (ServerService Thread Pool -- 58) Using Persistence Adapter: KahaDBPersistenceAdapter[/home/admin/activemq-data/localhost/KahaDB]
> 18:18:50,234 INFO [org.jboss.solder.exception.control.extension] (MSC service thread 1-4) Adding handler Qualifiers: [@javax.enterprise.inject.Any()] TraversalMode: BREADTH_FIRST Handles Type: class java.lang.Throwable Precedence: -100 [method] public org.jboss.seam.transaction.SimpleTransactionExceptionHandler.markTransactionRollback(CaughtException<Throwable>) to known handlers
> 18:18:50,248 ERROR [stderr] (JMX connector) Exception in thread "JMX connector" java.lang.UnsupportedOperationException: JBAS011859: Naming context is read-only
> 18:18:50,279 ERROR [stderr] (JMX connector) at org.jboss.as.naming.WritableServiceBasedNamingStore.requireOwner(WritableServiceBasedNamingStore.java:155)
> 18:18:50,279 ERROR [stderr] (JMX connector) at org.jboss.as.naming.WritableServiceBasedNamingStore.bind(WritableServiceBasedNamingStore.java:63)
> 18:18:50,280 ERROR [stderr] (JMX connector) at org.jboss.as.naming.NamingContext.bind(NamingContext.java:248)
> 18:18:50,280 ERROR [stderr] (JMX connector) at org.jboss.as.naming.InitialContext$DefaultInitialContext.bind(InitialContext.java:268)
> 18:18:50,280 ERROR [stderr] (JMX connector) at org.jboss.as.naming.NamingContext.bind(NamingContext.java:257)
> 18:18:50,281 ERROR [stderr] (JMX connector) at javax.naming.InitialContext.bind(InitialContext.java:419)
> 18:18:50,281 ERROR [stderr] (JMX connector) at javax.naming.InitialContext.bind(InitialContext.java:419)
> 18:18:50,281 ERROR [stderr] (JMX connector) at javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:643)
> 18:18:50,281 ERROR [stderr] (JMX connector) at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:426)
> 18:18:50,282 ERROR [stderr] (JMX connector) at org.apache.activemq.broker.jmx.ManagementContext$1.run(ManagementContext.java:131)
> 18:18:50,556 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-001440 Scope type @javax.enterprise.context.ApplicationScoped() used on injection point [field] @ApplicationScoped @Inject private org.overlord.sramp.governance.workflow.jbpm.ProcessService.processBean
> 18:18:50,560 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-001440 Scope type @javax.enterprise.context.ApplicationScoped() used on injection point [field] @ApplicationScoped @Inject private org.overlord.dtgov.jbpm.ProcessBean.processEngineService
> 18:18:50,581 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-001440 Scope type @javax.enterprise.context.ApplicationScoped() used on injection point [field] @ApplicationScoped @Inject private org.overlord.dtgov.taskapi.TaskApi.processEngineService
> 18:18:50,799 INFO [org.jboss.web] (ServerService Thread Pool -- 68) JBAS018210: Register web context: /dtgov
> 18:18:51,107 INFO [solder-servlet] (ServerService Thread Pool -- 68) Catch Integration for Servlets enabled
> 18:18:57,085 INFO [org.apache.activemq.store.kahadb.MessageDatabase] (ServerService Thread Pool -- 58) KahaDB is version 4
> 18:18:57,110 INFO [org.apache.activemq.store.kahadb.MessageDatabase] (ServerService Thread Pool -- 58) Recovering from the journal ...
> 18:18:57,111 INFO [org.apache.activemq.store.kahadb.MessageDatabase] (ServerService Thread Pool -- 58) Recovery replayed 2 operations from the journal in 0.008 seconds.
> 18:18:57,162 INFO [org.apache.activemq.broker.BrokerService] (ServerService Thread Pool -- 58) Apache ActiveMQ 5.8.0 (localhost, ID:overlordtestserver-38457-1412871529503-2:1) is starting
> 18:18:57,176 INFO [org.apache.activemq.transport.TransportServerThreadSupport] (ServerService Thread Pool -- 58) Listening for connections at: tcp://localhost:61616
> 18:18:57,177 INFO [org.apache.activemq.broker.TransportConnector] (ServerService Thread Pool -- 58) Connector tcp://localhost:61616 Started
> 18:18:57,178 INFO [org.apache.activemq.broker.BrokerService] (ServerService Thread Pool -- 58) Apache ActiveMQ 5.8.0 (localhost, ID:overlordtestserver-38457-1412871529503-2:1) started
> 18:18:57,178 INFO [org.apache.activemq.broker.BrokerService] (ServerService Thread Pool -- 58) For help or more information please see: http://activemq.apache.org
> 18:18:57,178 WARN [org.apache.activemq.broker.BrokerService] (ServerService Thread Pool -- 58) Store limit is 102400 mb, whilst the data directory: /home/admin/activemq-data/localhost/KahaDB only has 44079 mb of usable space
> 18:18:57,179 ERROR [org.apache.activemq.broker.BrokerService] (ServerService Thread Pool -- 58) Temporary Store limit is 51200 mb, whilst the temporary data directory: /home/admin/activemq-data/localhost/tmp_storage only has 44079 mb of usable space
> 18:18:57,211 ERROR [stderr] (JMX connector) Exception in thread "JMX connector" java.lang.UnsupportedOperationException: JBAS011859: Naming context is read-only
> 18:18:57,211 ERROR [stderr] (JMX connector) at org.jboss.as.naming.WritableServiceBasedNamingStore.requireOwner(WritableServiceBasedNamingStore.java:155)
> 18:18:57,213 ERROR [stderr] (JMX connector) at org.jboss.as.naming.WritableServiceBasedNamingStore.bind(WritableServiceBasedNamingStore.java:63)
> 18:18:57,213 ERROR [stderr] (JMX connector) at org.jboss.as.naming.NamingContext.bind(NamingContext.java:248)
> 18:18:57,213 ERROR [stderr] (JMX connector) at org.jboss.as.naming.InitialContext$DefaultInitialContext.bind(InitialContext.java:268)
> 18:18:57,213 ERROR [stderr] (JMX connector) at org.jboss.as.naming.NamingContext.bind(NamingContext.java:257)
> 18:18:57,213 ERROR [stderr] (JMX connector) at javax.naming.InitialContext.bind(InitialContext.java:419)
> 18:18:57,213 ERROR [stderr] (JMX connector) at javax.naming.InitialContext.bind(InitialContext.java:419)
> 18:18:57,214 ERROR [stderr] (JMX connector) at javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:643)
> 18:18:57,214 ERROR [stderr] (JMX connector) at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:426)
> 18:18:57,214 ERROR [stderr] (JMX connector) at org.apache.activemq.broker.jmx.ManagementContext$1.run(ManagementContext.java:131)
> 18:18:57,218 INFO [org.apache.activemq.broker.TransportConnector] (ServerService Thread Pool -- 58) Connector vm://localhost Started
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 3 months
