z-logo
Premium
Glucose Transporter 4 (GLUT4) is Not the Only GLUT Responsible for Ca 2+ /Calmodulin‐Dependent Protein Kinase Kinase α (CaMKKα)‐Induced Glucose Uptake in Mouse Skeletal Muscle
Author(s) -
Witczak Carol,
Ferey Jeremie,
Smith Cheryl,
Brault Jeffrey
Publication year - 2015
Publication title -
the faseb journal
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 1.709
H-Index - 277
eISSN - 1530-6860
pISSN - 0892-6638
DOI - 10.1096/fasebj.29.1_supplement.817.7
Subject(s) - glut4 , glucose transporter , glucose uptake , skeletal muscle , medicine , endocrinology , biology , insulin receptor , insulin , chemistry , insulin resistance
Chronic activation of Ca 2+ /calmodulin‐dependent protein kinase kinase α (CaMKKα) signaling for 2 weeks stimulates skeletal muscle glucose uptake in both insulin‐sensitive and insulin‐resistant mice; yet surprisingly the glucose transporter(s) that mediate this effect are currently unknown. The goal of this study was to determine if glucose transporter 4 (GLUT4) is the main glucose transporter responsible for CaMKKα‐induced muscle glucose uptake. To stimulate CaMKKα signaling, muscles from 13‐14 week old, male, wild‐type/control, muscle‐specific GLUT4 heterozygous and muscle‐specific GLUT4 knockout mice were transfected with plasmid DNA containing constitutively active CaMKKα or empty vector by in vivo electroporation. After 2 weeks, active CaMKKα protein levels were robustly increased and were not different between groups. In vivo muscle [ 3 H]‐2‐deoxyglucose uptake was examined in the absence of insulin stimulation. Constitutively active CaMKKα increased glucose uptake ~250% in wild‐type/control mice, ~100% in GLUT4 heterozygous mice, and ~60% in GLUT4 knockout mice. Collectively, these results show that activation of CaMKKα signaling primarily stimulates glucose uptake via GLUT4, but suggest that another glucose transporter is also involved. SUPPORT: NIH R00AR056298, ECU start‐up funds.

This content is not available in your region!

Continue researching here.

Having issues? You can contact us here