Facing issue while Configuring MDB and MQ in jboss 7.1 - jboss

I was using jboss 6.4 before now i am migrating to jboss 7.1 and MQ 8, We have used jboss-ejb3.xml to configure MDBs and MQs, But after migrating to jboss 7.1 i am getting following error can some one please help me to resolve this problem
2019-02-11 12:13:03,739 INFO [org.apache.activemq.artemis.ra] AMQ151004: Instantiating null "TRANS.CMUPT.REQ.MCOF" directly since UseJNDI=false.
2019-02-11 12:13:05,614 INFO [org.jboss.as.connector.deployers.RaXmlDeployer] wmq.jmsra.rar: MQJCA4004:Message delivery to an MDB 'null' failed with exception: 'Could not initialize class com.ge.trans.mcs.msgejb.ejb.imr.mdb.InBoundMessageMDB$$$endpoint4'.
2019-02-11 12:13:05,762 INFO [org.apache.activemq.artemis.ra] AMQ151004: Instantiating null "TRANS.CMUPT.REQ.MCOF" directly since UseJNDI=false.
2019-02-11 12:13:07,785 INFO [org.apache.activemq.artemis.ra] AMQ151004: Instantiating null "TRANS.CMUPT.REQ.MCOF" directly since UseJNDI=false.
2019-02-11 12:13:09,815 INFO [org.apache.activemq.artemis.ra] AMQ151004: Instantiating null "TRANS.CMUPT.REQ.MCOF" directly since UseJNDI=false.
2019-02-11 12:13:11,836 INFO [org.apache.activemq.artemis.ra] AMQ151004: Instantiating null "TRANS.CMUPT.REQ.MCOF" directly since UseJNDI=false.
2019-02-11 12:13:13,854 INFO [org.apache.activemq.artemis.ra] AMQ151004: Instantiating null "TRANS.CMUPT.REQ.MCOF" directly since UseJNDI=false.
2019-02-11 12:13:15,605 INFO [org.jboss.as.connector.deployers.RaXmlDeployer] wmq.jmsra.rar: MQJCA4004:Message delivery to an MDB 'null' failed with exception: 'Could n
New logs
Seeing flowing issue
2019-02-12 12:37:17,736 INFO [org.jboss.as.connector.deployers.RaXmlDeployer] wmq.jmsra.rar: : com.ibm.msg.client.commonservices.workqueue.WorkQueueItem.run(WorkQueueItem.java:338)
2019-02-12 12:37:17,736 INFO [org.jboss.as.connector.deployers.RaXmlDeployer] wmq.jmsra.rar: : com.ibm.msg.client.commonservices.workqueue.WorkQueueManager.runWorkQueueItem(WorkQueueManager.java:312)
2019-02-12 12:37:17,736 INFO [org.jboss.as.connector.deployers.RaXmlDeployer] wmq.jmsra.rar: : com.ibm.msg.client.commonservices.j2se.workqueue.WorkQueueManagerImplementation$ThreadPoolWorker.run(WorkQueueManagerImplementation.java:1227)
2019-02-12 12:37:17,736 INFO [org.jboss.as.connector.deployers.RaXmlDeployer] wmq.jmsra.rar: Caused by [1] --> Message : com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2053' ('MQRC_Q_FULL').
2019-02-12 12:37:17,736 INFO [org.jboss.as.connector.deployers.RaXmlDeployer] wmq.jmsra.rar: Class : class com.ibm.mq.MQException
2019-02-12 12:37:17,736 INFO [org.jboss.as.connector.deployers.RaXmlDeployer] wmq.jmsra.rar: Stack : com.ibm.msg.client.wmq.common.internal.Reason.createException(Reason.java:203)
2019-02-12 12:37:17,736 INFO [org.jboss.as.connector.deployers.RaXmlDeployer] wmq.jmsra.rar: : com.ibm.msg.client.wmq.internal.WMQPoison.checkJmqiCallSuccess(WMQPoison.java:1423)
2019-02-12 12:37:17,736 INFO [org.jboss.as.connector.deployers.RaXmlDeployer] wmq.jmsra.rar: : com.ibm.msg.client.wmq.internal.WMQPoison.put(WMQPoison.java:984)
2019-02-12 12:37:17,736 INFO [org.jboss.as.connector.deployers.RaXmlDeployer] wmq.jmsra.rar: : com.ibm.msg.client.wmq.internal.WMQPoison.deadletter(WMQPoison.java:894)
This is the only error i am seeing now please help me to resolve this issue.
01:25:55,618 INFO [org.jboss.as.connector.deployers.RaXmlDeployer] (default-threads - 2) wmq.jmsra.rar: MQJCA4004:Message delivery to an MDB 'null' failed with exception: 'Could not initialize class com.ge.trans.mcs.msgejb.ejb.alerter.mdb.AlerterMDB$$$endpoint8'.

