在大型系统架构时咱们会进行分库设计,好比用户库、订单库。若是采用了dubbo会产生服务,若是目前有两个服务,用户服务和订单服务。sql
实际业务中,用户下单支付成功后,并改变用户的状态或增长用户的积分。这样过程当中就会产生事务问题。这里咱们采用最终事务一致性。session
大体实现思路,把分布式事务切割成小事务,用消息队列消除分布式事务。实现方式以下:架构
订单功能的小事务以下:分布式
首先:订单服务。ide
jmsTemplate.setSessionTransacted(true);
transactionTemplate.execute(new TransactionCallback<String>()
{设计
@Override
public String doInTransaction(TransactionStatus status)
{
// TODO Auto-generated method stub
Connection connection = null;
Session session = null;
try
{
String orderId = System.currentTimeMillis() + "";
String sql = "insert into order (order_id,user_id) values (?,?)";
jdbcTemplate.update(sql, new Object[]
{ orderId, userId });
connection = jmsTemplate.getConnectionFactory().createConnection();
session = connection.createSession(true, Session.CLIENT_ACKNOWLEDGE);
Destination destination = session.createQueue("transactionQueue");
MessageProducer producer = session.createProducer(destination);
producer.setDeliveryMode(DeliveryMode.PERSISTENT);
String text = "orderid";
MapMessage message = session.createMapMessage();//Message(text);
message.setString("order_id", orderId);
message.setString("user_id", userId);
message.setString("status", "1");
producer.send(message);
session.commit();
} catch (Exception ex)
{
// TODO: handle exception
status.setRollbackOnly();
try
{
session.rollback();
} catch (JMSException e)
{
// TODO Auto-generated catch block
e.printStackTrace();
}
ex.printStackTrace();
} finally
{
try
{
session.close();
} catch (JMSException e)
{
// TODO Auto-generated catch block
e.printStackTrace();
}
}
return null;
}
});队列
用户服务监听消息队列事务
public void handlerMessage(final MapMessage mapMessage, final Session session) throws JMSException
{
getTransactionTemplate().execute(new TransactionCallback<String>()
{get
@Override
public String doInTransaction(TransactionStatus status)
{
int result = 0;
try
{
//String status, String user_id, String order_id
updateUserLevel(mapMessage.getString("status"),
mapMessage.getString("user_id"),
mapMessage.getString("order_id"));
} catch (Exception e)
{
try
{
session.rollback();
} catch (JMSException ex)
{
logger.error("JMS事务回滚异常", ex);
ex.printStackTrace();
}
status.setRollbackOnly();消息队列
}
return String.valueOf(result);
}
});
}
消息队列配置
<amq:redeliveryPolicy id="activeMQRedeliveryPolicy" destination="#defaultDestination" redeliveryDelay="1000" maximumRedeliveries="10" />
消息队列重试次数10次,若是一次失败,能够多试几回。
若是消息队列最终失败,则监听失败信息,采用事务补偿机制,删除以前增长的订单或其余处理。