Re: [Dev] [MB] Error while starting MB 3.0.0 cluster setup
You can use applyConfigurationWithoutRestart() method in
ServerConfigurationManager class.
After applying all configuration call restartGracefully() method in the
same class.
Thanks,
Krishantha.
On Fri, May 22, 2015 at 9:28 AM, Asitha Nanayakkara asi...@wso2.com wrote:
Commenting out in-memory mode by default led to automation test failure
[1] since server couldn't start in in-memory mode without the in-memory
datasource set
For in-memory mode related test we are restarting the server with a
broker.xml file configured to start the server in in-memory mode. We assume
master-datasources.xml in-memory mode configuration is set. But if we
comment it out we need to find a way to activate it again when the server
restarts for in-memory mode tests.
@Krishantha Is there a way to restart a server with changes to multiple
configuration files. Currently we only change the broker.xml [2]
* Restart the testing MB server in In-Memory H2 database mode by applying
In-Memory database configurations * in andes-virtualhosts-H2-mem.xml file.
* * @throws Exception */ protected void restartServerWithH2MemMode()
throws Exception { serverManager = new ServerConfigurationManager
(automationContext); // Replace the broker.xml with the new configuration
and restarts the server. serverManager.applyConfiguration(new File(
FrameworkPathUtil.getSystemResourceLocation() + File.separator +
artifacts + File.separator + mb + File.separator + config +
File.separator
+ broker.xml), new File(ServerConfigurationManager.getCarbonHome() +
File.separator + repository + File.separator + conf + File.separator +
broker.xml), true, true); }
[1] https://wso2.org/jenkins/job/product-mb/424/console
[2]
https://github.com/wso2/product-mb/blob/master/modules/integration/tests-common/integration-tests-utils/src/main/java/org/wso2/mb/integration/common/utils/backend/MBIntegrationBaseTest.java#L63
Thanks,
Asitha
On Thu, May 21, 2015 at 10:44 AM, Asitha Nanayakkara asi...@wso2.com
wrote:
Hi all,
I've commented out H2 In-memory store by default with PR [1]
[1] https://github.com/wso2/product-mb/pull/102
On Thu, May 21, 2015 at 10:29 AM, Ramith Jayasinghe ram...@wso2.com
wrote:
+1
On Thu, May 21, 2015 at 10:26 AM, Hemika Kodikara hem...@wso2.com
wrote:
Also I think we should comment out the H2-In Memory store by default.
WDYT ?
Hemika Kodikara
Software Engineer
WSO2 Inc.
lean . enterprise . middleware
http://wso2.com
Mobile : +9477762
On Thu, May 21, 2015 at 10:22 AM, Hasitha Hiranya hasit...@wso2.com
wrote:
Better to highlight this in our docs as well.
On Wed, May 20, 2015 at 11:16 PM, Indika Sampath indi...@wso2.com
wrote:
I looked into master-datasources.xml and there are two RDBMS
datasources configured for WSO2MBStoreDB (H2 and MySQL). H2 is default
database we distributed with MB pack. Please comment it [1] before you
configure any other RDBMS datasource.
!-- WSO2 MB embedded H2 Store --
datasource
nameWSO2_MB_STORE_DB/name
descriptionThe datasource used for message broker
database/description
jndiConfig
nameWSO2MBStoreDB/name
/jndiConfig
definition type=RDBMS
configuration
urljdbc:h2:repository/database/WSO2MB_DB;DB_CLOSE_ON_EXIT=FALSE;LOCK_TIMEOUT=6/url
driverClassNameorg.h2.Driver/driverClassName
maxActive50/maxActive
maxWait6/maxWait
testOnBorrowtrue/testOnBorrow
validationQuerySELECT 1/validationQuery
validationInterval3/validationInterval
/configuration
/definition
/datasource
Cheers!
On Thu, May 21, 2015 at 8:33 AM, Amalka Subasinghe ama...@wso2.com
wrote:
attached broker.xml and master-datasources.xml files
On Wed, May 20, 2015 at 11:31 PM, Hemika Kodikara hem...@wso2.com
wrote:
Hi Amalka,
Can you attach the broker.xml file and master-datasources.xml files
?
Regards,
Hemika
Hemika Kodikara
Software Engineer
WSO2 Inc.
lean . enterprise . middleware
http://wso2.com
Mobile : +9477762
On Wed, May 20, 2015 at 10:54 PM, Amalka Subasinghe
ama...@wso2.com wrote:
I'm using M7 pack. but I have to create the databases manually.
On Wed, May 20, 2015 at 10:51 PM, Indika Sampath indi...@wso2.com
wrote:
Hi Amalka,
You don't need to externally run db script. Below set of tables
created when you start MB 3.0.0 pack with -Dsetup option. Which
milestone
pack did you configure ?
MB_BINDING
MB_CONTENT
MB_DURABLE_SUBSCRIPTION
MB_EXCHANGE
MB_EXPIRATION_DATA
MB_METADATA
MB_NODE
MB_QUEUE
MB_QUEUE_COUNTER
MB_QUEUE_MAPPING
Cheers!
On Wed, May 20, 2015 at 10:14 PM, Amalka Subasinghe
ama...@wso2.com wrote:
Hi,
I'm trying to setup MB cluster with 2 MB nodes. When I start the
MB node with -Dsetup following error was thrown.
Do
Re: [Dev] [MB] Error while starting MB 3.0.0 cluster setup
Hi Asitha,
Cant we use the serverManager.applyConfiguration() method to apply a
master-datasources.xml file as well along with the broker.xml ?
Here, the master-datasources.xml file will have H2-InMemory uncommented.
Regards,
Hemika
Hemika Kodikara
Software Engineer
WSO2 Inc.
lean . enterprise . middleware
http://wso2.com
Mobile : +9477762
On Fri, May 22, 2015 at 10:40 AM, Krishantha Samaraweera
krishan...@wso2.com wrote:
You can use applyConfigurationWithoutRestart() method in
ServerConfigurationManager class.
After applying all configuration call restartGracefully() method in the
same class.
Thanks,
Krishantha.
On Fri, May 22, 2015 at 9:28 AM, Asitha Nanayakkara asi...@wso2.com
wrote:
Commenting out in-memory mode by default led to automation test failure
[1] since server couldn't start in in-memory mode without the in-memory
datasource set
For in-memory mode related test we are restarting the server with a
broker.xml file configured to start the server in in-memory mode. We assume
master-datasources.xml in-memory mode configuration is set. But if we
comment it out we need to find a way to activate it again when the server
restarts for in-memory mode tests.
@Krishantha Is there a way to restart a server with changes to multiple
configuration files. Currently we only change the broker.xml [2]
* Restart the testing MB server in In-Memory H2 database mode by applying
In-Memory database configurations * in andes-virtualhosts-H2-mem.xml
file. * * @throws Exception */ protected void restartServerWithH2MemMode()
throws Exception { serverManager = new ServerConfigurationManager
(automationContext); // Replace the broker.xml with the new
configuration and restarts the server. serverManager.applyConfiguration(
new File(FrameworkPathUtil.getSystemResourceLocation() + File.separator +
artifacts + File.separator + mb + File.separator + config +
File.separator
+ broker.xml), new File(ServerConfigurationManager.getCarbonHome() +
File.separator + repository + File.separator + conf + File.separator
+ broker.xml), true, true); }
[1] https://wso2.org/jenkins/job/product-mb/424/console
[2]
https://github.com/wso2/product-mb/blob/master/modules/integration/tests-common/integration-tests-utils/src/main/java/org/wso2/mb/integration/common/utils/backend/MBIntegrationBaseTest.java#L63
Thanks,
Asitha
On Thu, May 21, 2015 at 10:44 AM, Asitha Nanayakkara asi...@wso2.com
wrote:
Hi all,
I've commented out H2 In-memory store by default with PR [1]
[1] https://github.com/wso2/product-mb/pull/102
On Thu, May 21, 2015 at 10:29 AM, Ramith Jayasinghe ram...@wso2.com
wrote:
+1
On Thu, May 21, 2015 at 10:26 AM, Hemika Kodikara hem...@wso2.com
wrote:
Also I think we should comment out the H2-In Memory store by default.
WDYT ?
Hemika Kodikara
Software Engineer
WSO2 Inc.
lean . enterprise . middleware
http://wso2.com
Mobile : +9477762
On Thu, May 21, 2015 at 10:22 AM, Hasitha Hiranya hasit...@wso2.com
wrote:
Better to highlight this in our docs as well.
On Wed, May 20, 2015 at 11:16 PM, Indika Sampath indi...@wso2.com
wrote:
I looked into master-datasources.xml and there are two RDBMS
datasources configured for WSO2MBStoreDB (H2 and MySQL). H2 is default
database we distributed with MB pack. Please comment it [1] before you
configure any other RDBMS datasource.
!-- WSO2 MB embedded H2 Store --
datasource
nameWSO2_MB_STORE_DB/name
descriptionThe datasource used for message broker
database/description
jndiConfig
nameWSO2MBStoreDB/name
/jndiConfig
definition type=RDBMS
configuration
urljdbc:h2:repository/database/WSO2MB_DB;DB_CLOSE_ON_EXIT=FALSE;LOCK_TIMEOUT=6/url
driverClassNameorg.h2.Driver/driverClassName
maxActive50/maxActive
maxWait6/maxWait
testOnBorrowtrue/testOnBorrow
validationQuerySELECT 1/validationQuery
validationInterval3/validationInterval
/configuration
/definition
/datasource
Cheers!
On Thu, May 21, 2015 at 8:33 AM, Amalka Subasinghe ama...@wso2.com
wrote:
attached broker.xml and master-datasources.xml files
On Wed, May 20, 2015 at 11:31 PM, Hemika Kodikara hem...@wso2.com
wrote:
Hi Amalka,
Can you attach the broker.xml file and master-datasources.xml
files ?
Regards,
Hemika
Hemika Kodikara
Software Engineer
WSO2 Inc.
lean . enterprise . middleware
http://wso2.com
Mobile : +9477762
On Wed, May 20, 2015 at 10:54 PM, Amalka Subasinghe
ama...@wso2.com wrote:
I'm using M7 pack. but I have to create the databases manually.
On Wed, May 20, 2015 at 10:51 PM, Indika Sampath
indi...@wso2.com wrote:
Hi Amalka,
You don't need to externally run db script. Below set of tables
created when you start
Re: [Dev] [MB] Error while starting MB 3.0.0 cluster setup
Thanks Krishantha and Hemika. I will try that out
On Fri, May 22, 2015 at 10:45 AM, Hemika Kodikara hem...@wso2.com wrote:
Hi Asitha,
Cant we use the serverManager.applyConfiguration() method to apply a
master-datasources.xml file as well along with the broker.xml ?
Here, the master-datasources.xml file will have H2-InMemory uncommented.
Regards,
Hemika
Hemika Kodikara
Software Engineer
WSO2 Inc.
lean . enterprise . middleware
http://wso2.com
Mobile : +9477762
On Fri, May 22, 2015 at 10:40 AM, Krishantha Samaraweera
krishan...@wso2.com wrote:
You can use applyConfigurationWithoutRestart() method in
ServerConfigurationManager class.
After applying all configuration call restartGracefully() method in the
same class.
Thanks,
Krishantha.
On Fri, May 22, 2015 at 9:28 AM, Asitha Nanayakkara asi...@wso2.com
wrote:
Commenting out in-memory mode by default led to automation test failure
[1] since server couldn't start in in-memory mode without the in-memory
datasource set
For in-memory mode related test we are restarting the server with a
broker.xml file configured to start the server in in-memory mode. We assume
master-datasources.xml in-memory mode configuration is set. But if we
comment it out we need to find a way to activate it again when the server
restarts for in-memory mode tests.
@Krishantha Is there a way to restart a server with changes to multiple
configuration files. Currently we only change the broker.xml [2]
* Restart the testing MB server in In-Memory H2 database mode by
applying In-Memory database configurations * in
andes-virtualhosts-H2-mem.xml file. * * @throws Exception */ protected
void restartServerWithH2MemMode() throws Exception { serverManager = new
ServerConfigurationManager(automationContext); // Replace the
broker.xml with the new configuration and restarts the server.
serverManager.applyConfiguration(new
File(FrameworkPathUtil.getSystemResourceLocation()
+ File.separator + artifacts + File.separator + mb + File.separator
+ config + File.separator + broker.xml), new File(
ServerConfigurationManager.getCarbonHome() + File.separator +
repository + File.separator + conf + File.separator + broker.xml),
true, true); }
[1] https://wso2.org/jenkins/job/product-mb/424/console
[2]
https://github.com/wso2/product-mb/blob/master/modules/integration/tests-common/integration-tests-utils/src/main/java/org/wso2/mb/integration/common/utils/backend/MBIntegrationBaseTest.java#L63
Thanks,
Asitha
On Thu, May 21, 2015 at 10:44 AM, Asitha Nanayakkara asi...@wso2.com
wrote:
Hi all,
I've commented out H2 In-memory store by default with PR [1]
[1] https://github.com/wso2/product-mb/pull/102
On Thu, May 21, 2015 at 10:29 AM, Ramith Jayasinghe ram...@wso2.com
wrote:
+1
On Thu, May 21, 2015 at 10:26 AM, Hemika Kodikara hem...@wso2.com
wrote:
Also I think we should comment out the H2-In Memory store by default.
WDYT ?
Hemika Kodikara
Software Engineer
WSO2 Inc.
lean . enterprise . middleware
http://wso2.com
Mobile : +9477762
On Thu, May 21, 2015 at 10:22 AM, Hasitha Hiranya hasit...@wso2.com
wrote:
Better to highlight this in our docs as well.
On Wed, May 20, 2015 at 11:16 PM, Indika Sampath indi...@wso2.com
wrote:
I looked into master-datasources.xml and there are two RDBMS
datasources configured for WSO2MBStoreDB (H2 and MySQL). H2 is default
database we distributed with MB pack. Please comment it [1] before you
configure any other RDBMS datasource.
!-- WSO2 MB embedded H2 Store --
datasource
nameWSO2_MB_STORE_DB/name
descriptionThe datasource used for message broker
database/description
jndiConfig
nameWSO2MBStoreDB/name
/jndiConfig
definition type=RDBMS
configuration
urljdbc:h2:repository/database/WSO2MB_DB;DB_CLOSE_ON_EXIT=FALSE;LOCK_TIMEOUT=6/url
driverClassNameorg.h2.Driver/driverClassName
maxActive50/maxActive
maxWait6/maxWait
testOnBorrowtrue/testOnBorrow
validationQuerySELECT 1/validationQuery
validationInterval3/validationInterval
/configuration
/definition
/datasource
Cheers!
On Thu, May 21, 2015 at 8:33 AM, Amalka Subasinghe ama...@wso2.com
wrote:
attached broker.xml and master-datasources.xml files
On Wed, May 20, 2015 at 11:31 PM, Hemika Kodikara hem...@wso2.com
wrote:
Hi Amalka,
Can you attach the broker.xml file and master-datasources.xml
files ?
Regards,
Hemika
Hemika Kodikara
Software Engineer
WSO2 Inc.
lean . enterprise . middleware
http://wso2.com
Mobile : +9477762
On Wed, May 20, 2015 at 10:54 PM, Amalka Subasinghe
ama...@wso2.com wrote:
I'm using M7 pack. but I have to create the databases manually.
On Wed, May 20, 2015 at 10:51 PM,
Re: [Dev] [MB] Error while starting MB 3.0.0 cluster setup
I'm using M7 pack. but I have to create the databases manually.
On Wed, May 20, 2015 at 10:51 PM, Indika Sampath indi...@wso2.com wrote:
Hi Amalka,
You don't need to externally run db script. Below set of tables created
when you start MB 3.0.0 pack with -Dsetup option. Which milestone pack did
you configure ?
MB_BINDING
MB_CONTENT
MB_DURABLE_SUBSCRIPTION
MB_EXCHANGE
MB_EXPIRATION_DATA
MB_METADATA
MB_NODE
MB_QUEUE
MB_QUEUE_COUNTER
MB_QUEUE_MAPPING
Cheers!
On Wed, May 20, 2015 at 10:14 PM, Amalka Subasinghe ama...@wso2.com
wrote:
Hi,
I'm trying to setup MB cluster with 2 MB nodes. When I start the MB node
with -Dsetup following error was thrown.
Do I need to create tables manually for wso2_mb (MB store db)?
2015-05-20 22:01:04,676] ERROR
{org.wso2.andes.server.registry.ApplicationRegistry} -
org.wso2.andes.kernel.AndesException: Error occurred while retrieving all
queue information.
Exception during startup: java.lang.Exception:
org.wso2.andes.kernel.AndesException: Error occurred while retrieving all
queue information.
java.lang.Exception: org.wso2.andes.kernel.AndesException: Error occurred
while retrieving all queue information.
at
org.wso2.andes.server.registry.ApplicationRegistry.initialise(ApplicationRegistry.java:266)
at
org.wso2.andes.server.registry.ApplicationRegistry.initialise(ApplicationRegistry.java:147)
at org.wso2.andes.server.Broker.startupImpl(Broker.java:147)
at org.wso2.andes.server.Broker.startup(Broker.java:108)
at org.wso2.andes.server.Main.startBroker(Main.java:218)
at org.wso2.andes.server.Main.execute(Main.java:207)
at org.wso2.andes.server.Main.init(Main.java:48)
at org.wso2.andes.server.Main.main(Main.java:41)
at
org.wso2.carbon.andes.internal.QpidServiceComponent.startAndesBroker(QpidServiceComponent.java:324)
at
org.wso2.carbon.andes.internal.QpidServiceComponent.setHazelcastInstance(QpidServiceComponent.java:226)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.eclipse.equinox.internal.ds.model.ComponentReference.bind(ComponentReference.java:376)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.bindReference(ServiceComponentProp.java:432)
at
org.eclipse.equinox.internal.ds.InstanceProcess.dynamicBind(InstanceProcess.java:416)
at
org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:334)
at
org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at
org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:451)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:950)
at
org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent.init(HazelcastClusteringAgent.java:223)
at
org.wso2.carbon.core.util.ClusteringUtil.enableClustering(ClusteringUtil.java:38)
at
org.wso2.carbon.core.internal.StartupFinalizerServiceComponent.completeInitialization(StartupFinalizerServiceComponent.java:174)
at
org.wso2.carbon.core.internal.StartupFinalizerServiceComponent.serviceChanged(StartupFinalizerServiceComponent.java:285)
at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at
org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
at
Re: [Dev] [MB] Error while starting MB 3.0.0 cluster setup
Hi Amalka,
You don't need to externally run db script. Below set of tables created
when you start MB 3.0.0 pack with -Dsetup option. Which milestone pack did
you configure ?
MB_BINDING
MB_CONTENT
MB_DURABLE_SUBSCRIPTION
MB_EXCHANGE
MB_EXPIRATION_DATA
MB_METADATA
MB_NODE
MB_QUEUE
MB_QUEUE_COUNTER
MB_QUEUE_MAPPING
Cheers!
On Wed, May 20, 2015 at 10:14 PM, Amalka Subasinghe ama...@wso2.com wrote:
Hi,
I'm trying to setup MB cluster with 2 MB nodes. When I start the MB node
with -Dsetup following error was thrown.
Do I need to create tables manually for wso2_mb (MB store db)?
2015-05-20 22:01:04,676] ERROR
{org.wso2.andes.server.registry.ApplicationRegistry} -
org.wso2.andes.kernel.AndesException: Error occurred while retrieving all
queue information.
Exception during startup: java.lang.Exception:
org.wso2.andes.kernel.AndesException: Error occurred while retrieving all
queue information.
java.lang.Exception: org.wso2.andes.kernel.AndesException: Error occurred
while retrieving all queue information.
at
org.wso2.andes.server.registry.ApplicationRegistry.initialise(ApplicationRegistry.java:266)
at
org.wso2.andes.server.registry.ApplicationRegistry.initialise(ApplicationRegistry.java:147)
at org.wso2.andes.server.Broker.startupImpl(Broker.java:147)
at org.wso2.andes.server.Broker.startup(Broker.java:108)
at org.wso2.andes.server.Main.startBroker(Main.java:218)
at org.wso2.andes.server.Main.execute(Main.java:207)
at org.wso2.andes.server.Main.init(Main.java:48)
at org.wso2.andes.server.Main.main(Main.java:41)
at
org.wso2.carbon.andes.internal.QpidServiceComponent.startAndesBroker(QpidServiceComponent.java:324)
at
org.wso2.carbon.andes.internal.QpidServiceComponent.setHazelcastInstance(QpidServiceComponent.java:226)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.eclipse.equinox.internal.ds.model.ComponentReference.bind(ComponentReference.java:376)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.bindReference(ServiceComponentProp.java:432)
at
org.eclipse.equinox.internal.ds.InstanceProcess.dynamicBind(InstanceProcess.java:416)
at
org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:334)
at
org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at
org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:451)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:950)
at
org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent.init(HazelcastClusteringAgent.java:223)
at
org.wso2.carbon.core.util.ClusteringUtil.enableClustering(ClusteringUtil.java:38)
at
org.wso2.carbon.core.internal.StartupFinalizerServiceComponent.completeInitialization(StartupFinalizerServiceComponent.java:174)
at
org.wso2.carbon.core.internal.StartupFinalizerServiceComponent.serviceChanged(StartupFinalizerServiceComponent.java:285)
at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at
org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
at
Re: [Dev] [MB] Error while starting MB 3.0.0 cluster setup
Hi Amalka,
Can you attach the broker.xml file and master-datasources.xml files ?
Regards,
Hemika
Hemika Kodikara
Software Engineer
WSO2 Inc.
lean . enterprise . middleware
http://wso2.com
Mobile : +9477762
On Wed, May 20, 2015 at 10:54 PM, Amalka Subasinghe ama...@wso2.com wrote:
I'm using M7 pack. but I have to create the databases manually.
On Wed, May 20, 2015 at 10:51 PM, Indika Sampath indi...@wso2.com wrote:
Hi Amalka,
You don't need to externally run db script. Below set of tables created
when you start MB 3.0.0 pack with -Dsetup option. Which milestone pack did
you configure ?
MB_BINDING
MB_CONTENT
MB_DURABLE_SUBSCRIPTION
MB_EXCHANGE
MB_EXPIRATION_DATA
MB_METADATA
MB_NODE
MB_QUEUE
MB_QUEUE_COUNTER
MB_QUEUE_MAPPING
Cheers!
On Wed, May 20, 2015 at 10:14 PM, Amalka Subasinghe ama...@wso2.com
wrote:
Hi,
I'm trying to setup MB cluster with 2 MB nodes. When I start the MB node
with -Dsetup following error was thrown.
Do I need to create tables manually for wso2_mb (MB store db)?
2015-05-20 22:01:04,676] ERROR
{org.wso2.andes.server.registry.ApplicationRegistry} -
org.wso2.andes.kernel.AndesException: Error occurred while retrieving all
queue information.
Exception during startup: java.lang.Exception:
org.wso2.andes.kernel.AndesException: Error occurred while retrieving all
queue information.
java.lang.Exception: org.wso2.andes.kernel.AndesException: Error
occurred while retrieving all queue information.
at
org.wso2.andes.server.registry.ApplicationRegistry.initialise(ApplicationRegistry.java:266)
at
org.wso2.andes.server.registry.ApplicationRegistry.initialise(ApplicationRegistry.java:147)
at org.wso2.andes.server.Broker.startupImpl(Broker.java:147)
at org.wso2.andes.server.Broker.startup(Broker.java:108)
at org.wso2.andes.server.Main.startBroker(Main.java:218)
at org.wso2.andes.server.Main.execute(Main.java:207)
at org.wso2.andes.server.Main.init(Main.java:48)
at org.wso2.andes.server.Main.main(Main.java:41)
at
org.wso2.carbon.andes.internal.QpidServiceComponent.startAndesBroker(QpidServiceComponent.java:324)
at
org.wso2.carbon.andes.internal.QpidServiceComponent.setHazelcastInstance(QpidServiceComponent.java:226)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.eclipse.equinox.internal.ds.model.ComponentReference.bind(ComponentReference.java:376)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.bindReference(ServiceComponentProp.java:432)
at
org.eclipse.equinox.internal.ds.InstanceProcess.dynamicBind(InstanceProcess.java:416)
at
org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:334)
at
org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at
org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:451)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:950)
at
org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent.init(HazelcastClusteringAgent.java:223)
at
org.wso2.carbon.core.util.ClusteringUtil.enableClustering(ClusteringUtil.java:38)
at
org.wso2.carbon.core.internal.StartupFinalizerServiceComponent.completeInitialization(StartupFinalizerServiceComponent.java:174)
at
org.wso2.carbon.core.internal.StartupFinalizerServiceComponent.serviceChanged(StartupFinalizerServiceComponent.java:285)
at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
at
Re: [Dev] [MB] Error while starting MB 3.0.0 cluster setup
+1
On Thu, May 21, 2015 at 10:26 AM, Hemika Kodikara hem...@wso2.com wrote:
Also I think we should comment out the H2-In Memory store by default. WDYT
?
Hemika Kodikara
Software Engineer
WSO2 Inc.
lean . enterprise . middleware
http://wso2.com
Mobile : +9477762
On Thu, May 21, 2015 at 10:22 AM, Hasitha Hiranya hasit...@wso2.com
wrote:
Better to highlight this in our docs as well.
On Wed, May 20, 2015 at 11:16 PM, Indika Sampath indi...@wso2.com
wrote:
I looked into master-datasources.xml and there are two RDBMS datasources
configured for WSO2MBStoreDB (H2 and MySQL). H2 is default database we
distributed with MB pack. Please comment it [1] before you configure any
other RDBMS datasource.
!-- WSO2 MB embedded H2 Store --
datasource
nameWSO2_MB_STORE_DB/name
descriptionThe datasource used for message broker
database/description
jndiConfig
nameWSO2MBStoreDB/name
/jndiConfig
definition type=RDBMS
configuration
urljdbc:h2:repository/database/WSO2MB_DB;DB_CLOSE_ON_EXIT=FALSE;LOCK_TIMEOUT=6/url
driverClassNameorg.h2.Driver/driverClassName
maxActive50/maxActive
maxWait6/maxWait
testOnBorrowtrue/testOnBorrow
validationQuerySELECT 1/validationQuery
validationInterval3/validationInterval
/configuration
/definition
/datasource
Cheers!
On Thu, May 21, 2015 at 8:33 AM, Amalka Subasinghe ama...@wso2.com
wrote:
attached broker.xml and master-datasources.xml files
On Wed, May 20, 2015 at 11:31 PM, Hemika Kodikara hem...@wso2.com
wrote:
Hi Amalka,
Can you attach the broker.xml file and master-datasources.xml files ?
Regards,
Hemika
Hemika Kodikara
Software Engineer
WSO2 Inc.
lean . enterprise . middleware
http://wso2.com
Mobile : +9477762
On Wed, May 20, 2015 at 10:54 PM, Amalka Subasinghe ama...@wso2.com
wrote:
I'm using M7 pack. but I have to create the databases manually.
On Wed, May 20, 2015 at 10:51 PM, Indika Sampath indi...@wso2.com
wrote:
Hi Amalka,
You don't need to externally run db script. Below set of tables
created when you start MB 3.0.0 pack with -Dsetup option. Which
milestone
pack did you configure ?
MB_BINDING
MB_CONTENT
MB_DURABLE_SUBSCRIPTION
MB_EXCHANGE
MB_EXPIRATION_DATA
MB_METADATA
MB_NODE
MB_QUEUE
MB_QUEUE_COUNTER
MB_QUEUE_MAPPING
Cheers!
On Wed, May 20, 2015 at 10:14 PM, Amalka Subasinghe ama...@wso2.com
wrote:
Hi,
I'm trying to setup MB cluster with 2 MB nodes. When I start the MB
node with -Dsetup following error was thrown.
Do I need to create tables manually for wso2_mb (MB store db)?
2015-05-20 22:01:04,676] ERROR
{org.wso2.andes.server.registry.ApplicationRegistry} -
org.wso2.andes.kernel.AndesException: Error occurred while retrieving
all
queue information.
Exception during startup: java.lang.Exception:
org.wso2.andes.kernel.AndesException: Error occurred while retrieving
all
queue information.
java.lang.Exception: org.wso2.andes.kernel.AndesException: Error
occurred while retrieving all queue information.
at
org.wso2.andes.server.registry.ApplicationRegistry.initialise(ApplicationRegistry.java:266)
at
org.wso2.andes.server.registry.ApplicationRegistry.initialise(ApplicationRegistry.java:147)
at org.wso2.andes.server.Broker.startupImpl(Broker.java:147)
at org.wso2.andes.server.Broker.startup(Broker.java:108)
at org.wso2.andes.server.Main.startBroker(Main.java:218)
at org.wso2.andes.server.Main.execute(Main.java:207)
at org.wso2.andes.server.Main.init(Main.java:48)
at org.wso2.andes.server.Main.main(Main.java:41)
at
org.wso2.carbon.andes.internal.QpidServiceComponent.startAndesBroker(QpidServiceComponent.java:324)
at
org.wso2.carbon.andes.internal.QpidServiceComponent.setHazelcastInstance(QpidServiceComponent.java:226)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.eclipse.equinox.internal.ds.model.ComponentReference.bind(ComponentReference.java:376)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.bindReference(ServiceComponentProp.java:432)
at
org.eclipse.equinox.internal.ds.InstanceProcess.dynamicBind(InstanceProcess.java:416)
at
org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:334)
at
org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
at
Re: [Dev] [MB] Error while starting MB 3.0.0 cluster setup
Also I think we should comment out the H2-In Memory store by default. WDYT ?
Hemika Kodikara
Software Engineer
WSO2 Inc.
lean . enterprise . middleware
http://wso2.com
Mobile : +9477762
On Thu, May 21, 2015 at 10:22 AM, Hasitha Hiranya hasit...@wso2.com wrote:
Better to highlight this in our docs as well.
On Wed, May 20, 2015 at 11:16 PM, Indika Sampath indi...@wso2.com wrote:
I looked into master-datasources.xml and there are two RDBMS datasources
configured for WSO2MBStoreDB (H2 and MySQL). H2 is default database we
distributed with MB pack. Please comment it [1] before you configure any
other RDBMS datasource.
!-- WSO2 MB embedded H2 Store --
datasource
nameWSO2_MB_STORE_DB/name
descriptionThe datasource used for message broker
database/description
jndiConfig
nameWSO2MBStoreDB/name
/jndiConfig
definition type=RDBMS
configuration
urljdbc:h2:repository/database/WSO2MB_DB;DB_CLOSE_ON_EXIT=FALSE;LOCK_TIMEOUT=6/url
driverClassNameorg.h2.Driver/driverClassName
maxActive50/maxActive
maxWait6/maxWait
testOnBorrowtrue/testOnBorrow
validationQuerySELECT 1/validationQuery
validationInterval3/validationInterval
/configuration
/definition
/datasource
Cheers!
On Thu, May 21, 2015 at 8:33 AM, Amalka Subasinghe ama...@wso2.com
wrote:
attached broker.xml and master-datasources.xml files
On Wed, May 20, 2015 at 11:31 PM, Hemika Kodikara hem...@wso2.com
wrote:
Hi Amalka,
Can you attach the broker.xml file and master-datasources.xml files ?
Regards,
Hemika
Hemika Kodikara
Software Engineer
WSO2 Inc.
lean . enterprise . middleware
http://wso2.com
Mobile : +9477762
On Wed, May 20, 2015 at 10:54 PM, Amalka Subasinghe ama...@wso2.com
wrote:
I'm using M7 pack. but I have to create the databases manually.
On Wed, May 20, 2015 at 10:51 PM, Indika Sampath indi...@wso2.com
wrote:
Hi Amalka,
You don't need to externally run db script. Below set of tables
created when you start MB 3.0.0 pack with -Dsetup option. Which milestone
pack did you configure ?
MB_BINDING
MB_CONTENT
MB_DURABLE_SUBSCRIPTION
MB_EXCHANGE
MB_EXPIRATION_DATA
MB_METADATA
MB_NODE
MB_QUEUE
MB_QUEUE_COUNTER
MB_QUEUE_MAPPING
Cheers!
On Wed, May 20, 2015 at 10:14 PM, Amalka Subasinghe ama...@wso2.com
wrote:
Hi,
I'm trying to setup MB cluster with 2 MB nodes. When I start the MB
node with -Dsetup following error was thrown.
Do I need to create tables manually for wso2_mb (MB store db)?
2015-05-20 22:01:04,676] ERROR
{org.wso2.andes.server.registry.ApplicationRegistry} -
org.wso2.andes.kernel.AndesException: Error occurred while retrieving
all
queue information.
Exception during startup: java.lang.Exception:
org.wso2.andes.kernel.AndesException: Error occurred while retrieving
all
queue information.
java.lang.Exception: org.wso2.andes.kernel.AndesException: Error
occurred while retrieving all queue information.
at
org.wso2.andes.server.registry.ApplicationRegistry.initialise(ApplicationRegistry.java:266)
at
org.wso2.andes.server.registry.ApplicationRegistry.initialise(ApplicationRegistry.java:147)
at org.wso2.andes.server.Broker.startupImpl(Broker.java:147)
at org.wso2.andes.server.Broker.startup(Broker.java:108)
at org.wso2.andes.server.Main.startBroker(Main.java:218)
at org.wso2.andes.server.Main.execute(Main.java:207)
at org.wso2.andes.server.Main.init(Main.java:48)
at org.wso2.andes.server.Main.main(Main.java:41)
at
org.wso2.carbon.andes.internal.QpidServiceComponent.startAndesBroker(QpidServiceComponent.java:324)
at
org.wso2.carbon.andes.internal.QpidServiceComponent.setHazelcastInstance(QpidServiceComponent.java:226)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.eclipse.equinox.internal.ds.model.ComponentReference.bind(ComponentReference.java:376)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.bindReference(ServiceComponentProp.java:432)
at
org.eclipse.equinox.internal.ds.InstanceProcess.dynamicBind(InstanceProcess.java:416)
at
org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:334)
at
org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
Re: [Dev] [MB] Error while starting MB 3.0.0 cluster setup
Hi all,
I've commented out H2 In-memory store by default with PR [1]
[1] https://github.com/wso2/product-mb/pull/102
On Thu, May 21, 2015 at 10:29 AM, Ramith Jayasinghe ram...@wso2.com wrote:
+1
On Thu, May 21, 2015 at 10:26 AM, Hemika Kodikara hem...@wso2.com wrote:
Also I think we should comment out the H2-In Memory store by default.
WDYT ?
Hemika Kodikara
Software Engineer
WSO2 Inc.
lean . enterprise . middleware
http://wso2.com
Mobile : +9477762
On Thu, May 21, 2015 at 10:22 AM, Hasitha Hiranya hasit...@wso2.com
wrote:
Better to highlight this in our docs as well.
On Wed, May 20, 2015 at 11:16 PM, Indika Sampath indi...@wso2.com
wrote:
I looked into master-datasources.xml and there are two RDBMS
datasources configured for WSO2MBStoreDB (H2 and MySQL). H2 is default
database we distributed with MB pack. Please comment it [1] before you
configure any other RDBMS datasource.
!-- WSO2 MB embedded H2 Store --
datasource
nameWSO2_MB_STORE_DB/name
descriptionThe datasource used for message broker
database/description
jndiConfig
nameWSO2MBStoreDB/name
/jndiConfig
definition type=RDBMS
configuration
urljdbc:h2:repository/database/WSO2MB_DB;DB_CLOSE_ON_EXIT=FALSE;LOCK_TIMEOUT=6/url
driverClassNameorg.h2.Driver/driverClassName
maxActive50/maxActive
maxWait6/maxWait
testOnBorrowtrue/testOnBorrow
validationQuerySELECT 1/validationQuery
validationInterval3/validationInterval
/configuration
/definition
/datasource
Cheers!
On Thu, May 21, 2015 at 8:33 AM, Amalka Subasinghe ama...@wso2.com
wrote:
attached broker.xml and master-datasources.xml files
On Wed, May 20, 2015 at 11:31 PM, Hemika Kodikara hem...@wso2.com
wrote:
Hi Amalka,
Can you attach the broker.xml file and master-datasources.xml files ?
Regards,
Hemika
Hemika Kodikara
Software Engineer
WSO2 Inc.
lean . enterprise . middleware
http://wso2.com
Mobile : +9477762
On Wed, May 20, 2015 at 10:54 PM, Amalka Subasinghe ama...@wso2.com
wrote:
I'm using M7 pack. but I have to create the databases manually.
On Wed, May 20, 2015 at 10:51 PM, Indika Sampath indi...@wso2.com
wrote:
Hi Amalka,
You don't need to externally run db script. Below set of tables
created when you start MB 3.0.0 pack with -Dsetup option. Which
milestone
pack did you configure ?
MB_BINDING
MB_CONTENT
MB_DURABLE_SUBSCRIPTION
MB_EXCHANGE
MB_EXPIRATION_DATA
MB_METADATA
MB_NODE
MB_QUEUE
MB_QUEUE_COUNTER
MB_QUEUE_MAPPING
Cheers!
On Wed, May 20, 2015 at 10:14 PM, Amalka Subasinghe
ama...@wso2.com wrote:
Hi,
I'm trying to setup MB cluster with 2 MB nodes. When I start the
MB node with -Dsetup following error was thrown.
Do I need to create tables manually for wso2_mb (MB store db)?
2015-05-20 22:01:04,676] ERROR
{org.wso2.andes.server.registry.ApplicationRegistry} -
org.wso2.andes.kernel.AndesException: Error occurred while retrieving
all
queue information.
Exception during startup: java.lang.Exception:
org.wso2.andes.kernel.AndesException: Error occurred while retrieving
all
queue information.
java.lang.Exception: org.wso2.andes.kernel.AndesException: Error
occurred while retrieving all queue information.
at
org.wso2.andes.server.registry.ApplicationRegistry.initialise(ApplicationRegistry.java:266)
at
org.wso2.andes.server.registry.ApplicationRegistry.initialise(ApplicationRegistry.java:147)
at org.wso2.andes.server.Broker.startupImpl(Broker.java:147)
at org.wso2.andes.server.Broker.startup(Broker.java:108)
at org.wso2.andes.server.Main.startBroker(Main.java:218)
at org.wso2.andes.server.Main.execute(Main.java:207)
at org.wso2.andes.server.Main.init(Main.java:48)
at org.wso2.andes.server.Main.main(Main.java:41)
at
org.wso2.carbon.andes.internal.QpidServiceComponent.startAndesBroker(QpidServiceComponent.java:324)
at
org.wso2.carbon.andes.internal.QpidServiceComponent.setHazelcastInstance(QpidServiceComponent.java:226)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.eclipse.equinox.internal.ds.model.ComponentReference.bind(ComponentReference.java:376)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.bindReference(ServiceComponentProp.java:432)
at
org.eclipse.equinox.internal.ds.InstanceProcess.dynamicBind(InstanceProcess.java:416)
at
org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:334)
at
Re: [Dev] [MB] Error while starting MB 3.0.0 cluster setup
attached broker.xml and master-datasources.xml files
On Wed, May 20, 2015 at 11:31 PM, Hemika Kodikara hem...@wso2.com wrote:
Hi Amalka,
Can you attach the broker.xml file and master-datasources.xml files ?
Regards,
Hemika
Hemika Kodikara
Software Engineer
WSO2 Inc.
lean . enterprise . middleware
http://wso2.com
Mobile : +9477762
On Wed, May 20, 2015 at 10:54 PM, Amalka Subasinghe ama...@wso2.com
wrote:
I'm using M7 pack. but I have to create the databases manually.
On Wed, May 20, 2015 at 10:51 PM, Indika Sampath indi...@wso2.com
wrote:
Hi Amalka,
You don't need to externally run db script. Below set of tables created
when you start MB 3.0.0 pack with -Dsetup option. Which milestone pack did
you configure ?
MB_BINDING
MB_CONTENT
MB_DURABLE_SUBSCRIPTION
MB_EXCHANGE
MB_EXPIRATION_DATA
MB_METADATA
MB_NODE
MB_QUEUE
MB_QUEUE_COUNTER
MB_QUEUE_MAPPING
Cheers!
On Wed, May 20, 2015 at 10:14 PM, Amalka Subasinghe ama...@wso2.com
wrote:
Hi,
I'm trying to setup MB cluster with 2 MB nodes. When I start the MB
node with -Dsetup following error was thrown.
Do I need to create tables manually for wso2_mb (MB store db)?
2015-05-20 22:01:04,676] ERROR
{org.wso2.andes.server.registry.ApplicationRegistry} -
org.wso2.andes.kernel.AndesException: Error occurred while retrieving all
queue information.
Exception during startup: java.lang.Exception:
org.wso2.andes.kernel.AndesException: Error occurred while retrieving all
queue information.
java.lang.Exception: org.wso2.andes.kernel.AndesException: Error
occurred while retrieving all queue information.
at
org.wso2.andes.server.registry.ApplicationRegistry.initialise(ApplicationRegistry.java:266)
at
org.wso2.andes.server.registry.ApplicationRegistry.initialise(ApplicationRegistry.java:147)
at org.wso2.andes.server.Broker.startupImpl(Broker.java:147)
at org.wso2.andes.server.Broker.startup(Broker.java:108)
at org.wso2.andes.server.Main.startBroker(Main.java:218)
at org.wso2.andes.server.Main.execute(Main.java:207)
at org.wso2.andes.server.Main.init(Main.java:48)
at org.wso2.andes.server.Main.main(Main.java:41)
at
org.wso2.carbon.andes.internal.QpidServiceComponent.startAndesBroker(QpidServiceComponent.java:324)
at
org.wso2.carbon.andes.internal.QpidServiceComponent.setHazelcastInstance(QpidServiceComponent.java:226)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.eclipse.equinox.internal.ds.model.ComponentReference.bind(ComponentReference.java:376)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.bindReference(ServiceComponentProp.java:432)
at
org.eclipse.equinox.internal.ds.InstanceProcess.dynamicBind(InstanceProcess.java:416)
at
org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:334)
at
org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at
org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:451)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:950)
at
org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent.init(HazelcastClusteringAgent.java:223)
at
org.wso2.carbon.core.util.ClusteringUtil.enableClustering(ClusteringUtil.java:38)
at
org.wso2.carbon.core.internal.StartupFinalizerServiceComponent.completeInitialization(StartupFinalizerServiceComponent.java:174)
at
org.wso2.carbon.core.internal.StartupFinalizerServiceComponent.serviceChanged(StartupFinalizerServiceComponent.java:285)
at
Re: [Dev] [MB] Error while starting MB 3.0.0 cluster setup
I looked into master-datasources.xml and there are two RDBMS datasources
configured for WSO2MBStoreDB (H2 and MySQL). H2 is default database we
distributed with MB pack. Please comment it [1] before you configure any
other RDBMS datasource.
!-- WSO2 MB embedded H2 Store --
datasource
nameWSO2_MB_STORE_DB/name
descriptionThe datasource used for message broker
database/description
jndiConfig
nameWSO2MBStoreDB/name
/jndiConfig
definition type=RDBMS
configuration
urljdbc:h2:repository/database/WSO2MB_DB;DB_CLOSE_ON_EXIT=FALSE;LOCK_TIMEOUT=6/url
driverClassNameorg.h2.Driver/driverClassName
maxActive50/maxActive
maxWait6/maxWait
testOnBorrowtrue/testOnBorrow
validationQuerySELECT 1/validationQuery
validationInterval3/validationInterval
/configuration
/definition
/datasource
Cheers!
On Thu, May 21, 2015 at 8:33 AM, Amalka Subasinghe ama...@wso2.com wrote:
attached broker.xml and master-datasources.xml files
On Wed, May 20, 2015 at 11:31 PM, Hemika Kodikara hem...@wso2.com wrote:
Hi Amalka,
Can you attach the broker.xml file and master-datasources.xml files ?
Regards,
Hemika
Hemika Kodikara
Software Engineer
WSO2 Inc.
lean . enterprise . middleware
http://wso2.com
Mobile : +9477762
On Wed, May 20, 2015 at 10:54 PM, Amalka Subasinghe ama...@wso2.com
wrote:
I'm using M7 pack. but I have to create the databases manually.
On Wed, May 20, 2015 at 10:51 PM, Indika Sampath indi...@wso2.com
wrote:
Hi Amalka,
You don't need to externally run db script. Below set of tables created
when you start MB 3.0.0 pack with -Dsetup option. Which milestone pack did
you configure ?
MB_BINDING
MB_CONTENT
MB_DURABLE_SUBSCRIPTION
MB_EXCHANGE
MB_EXPIRATION_DATA
MB_METADATA
MB_NODE
MB_QUEUE
MB_QUEUE_COUNTER
MB_QUEUE_MAPPING
Cheers!
On Wed, May 20, 2015 at 10:14 PM, Amalka Subasinghe ama...@wso2.com
wrote:
Hi,
I'm trying to setup MB cluster with 2 MB nodes. When I start the MB
node with -Dsetup following error was thrown.
Do I need to create tables manually for wso2_mb (MB store db)?
2015-05-20 22:01:04,676] ERROR
{org.wso2.andes.server.registry.ApplicationRegistry} -
org.wso2.andes.kernel.AndesException: Error occurred while retrieving all
queue information.
Exception during startup: java.lang.Exception:
org.wso2.andes.kernel.AndesException: Error occurred while retrieving all
queue information.
java.lang.Exception: org.wso2.andes.kernel.AndesException: Error
occurred while retrieving all queue information.
at
org.wso2.andes.server.registry.ApplicationRegistry.initialise(ApplicationRegistry.java:266)
at
org.wso2.andes.server.registry.ApplicationRegistry.initialise(ApplicationRegistry.java:147)
at org.wso2.andes.server.Broker.startupImpl(Broker.java:147)
at org.wso2.andes.server.Broker.startup(Broker.java:108)
at org.wso2.andes.server.Main.startBroker(Main.java:218)
at org.wso2.andes.server.Main.execute(Main.java:207)
at org.wso2.andes.server.Main.init(Main.java:48)
at org.wso2.andes.server.Main.main(Main.java:41)
at
org.wso2.carbon.andes.internal.QpidServiceComponent.startAndesBroker(QpidServiceComponent.java:324)
at
org.wso2.carbon.andes.internal.QpidServiceComponent.setHazelcastInstance(QpidServiceComponent.java:226)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.eclipse.equinox.internal.ds.model.ComponentReference.bind(ComponentReference.java:376)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.bindReference(ServiceComponentProp.java:432)
at
org.eclipse.equinox.internal.ds.InstanceProcess.dynamicBind(InstanceProcess.java:416)
at
org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:334)
at
org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at
org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
at
Re: [Dev] [MB] Error while starting MB 3.0.0 cluster setup
Better to highlight this in our docs as well.
On Wed, May 20, 2015 at 11:16 PM, Indika Sampath indi...@wso2.com wrote:
I looked into master-datasources.xml and there are two RDBMS datasources
configured for WSO2MBStoreDB (H2 and MySQL). H2 is default database we
distributed with MB pack. Please comment it [1] before you configure any
other RDBMS datasource.
!-- WSO2 MB embedded H2 Store --
datasource
nameWSO2_MB_STORE_DB/name
descriptionThe datasource used for message broker
database/description
jndiConfig
nameWSO2MBStoreDB/name
/jndiConfig
definition type=RDBMS
configuration
urljdbc:h2:repository/database/WSO2MB_DB;DB_CLOSE_ON_EXIT=FALSE;LOCK_TIMEOUT=6/url
driverClassNameorg.h2.Driver/driverClassName
maxActive50/maxActive
maxWait6/maxWait
testOnBorrowtrue/testOnBorrow
validationQuerySELECT 1/validationQuery
validationInterval3/validationInterval
/configuration
/definition
/datasource
Cheers!
On Thu, May 21, 2015 at 8:33 AM, Amalka Subasinghe ama...@wso2.com
wrote:
attached broker.xml and master-datasources.xml files
On Wed, May 20, 2015 at 11:31 PM, Hemika Kodikara hem...@wso2.com
wrote:
Hi Amalka,
Can you attach the broker.xml file and master-datasources.xml files ?
Regards,
Hemika
Hemika Kodikara
Software Engineer
WSO2 Inc.
lean . enterprise . middleware
http://wso2.com
Mobile : +9477762
On Wed, May 20, 2015 at 10:54 PM, Amalka Subasinghe ama...@wso2.com
wrote:
I'm using M7 pack. but I have to create the databases manually.
On Wed, May 20, 2015 at 10:51 PM, Indika Sampath indi...@wso2.com
wrote:
Hi Amalka,
You don't need to externally run db script. Below set of tables
created when you start MB 3.0.0 pack with -Dsetup option. Which milestone
pack did you configure ?
MB_BINDING
MB_CONTENT
MB_DURABLE_SUBSCRIPTION
MB_EXCHANGE
MB_EXPIRATION_DATA
MB_METADATA
MB_NODE
MB_QUEUE
MB_QUEUE_COUNTER
MB_QUEUE_MAPPING
Cheers!
On Wed, May 20, 2015 at 10:14 PM, Amalka Subasinghe ama...@wso2.com
wrote:
Hi,
I'm trying to setup MB cluster with 2 MB nodes. When I start the MB
node with -Dsetup following error was thrown.
Do I need to create tables manually for wso2_mb (MB store db)?
2015-05-20 22:01:04,676] ERROR
{org.wso2.andes.server.registry.ApplicationRegistry} -
org.wso2.andes.kernel.AndesException: Error occurred while retrieving all
queue information.
Exception during startup: java.lang.Exception:
org.wso2.andes.kernel.AndesException: Error occurred while retrieving all
queue information.
java.lang.Exception: org.wso2.andes.kernel.AndesException: Error
occurred while retrieving all queue information.
at
org.wso2.andes.server.registry.ApplicationRegistry.initialise(ApplicationRegistry.java:266)
at
org.wso2.andes.server.registry.ApplicationRegistry.initialise(ApplicationRegistry.java:147)
at org.wso2.andes.server.Broker.startupImpl(Broker.java:147)
at org.wso2.andes.server.Broker.startup(Broker.java:108)
at org.wso2.andes.server.Main.startBroker(Main.java:218)
at org.wso2.andes.server.Main.execute(Main.java:207)
at org.wso2.andes.server.Main.init(Main.java:48)
at org.wso2.andes.server.Main.main(Main.java:41)
at
org.wso2.carbon.andes.internal.QpidServiceComponent.startAndesBroker(QpidServiceComponent.java:324)
at
org.wso2.carbon.andes.internal.QpidServiceComponent.setHazelcastInstance(QpidServiceComponent.java:226)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.eclipse.equinox.internal.ds.model.ComponentReference.bind(ComponentReference.java:376)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.bindReference(ServiceComponentProp.java:432)
at
org.eclipse.equinox.internal.ds.InstanceProcess.dynamicBind(InstanceProcess.java:416)
at
org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:334)
at
org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at
org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
at