reason '2053' ('MQRC_Q_FULL') just means what it sounds like, the destination queue you are putting to is full, this means that it has reached the MAXDEPTH number of messages.
Could not initialize class com.ge.trans.mcs.msgejb.ejb.alerter.mdb.AlerterMDB$$$endpoint8
In a comment from Tim McCormick he stated the following:
Looks like some sort of classpath error with your MDB: com.ge.trans.mcs.msgejb.ejb.imr.mdb.InBoundMessageMDB The error states that it can't create the 'endpoint4' subclass.
Ensure the endpoint4 subclass is in your classpath.

Related

ClassNotFoundException exception occurred: io.confluent.kafka.security.config.provider.SecurePassConfigProvider (kafka.server.KafkaConfig)

The broker is failed on start-up and I can see the following errors :
INFO Registered kafka:type=kafka.Log4jController MBean (kafka.utils.Log4jControllerRegistration$)
ERROR ClassNotFoundException exception occurred: io.confluent.kafka.security.config.provider.SecurePassConfigProvider (kafka.server.KafkaConfig)
INFO Registered kafka:type=kafka.Log4jController MBean (kafka.utils.Log4jControllerRegistration$)
ERROR ClassNotFoundException exception occurred: io.confluent.kafka.security.config.provider.SecurePassConfigProvider (kafka.server.KafkaConfig)
INFO Registered kafka:type=kafka.Log4jController MBean (kafka.utils.Log4jControllerRegistration$)
ERROR ClassNotFoundException exception occurred: io.confluent.kafka.security.config.provider.SecurePassConfigProvider (kafka.server.KafkaConfig)
INFO Registered kafka:type=kafka.Log4jController MBean (kafka.utils.Log4jControllerRegistration$)
ERROR ClassNotFoundException exception occurred: io.confluent.kafka.security.config.provider.SecurePassConfigProvider (kafka.server.KafkaConfig)
INFO Registered kafka:type=kafka.Log4jController MBean (kafka.utils.Log4jControllerRegistration$)
INFO KafkaConfig values:
----------------------------
I did a secret setup for one of the property(i.e., ssl.truststore.password) in server.properties file and tried re-starting the server and observed the above error.
Any help would be appreciated. Thanks!!!
---server.properties---
##
ssl.truststore.password = ${securepass:/home/secret/secrets.txt:server.properties/ssl.truststore.password}
config.providers = securepass
config.providers.securepass.class = io.confluent.kafka.security.config.provider.SecurePassConfigProvider
Confluent Community version used - 5.5.2
The community edition of Confluent Platform 5.5.2 does not come with this class...
$ find ./confluent-5.5.2 -name 'kafka-client-plugins*.jar'
Download the file here and make sure it is in the Kafka broker classpath, e.g. /usr/share/java/kafka if installed directly to the OS, or the share/java/kafka folder of the Confluent tarball.
https://packages.confluent.io/maven/io/confluent/kafka-client-plugins/5.5.2-ce/kafka-client-plugins-5.5.2-ce.jar
Verified with
$ jar -tf kafka-client-plugins-5.5.2-ce.jar| grep SecurePassConfigProvider
io/confluent/kafka/security/config/provider/SecurePassConfigProvider.class
Overall, if someone has file-system access to your brokers, you have bigger problems, and obscuring the file with a direct reference to another is not "secure"

liquibase generateChangeLog error with MongoDB

