[
http://jira.amdatu.org/jira/browse/AMDATU-318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivo Ladage - van Doorn reopened AMDATU-318:
-------------------------------------------
After updating replication factor to 2 and restart of node 2, I get this error:
[2011-03-10 11:52:47] WARNING: Invocation of 'start' failed.
[org.amdatu.example.course.service]
null
java.lang.NullPointerException
at
org.amdatu.example.course.service.service.ProfileDataProvider.createTestPersons(ProfileDataProvider.java:83)
at
org.amdatu.example.course.service.service.ProfileDataProvider.start(ProfileDataProvider.java:51)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.felix.dm.InvocationUtil.invokeMethod(InvocationUtil.java:45)
at
org.apache.felix.dm.InvocationUtil.invokeCallbackMethod(InvocationUtil.java:13)
at
org.apache.felix.dm.impl.ComponentImpl.invokeCallbackMethod(ComponentImpl.java:684)
at org.apache.felix.dm.impl.ComponentImpl.invoke(ComponentImpl.java:675)
at
org.apache.felix.dm.impl.ComponentImpl.bindService(ComponentImpl.java:620)
at
org.apache.felix.dm.impl.ComponentImpl.access$400(ComponentImpl.java:52)
at org.apache.felix.dm.impl.ComponentImpl$7.run(ComponentImpl.java:178)
at org.apache.felix.dm.impl.SerialExecutor$1.run(SerialExecutor.java:47)
at
org.apache.felix.dm.impl.SerialExecutor.scheduleNext(SerialExecutor.java:84)
at
org.apache.felix.dm.impl.SerialExecutor.access$000(SerialExecutor.java:33)
at org.apache.felix.dm.impl.SerialExecutor$1.run(SerialExecutor.java:50)
at
org.apache.felix.dm.impl.SerialExecutor.scheduleNext(SerialExecutor.java:84)
at
org.apache.felix.dm.impl.SerialExecutor.access$000(SerialExecutor.java:33)
at org.apache.felix.dm.impl.SerialExecutor$1.run(SerialExecutor.java:50)
at
org.apache.felix.dm.impl.SerialExecutor.scheduleNext(SerialExecutor.java:84)
at
org.apache.felix.dm.impl.SerialExecutor.execute(SerialExecutor.java:68)
at
org.apache.felix.dm.impl.ComponentImpl.calculateStateChanges(ComponentImpl.java:228)
at org.apache.felix.dm.impl.ComponentImpl.start(ComponentImpl.java:406)
at org.apache.felix.dm.DependencyManager.add(DependencyManager.java:81)
at
org.amdatu.example.course.service.osgi.Activator.initWithDependencies(Activator.java:86)
at
org.amdatu.libraries.utilities.osgi.ServiceDependentActivator$SpiWatcher.start(ServiceDependentActivat
> Tombstones out of sync on node B in Cassandra cluster when they are removed
> from node A during downtime of node B
> -----------------------------------------------------------------------------------------------------------------
>
> Key: AMDATU-318
> URL: http://jira.amdatu.org/jira/browse/AMDATU-318
> Project: Amdatu
> Issue Type: Bug
> Components: Amdatu Cassandra
> Affects Versions: 0.2.0
> Reporter: Ivo Ladage - van Doorn
> Assignee: Ivo Ladage - van Doorn
> Fix For: 0.1.1
>
>
> First setup a Cassandra cluster as described in this use case:
> http://www.amdatu.org/confluence/display/Amdatu/Use+case+2
> Assume that node A is the seed (master) of node B.
> Now to reproduce:
> - Open dashboards of node A and B, login as Administrator and add UserAdmin
> gadget
> - Add a user '01' on node A (using UserAdmin gagdet), note that it appears on
> node B
> - Stop node B
> - Create another user '02' on node A
> - Remove user '01' on node A
> - Start node B
> Now note that user '02' is now available on node B, but also user '01' is
> still present, which should have been removed (upon Hinted handoff and read
> repair).
> Also tried removing the users using cassandra-cli instead, but the result is
> the same.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Amdatu-developers mailing list
[email protected]
http://lists.amdatu.org/mailman/listinfo/amdatu-developers
