z-logo
Premium
Control of death receptor and mitochondrial‐dependent apoptosis by c‐Jun N‐terminal kinase in hippocampal CA1 neurones following global transient ischaemia
Author(s) -
Carboni Sonia,
Antonsson Bruno,
Gaillard Pascale,
Gotteland JeanPierre,
Gillon JeanYves,
Vitte PierreAlain
Publication year - 2005
Publication title -
journal of neurochemistry
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 1.75
H-Index - 229
eISSN - 1471-4159
pISSN - 0022-3042
DOI - 10.1111/j.1471-4159.2004.02925.x
Subject(s) - hippocampal formation , terminal (telecommunication) , transient (computer programming) , apoptosis , kinase , microbiology and biotechnology , chemistry , ischemia , neuroscience , biology , medicine , biochemistry , computer science , computer network , operating system
c‐Jun N‐terminal kinase (JNK), a member of the mitogen‐activated protein kinase family, is activated in response to a number of extracellular stimuli, including inflammatory cytokines, UV irradiation and ischaemia. A large body of evidence supports a role for JNK signalling in stress‐induced apoptosis. It has been hypothesized that JNK may contribute to the apoptotic response by regulating the intrinsic cell death pathway involving the mitochondria. Here, we examined the role of the JNK signalling pathway in hippocampal CA1 apoptotic neurones following transient ischaemia in gerbils. We showed early activation of death receptor‐dependent apoptosis (caspase‐8 activation 2 days after ischaemia) and a biphasic activation of caspase‐3 and caspase‐9 after ischaemia. Activation of the mitochondrial pathway, as measured by cytochrome c release, appeared as a late event (5–7 days after ischaemia). AS601245, a novel JNK inhibitor, antagonized activation of both pathways and significantly protected CA1 neurones from cell death. Our results suggest a key role of JNK in the control of death receptor and mitochondrial‐dependent apoptosis after transient ischaemia.

This content is not available in your region!

Continue researching here.

Having issues? You can contact us here