Is it possible to generate change log from existing MongoDB database?
❯ liquibase generateChangeLog
[2021-04-05 11:01:31] INFO [liquibase.integration] No Liquibase Pro license key supplied. Please set liquibaseProLicenseKey on command line or in liquibase.properties to use Liquibase Pro features.
Liquibase Community 4.3.2 by Datical
Starting Liquibase at 11:01:31 (version 4.3.2 #44 built at 2021-03-23 14:01+0000)
[2021-04-05 11:01:31] INFO [com.mongodb.diagnostics.logging.JULLogger log] Cluster created with settings {hosts=[localhost:27017], mode=SINGLE, requiredClusterType=UNKNOWN, serverSelectionTimeout='30000 ms', maxWaitQueueSize=500}
BEST PRACTICE: The changelog generated by diffChangeLog/generateChangeLog should be inspected for correctness and completeness before being deployed.
[2021-04-05 11:01:31] INFO [com.mongodb.diagnostics.logging.JULLogger log] Exception in monitor thread while connecting to server localhost:27017
com.mongodb.MongoSocketOpenException: Exception opening socket
at com.mongodb.internal.connection.SocketStream.open(SocketStream.java:70)
at com.mongodb.internal.connection.InternalStreamConnection.open(InternalStreamConnection.java:128)
at com.mongodb.internal.connection.DefaultServerMonitor$ServerMonitorRunnable.run(DefaultServerMonitor.java:117)
at java.base/java.lang.Thread.run(Thread.java:831)
Caused by: java.net.ConnectException: Connection refused
at java.base/sun.nio.ch.Net.pollConnect(Native Method)
at java.base/sun.nio.ch.Net.pollConnectNow(Net.java:669)
at java.base/sun.nio.ch.NioSocketImpl.timedFinishConnect(NioSocketImpl.java:542)
at java.base/sun.nio.ch.NioSocketImpl.connect(NioSocketImpl.java:597)
at java.base/java.net.SocksSocketImpl.connect(SocksSocketImpl.java:333)
at java.base/java.net.Socket.connect(Socket.java:645)
at com.mongodb.internal.connection.SocketStreamHelper.initialize(SocketStreamHelper.java:64)
at com.mongodb.internal.connection.SocketStream.initializeSocket(SocketStream.java:79)
at com.mongodb.internal.connection.SocketStream.open(SocketStream.java:65)
... 3 more
Unexpected error running Liquibase: java.lang.ClassCastException: class liquibase.ext.mongodb.database.MongoConnection cannot be cast to class liquibase.database.jvm.JdbcConnection (liquibase.ext.mongodb.database.MongoConnection and liquibase.database.jvm.JdbcConnection are in unnamed module of loader 'app')
For more information, please use the --logLevel flag
[2021-04-05 11:01:31] SEVERE [liquibase.integration] Unexpected error running Liquibase: java.lang.ClassCastException: class liquibase.ext.mongodb.database.MongoConnection cannot be cast to class liquibase.database.jvm.JdbcConnection (liquibase.ext.mongodb.database.MongoConnection and liquibase.database.jvm.JdbcConnection are in unnamed module of loader 'app')
liquibase.exception.LiquibaseException: liquibase.command.CommandExecutionException: java.lang.ClassCastException: class liquibase.ext.mongodb.database.MongoConnection cannot be cast to class liquibase.database.jvm.JdbcConnection (liquibase.ext.mongodb.database.MongoConnection and liquibase.database.jvm.JdbcConnection are in unnamed module of loader 'app')
at liquibase.integration.commandline.CommandLineUtils.doGenerateChangeLog(CommandLineUtils.java:251)
at liquibase.integration.commandline.Main.doMigration(Main.java:1542)
at liquibase.integration.commandline.Main$1.lambda$run$0(Main.java:367)
at liquibase.Scope.lambda$child$0(Scope.java:160)
at liquibase.Scope.child(Scope.java:169)
at liquibase.Scope.child(Scope.java:159)
at liquibase.Scope.child(Scope.java:138)
at liquibase.integration.commandline.Main$1.run(Main.java:366)
at liquibase.integration.commandline.Main$1.run(Main.java:196)
at liquibase.Scope.child(Scope.java:169)
at liquibase.Scope.child(Scope.java:145)
at liquibase.integration.commandline.Main.run(Main.java:196)
at liquibase.integration.commandline.Main.main(Main.java:158)
Caused by: liquibase.command.CommandExecutionException: java.lang.ClassCastException: class liquibase.ext.mongodb.database.MongoConnection cannot be cast to class liquibase.database.jvm.JdbcConnection (liquibase.ext.mongodb.database.MongoConnection and liquibase.database.jvm.JdbcConnection are in unnamed module of loader 'app')
at liquibase.command.AbstractCommand.execute(AbstractCommand.java:24)
at liquibase.integration.commandline.CommandLineUtils.doGenerateChangeLog(CommandLineUtils.java:249)
... 12 more
Caused by: java.lang.ClassCastException: class liquibase.ext.mongodb.database.MongoConnection cannot be cast to class liquibase.database.jvm.JdbcConnection (liquibase.ext.mongodb.database.MongoConnection and liquibase.database.jvm.JdbcConnection are in unnamed module of loader 'app')
at liquibase.snapshot.jvm.JdbcSnapshotGenerator.getDatabaseCatalogNames(JdbcSnapshotGenerator.java:144)
at liquibase.snapshot.jvm.CatalogSnapshotGenerator.snapshotObject(CatalogSnapshotGenerator.java:35)
at liquibase.snapshot.jvm.JdbcSnapshotGenerator.snapshot(JdbcSnapshotGenerator.java:65)
at liquibase.snapshot.SnapshotGeneratorChain.snapshot(SnapshotGeneratorChain.java:49)
at liquibase.snapshot.DatabaseSnapshot.include(DatabaseSnapshot.java:315)
at liquibase.snapshot.DatabaseSnapshot.init(DatabaseSnapshot.java:100)
at liquibase.snapshot.DatabaseSnapshot.<init>(DatabaseSnapshot.java:59)
at liquibase.snapshot.JdbcDatabaseSnapshot.<init>(JdbcDatabaseSnapshot.java:38)
at liquibase.snapshot.SnapshotGeneratorFactory.createSnapshot(SnapshotGeneratorFactory.java:215)
at liquibase.snapshot.SnapshotGeneratorFactory.createSnapshot(SnapshotGeneratorFactory.java:188)
at liquibase.command.core.DiffCommand.createReferenceSnapshot(DiffCommand.java:222)
at liquibase.command.core.DiffCommand.createDiffResult(DiffCommand.java:144)
at liquibase.command.core.GenerateChangeLogCommand.run(GenerateChangeLogCommand.java:62)
at liquibase.command.AbstractCommand.execute(AbstractCommand.java:19)
... 13 more
Liquibase properties:
changeLogFile: _changelog.xml
url: mongodb://localhost:27017/test?authSource=admin
username: xxx
password: xxx
logLevel: info
Is there any configuration that I am missing?
Currently, generatechangelog using the liquibase-mongodb extension is not supported. I am using this issue as a reference.
However, you can request the feature here.

java.lang.IllegalStateException: RpcEnv already stopped

How can we handle below warning message in spark - 1.6.2. Can someone help on this.
java.lang.IllegalStateException: RpcEnv already stopped
WARN 2018-03-08 07:20:37,049 org.apache.spark.rpc.netty. Dispatcher:
Message
RemoteProcessDisconnected(prdshsvcs-cassandra-cluster-002:60090)
dropped. java.lang.IllegalStateException: RpcEnv already stopped.
Thanks,
Chandra

Getting SmscManagement is not registered error in smsc gateway management UI

I am using Telestax Restcomm smsc gateway 7.2.109.
When I load sms gateway management UI, I am getting
15:31:12:520 [ERROR] javax.management.InstanceNotFoundException : org.mobicents.smsc:layer=SmscPropertiesManagement,name=SmscManagement is not registered.. (Full Stack Trace)
Also I am getting following errors while starting smsc server (jboss).
08:56:25,851 WARN [AbstractDeploymentContext] (main) Unable to register deployment mbean SCTPManagement
javax.management.InstanceAlreadyExistsException: jboss.deployment:id="SCTPManagement",type=Component already registered.
08:56:25,858 WARN [AbstractDeploymentContext] (main) Unable to register deployment mbean SCTPShellExecutor
javax.management.InstanceAlreadyExistsException: jboss.deployment:id="SCTPShellExecutor",type=Component already registered.
08:56:25,865 WARN [AbstractDeploymentContext] (main) Unable to register deployment mbean RoutingLabelFormat
javax.management.InstanceAlreadyExistsException: jboss.deployment:id="RoutingLabelFormat",type=Component already registered.
08:56:25,874 WARN [AbstractDeploymentContext] (main) Unable to register deployment mbean Mtp3UserPart
javax.management.InstanceAlreadyExistsException: jboss.deployment:id="Mtp3UserPart",type=Component already registered.
08:56:25,882 WARN [AbstractDeploymentContext] (main) Unable to register deployment mbean M3UAShellExecutor
javax.management.InstanceAlreadyExistsException: jboss.deployment:id="M3UAShellExecutor",type=Component already registered.
08:56:25,889 WARN [AbstractDeploymentContext] (main) Unable to register deployment mbean SS7Clock
javax.management.InstanceAlreadyExistsException: jboss.deployment:id="SS7Clock",type=Component already registered.
08:56:25,899 WARN [AbstractDeploymentContext] (main) Unable to register deployment mbean SS7Scheduler
javax.management.InstanceAlreadyExistsException: jboss.deployment:id="SS7Scheduler",type=Component already registered.
08:56:25,907 WARN [AbstractDeploymentContext] (main) Unable to register deployment mbean SccpStack
javax.management.InstanceAlreadyExistsException: jboss.deployment:id="SccpStack",type=Component already registered.
08:56:25,914 WARN [AbstractDeploymentContext] (main) Unable to register deployment mbean SccpExecutor
javax.management.InstanceAlreadyExistsException: jboss.deployment:id="SccpExecutor",type=Component already registered.
08:56:25,921 WARN [AbstractDeploymentContext] (main) Unable to register deployment mbean TcapStack
javax.management.InstanceAlreadyExistsException: jboss.deployment:id="TcapStack",type=Component already registered.
08:56:25,927 WARN [AbstractDeploymentContext] (main) Unable to register deployment mbean TcapExecutor
javax.management.InstanceAlreadyExistsException: jboss.deployment:id="TcapExecutor",type=Component already registered.
08:56:25,934 WARN [AbstractDeploymentContext] (main) Unable to register deployment mbean ShellExecutor
javax.management.InstanceAlreadyExistsException: jboss.deployment:id="ShellExecutor",type=Component already registered.
08:56:25,940 WARN [AbstractDeploymentContext] (main) Unable to register deployment mbean MapStack
javax.management.InstanceAlreadyExistsException: jboss.deployment:id="MapStack",type=Component already registered.
08:56:25,950 WARN [AbstractDeploymentContext] (main) Unable to register deployment mbean MAPSS7Service
javax.management.InstanceAlreadyExistsException: jboss.deployment:id="MAPSS7Service",type=Component already registered.
08:56:25,984 WARN [AbstractDeploymentContext] (main) Unable to register deployment mbean Ss7Management
javax.management.InstanceAlreadyExistsException: jboss.deployment:id="Ss7Management",type=Component already registered.
08:56:26,041 ERROR [AbstractKernelController] (main) Error installing to Real: name=vfsfile:/home/telestax/Downloads/restcomm-smsc-7.2.109/jboss-5.1.0.GA/server/default/deploy/restcomm-smsc-server/META-INF/jboss-beans.xml state=PreReal mode=Manual requiredState=Real
org.jboss.deployers.spi.DeploymentException: Error deploying: SCTPManagement
DEPLOYMENTS MISSING DEPENDENCIES:
Deployment "vfszip:/home/telestax/Downloads/restcomm-smsc-7.2.109/jboss-5.1.0.GA/server/default/deploy/smpp-server-ra-du-7.0.5.jar/" is missing the following dependencies:
Dependency "SmppManagement" (should be in state "Real", but is actually in state "** NOT FOUND Depends on 'SmppManagement' ")
Deployment "vfszip:/home/telestax/Downloads/restcomm-smsc-7.2.109/jboss-5.1.0.GA/server/default/deploy/smsc-resource-adaptors-du-7.2.109.jar/" is missing the following dependencies:
Dependency "SmscManagement" (should be in state "Real", but is actually in state " NOT FOUND Depends on 'SmscManagement' ")
Deployment "vfszip:/home/telestax/Downloads/restcomm-smsc-7.2.109/jboss-5.1.0.GA/server/default/deploy/smsc-services-du-7.2.109.jar/" is missing the following dependencies:
Dependency "SmscManagement" (should be in state "Real", but is actually in state " NOT FOUND Depends on 'SmscManagement' **")
DEPLOYMENTS IN ERROR:
Deployment "vfsfile:/home/telestax/Downloads/restcomm-smsc-7.2.109/jboss-5.1.0.GA/server/default/deploy/restcomm-smsc-server/META-INF/jboss-beans.xml" is in error due to the following reason(s): java.lang.IllegalStateException: SCTPManagement is already installed.
Deployment "SmscManagement" is in error due to the following reason(s): ** NOT FOUND Depends on 'SmscManagement' **
Deployment "SmppManagement" is in error due to the following reason(s): ** NOT FOUND Depends on 'SmppManagement' **
Kindly help.
Thanks.
Update:
Server is working fine now.
Getting below error when calling from smtp simulator client.
14:26:41,913 INFO [SmppServerConnector] (SmppManagement) New channel from [172.17.0.1:57210]
14:26:41,916 INFO [UnboundSmppSession] (SmppManagement.UnboundSession.172.17.0.1:57210) received PDU: (bind_transmitter: 0x00000023 0x00000002 0x00000000 0x00000001) (body: systemId [test] password [test] systemType [] interfaceVersion [0x34] addressRange (0x01 0x01 [6666])) (opts: )
14:26:41,917 ERROR [DefaultSmppServerHandler] (SmppManagement.UnboundSession.172.17.0.1:57210) Received BIND request but no ESME configured for SystemId=test Host=172.17.0.1 Port=57210 SmppBindType=TRANSMITTER
14:26:41,918 WARN [UnboundSmppSession] (SmppManagement.UnboundSession.172.17.0.1:57210) Bind request rejected or failed for connection [172.17.0.1:57210] with error [SMPP processing error [0x0000000F]]
14:26:41,918 INFO [UnboundSmppSession] (SmppManagement.UnboundSession.172.17.0.1:57210) send PDU: (bind_transmitter_resp: 0x0000001A 0x80000002 0x0000000F 0x00000001 result: "System ID invalid") (body: systemId [test]) (opts: (sc_interface_version: 0x0210 0x0001 [34]))
14:26:41,919 INFO [UnboundSmppSession] (SmppManagement.UnboundSession.172.17.0.1:57210) Connection closed with [172.17.0.1:57210]
Can you retry from the latest snapshot release from https://mobicents.ci.cloudbees.com/job/RestComm-SMSC/ ?

deployed cassandra datastax enterprise and got java.lang.AssertionError

I am trying to deploy the cassandra datastax enterprise 4.5.1 on my cluster, and I always got java.lang.AssertionError, the log is as below:
INFO [main] 2014-10-13 06:01:03,142 CLibrary.java (line 63) JNA not found. Native methods will be disabled.
INFO [main] 2014-10-13 06:01:03,155 CacheService.java (line 105) Initializing key cache with capacity of 100 MBs.
INFO [main] 2014-10-13 06:01:03,167 CacheService.java (line 117) Scheduling key cache save to each 14400 seconds (going to save all keys).
INFO [main] 2014-10-13 06:01:03,169 CacheService.java (line 131) Initializing row cache with capacity of 0 MBs
INFO [main] 2014-10-13 06:01:03,177 CacheService.java (line 141) Scheduling row cache save to each 0 seconds (going to save all keys).
INFO [main] 2014-10-13 06:01:03,471 ColumnFamilyStore.java (line 249) Initializing system.schema_triggers
INFO [main] 2014-10-13 06:01:03,522 ColumnFamilyStore.java (line 249) Initializing system.compaction_history
INFO [SSTableBatchOpen:1] 2014-10-13 06:01:03,547 SSTableReader.java (line 223) Opening /apps/datastax-enterprise/9161/ddata/data/system/compaction_history/system-compaction_history-jb-4349 (163599 bytes)
ERROR [SSTableBatchOpen:1] 2014-10-13 06:01:03,565 SSTableReader.java (line 233) Cannot open /apps/datastax-enterprise/9161/ddata/data/system/compaction_history/system-compaction_history-jb-4349; partitioner org.apache.cassandra.dht.RandomPartitioner does not match system partitioner org.apache.cassandra.dht.Murmur3Partitioner. Note that the default partitioner starting with Cassandra 1.2 is Murmur3Partitioner, so you will need to edit that to match your old partitioner if upgrading.
INFO [Thread-1] 2014-10-13 06:01:03,569 DseDaemon.java (line 477) DSE shutting down...
ERROR [Thread-1] 2014-10-13 06:01:03,635 CassandraDaemon.java (line 199) Exception in thread Thread[Thread-1,5,main]
java.lang.AssertionError
at org.apache.cassandra.gms.Gossiper.addLocalApplicationState(Gossiper.java:1263)
at com.datastax.bdp.gms.DseState.setActiveStatus(DseState.java:171)
at com.datastax.bdp.server.DseDaemon.stop(DseDaemon.java:478)
at com.datastax.bdp.server.DseDaemon$1.run(DseDaemon.java:384)
Dose anynone know this or maybe give me any infomation? Any answer will be appreciated
Problem solved, as #RussS said, this is because the partitioner doesn`t match, we should use partitioner: org.apache.cassandra.dht.RandomPartitioner in cassandra.yaml