简体   繁体   English

ActiveMQ Blob消息的持久性

[英]Persistence of ActiveMQ Blob Messages

在此处输入图片说明 When we communicating using text if remote server failed or down embedded server will save data in localdb(KahaDB) and send it later. 当我们使用文本进行通信时,如果远程服务器出现故障或停机,则嵌入式服务器会将数据保存在localdb(KahaDB)中,并在以后发送。 But while sending Blob messages how can we ensure persistence. 但是在发送Blob消息时,我们如何确保持久性。 Here we have to specify upload URL to upload data. 在这里,我们必须指定上传URL来上传数据。 This upload URL is accessible to both producer and consumer. 生产者和消费者均可访问此上载URL。 In my case my upload URL is in remote. 就我而言,我的上传网址位于远程位置。 If i send data while network failure then producer will failed to upload(Then how we can persist that message -I think KahaDB can't be used for blob messages). 如果我在网络故障时发送数据,那么生产者将无法上传(那么我们如何持久化该消息-我认为KahaDB不能用于Blob消息)。

"Persistence of Blob Messaging in ActiveMQ"? “ ActiveMQ中Blob消息的持久性”?

"Can't we use Database(KahaDB) to Blob Message URL?" “我们不能使用数据库(KahaDB)来Blob消息URL吗?”

"Can We create File Server in embedded broker like in remote activemq server?" “我们可以像在远程activemq服务器中一样在嵌入式代理中创建文件服务器吗?”

KahaDB does not store the Blob portion of the BlobMessage. KahaDB不存储BlobMessage的Blob部分。 If you send a message with the URL where the blob is and that resource goes down your receiver won't have access to it, at least not until that resource comes back online. 如果您发送的消息带有该Blob所在的URL,并且该资源出现故障,那么您的接收者将无权访问它,至少直到该资源恢复联机为止。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM